Please add 2 new packages for EOIP

Hi, please add 2 my packages EOIP mikrotik compatible


Guys on says post on this forum for add this

2 Likes

Hi, I found a Linux kernel mode of EOIP on Github. May be can be ported OpenWRT :slight_smile:

Hi bogdik.

Did you ever get a response to this request? I built your code into my image and tested it with an ath79 target AP and it works perfectly. I had to add it to my packages directory and I built the latest snapshot. It wasn't there by default. I also used the default configuration but changed the tunnel id and Remote IP.

I am building a script that will work with udhcp to make the configuration file dynamically. But there are some configuration items in the file I don't really understand and there is little documentation. Is there a repo somewhere that describes the configuration items clearly?

I made a pull request without waiting,


2 Likes

Comment author in sources - "If you use dynamic=1 option, take attention that there is no authorization,
and it is not secure. It is not good idea to use this feature with public
ip or insecure(not completely under your control, each host) network.
"
other parameters should be clear

Okay, that makes sense. I'll use it carefully. :wink:

1 Like

@bogdik I compiled your packages but I'm getting an error in the UI.

Any guidance will be much appreciated.

Don't forget to use search:

1 Like

@123serge123 you're right for both things. Thanks :+1:

Since the eoip package was added to the main branch, luci needs to be convert to javascript, I'll deal with this soon so that it will also be added to the packages

1 Like

hi @bogdik

i like to ask you about EoIP on OpenWRT

Using Mikrotik for many years, so i have EoIP tunnels between sites
EoIP is bridged on both end, so Vlan's are pushed thru EoIP
6 pcs of Vlan are terminated on both side

With your EoIP package, is it possible to reproduce same thing ?

full L2 with Vlans terminated on bridge ?

thank you in advance

My tests showed that everything works without problems, but you can check it yourself and write the result here

1 Like

Ok
i like to ask you, do you have any example for config file how to enable Vlan in EoIP?
i am try to avoid using Luci, only ssh/cli so i will be happy if you could provide some config for tunnel

thank you

Just use Luci package https://github.com/bogdik/luci-app-eoip
or /etc/config/eoip example

Summary

config eoip

option name '0'
option dynamic '1'
option idtun '10170'
option dst '192.168.101.1'
list vlan '234'
list vlan '100'

And restart eoip service

This was the missing piece of information. Thank you

Everything has been added, use the main branch

Hi @bogdik

few observation
init script:

echo "#!/bin/sh" > /etc/afterStart.sh
...
echo "rm /etc/afterStart.sh" >> /etc/afterStart.sh

it is very wrong to write TMP files in /etc (squash)
it could easy corrupt file system in case of failure when starting EoIP or similar situation, and flash chip wearout is issue on all embeded devices

so please rewrite script to make TMP files in TMP directory

second:

eoip [configfile [bindip]]

as you see, there is option for bindip
in some cases, it is realy useful to have
/usr/bin/eoip /etc/eoip.cfg 192.168.3.1
or whatever, when system could not determine easy what is the proper local address

same settings exist in Mikrotik ROS (local address)
and exist in eoip.c

only missing from LUCI and startup script

so, if you rewrite a startup script to point on TMP, same time you could add "local address" to it

tnx

hi @bogdik
another observation

when using Vlan's your startup script simply does not work

interface is added

ip link add link zeoip${name} name zeoip${name}.${value} type vlan id ${value}

but there is no hotplug event, interface is down, so it is stay unconfigured

zeoip0.555 Link encap:Ethernet  HWaddr 2E:9B:17:6C:69:0C  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

it is not a problem for advanced users to use EoIP in this state, custom script, custom startup, but what is the meaning of plug&play Luci concept if thing simply does not work automaticaly ??

it looks like you need to do some heavy rewriting

There are no problems with configuring such an interface through luci tools, after config eoip, just use Interfaces->add new interface and customize as you like

If you want to fix something, take it and do it yourself Pull request to main branch

1 Like

@bogdik

ok, i see you use same tone / language / approach like in your PR

as you stated in many place "it is MY eoip" MY package, etc
so obviously, you are maintainer, and responsible for it

but after all, thank you for adding p910nd package to openwrt

"Project-Id-Version: LuCI: p910nd\n"
"POT-Creation-Date: 2012-08-15 11:42+0300\n"
"PO-Revision-Date: 2018-01-22 13:16+0300\n"

best wishes