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?
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
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
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 ?
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
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
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 ??
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
I just wanted to give the opportunity to use what I did a long time ago, but you impose some kind of responsibility on me, I just made a shell, because I could take other packages as examples, what is the problem to fix what you wrote here (contribute to the community), or do not want to take responsibility? If you don’t want to, and don’t make claims
p.s:
Authorship does not bother me much, you can take it if you want)