14 Feb
2017
14 Feb
'17
12:43 a.m.
Hi Nicolas!
I think I missed some of your emails in Gmail's spam folder...
Answer inline:
2017-02-13 1:51 GMT+01:00 Nicolas North <nk(a)os.vu>vu>:
Also, as a bonus, we try to
pair all LiMe routers with an openwrt “simple AP” router, that takes care of
the AP level and lets the LiMe router handle only the adhoc meshing level,
for maximum wireless efficiency.
That's really wise :)
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?
Anyway, do you need static IP addresses at the AP routers? You could
also let them take the IP from LiMe (and LiMe would take care of
avoiding collisions).
Additionally, if you let LiMe routers to autoassign their own IPv4,
they will span over the whole subnet, unless you specify a smaller
"subnet" (not a real subnet, just a range) for auto-assignment, as
explained in /etc/config/lime-example in the comment on the
main_ipv4_address option:
https://github.com/libremesh/lime-packages/blob/2ce5ffa96de5b0b5abb507076b0…
For example:
# cat /etc/config/lime
config lime 'network'
option main_ipv4_address '10.13.128.0/16/17'
will limit the autoassignment of IPv4 to the second half of the
broadcast domain.
Bye!
Ilario