22 Feb
2017
22 Feb
'17
6:23 p.m.
Hi devs!
In lime-users mailing list Nicolas asked how to change the IPv4 DHCP
server range in LiMe.
I realized that there's no way to do it. Anygw configures dnsmasq to
use the whole broadcast domain as DHCP range.
Here is where this happens:
https://github.com/libremesh/lime-packages/commit/3a6596d50b3c0446b988f84d3…
In theory there should be no problem as there should be a check for
the availability of the IP (by the DHCP server or client?), anyway I
think we should fix this.
Should we add a new option in /etc/config/lime?
Or use the values from /etc/config/dhcp?
2017-02-14 1:43 GMT+01:00 Ilario <iochesonome(a)gmail.com>om>:
We give APs
static addresses of 10.13.64.1, 2, 3, and so on. They must all
be different. Try and stay out of the DHCP range which starts at 100 I
think.
A very interesting question. There's no option for DHCP range in
/etc/config/lime* files (and this is ok).
But I supposed that the range was defined in /etc/config/dhcp, which
on LibreMesh is identical than on OpenWrt/LEDE and contains:
# cat /etc/config/dhcp
[...]
config dhcp 'lan'
option interface 'lan'
option start '100'
option limit '150'
option leasetime '1h'
But trying to ask for a DHCP lease I received an IPv4 out of the
10.x.x.100-250 range, looking around I found that the DHCP range for
anygw is hardcoded:
https://github.com/libremesh/lime-packages/commit/3a6596d50b3c0446b988f84d3…
resulting in the whole subnet... No good. @devs?