-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting a static IP on the WAN port #1146
Comments
Hi, add few notes and a question on this.
To avoid this manual change i tried to rewrite both scripts to not use But testing this i noticed that watchping will check only As a proposal, could have sense instead to define an overwriteable array of main wan interfaces? And let both watchping and babeld-auto-gw-mode check this list to do their stuff?
allowing so, to do this in my case:
babeld-auto-gw-mode with or without ubus doesn't matter at this point, but i wonder:
Both watchping and babeld-auto-gw-mode should in this case Here the example of babel watchping's hooks without ubus that check /etc/watchping/wan-fail.d/babeld-gw
/etc/watchping/wan-ok.d/babeld-gw
|
An alternative could be to add the IP and gateway IP as options of the wan proto. Either something like this:
or something like this:
These IPs will then be taken and used for setting the static configuration here: https://github.com/libremesh/lime-packages/blob/master/packages/lime-proto-wan/files/usr/lib/lua/lime/proto/wan.lua#L16 We can take some code from the static proto: |
I just tried to set a static IPv4 on the WAN port connected to an internet-providing router and just realized that Babeld does not share the default route from this interface.
The configuration I inserted in
/etc/config/lime-node
is this:(as documented in lime-example.txt, the first section is for avoiding the lime-hwd-openwrt-wan to configure the wan interface to use dhcp client, the second is creating a section setting the static IP).
The default route is present, but it does not get shared with the rest of the network.
I suppose this happens because babeld-auto-gw-mode is looking for the default route only on the section
wan
of/etc/config/network
:lime-packages/packages/babeld-auto-gw-mode/files/etc/watchping/wan-ok.d/babeld-gw
Line 14 in 1aa97c6
but the configuration above generates the route in a section named
lm_net_wan_static
:The text was updated successfully, but these errors were encountered: