13 Apr
2017
13 Apr
'17
12:03 p.m.
On Thursday 13 April 2017 12:54:13 Nk via lime-users wrote:
So within the same network the DHCP assignments are
unique independently of
what node the client is connected to, correct?
Yeah
If you move between
different networks, you’re saying a conflict could of course arise.
No, different network on libremesh has different broadcast domain so no IP
conflict is possible
Is this
package available in standard openwrt?
No, it is in libremesh repository
If so could it be used in a non-lime
network where [long story short] there are a bunch of routers/APs [with
mesh nodes on the wan side] all with the same IP and subnet and DHCP range
being offered to clients [similarly to lime nodes all having 10.13.0.1
etc…], in order to have a distributed map of active leases and prevent
other routers/APs from assigning that lease to one of their clients, or is
this plugin relying on the layer 2 routing in lime?
ATM it rely on alfred, that rely on batman-adv it don't work on any network,
but alfred has proved to not scale well on our network so we are considering
different mechanisms for the near future, it would be nice if we find/implement
a solution that do not rely on specific routing protocol, as this is a more
general problem that make sense to solve on any multi-DHCP L2 network
Cheers!