8 Apr
2014
8 Apr
'14
3:12 p.m.
Wouldn't you just do dhcp forwarding?
Host dhcp in the network core. So maybe a few dozen l2 clouds for a city, run an HA pair
of dhcp server virtual machines in Colo where the bmx router is?
That's how I do data center networks. L3 core with dns/dhcp etc and l2 edge with lots
of vlans .
On April 8, 2014 3:49:13 AM CDT, Pau <pau(a)dabax.net> wrote:
It is a hard problem. If the L2 cloud split, you cannot
sync the DHCP
servers. And once the cloud join afain, I don't know how the dhcp
leases
file will became.
I quick/dirty solution would be to split the DHCP servers range. So
instead of /24, give /21 or so and each DHCP server offers a different
/24. However I don't know if it makes sense to break the cleanness of
the solution to solve this case.
Maybe (maybe...) dnsmasq can solve this by detecting duplicate
addresses
and sending a DHCP renew to the affected clients.
@Gui, you are our dnsmasq guy, what do you think?
On 08/04/14 08:21, Tim Niemeyer wrote:
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hi
I heard an presentation last year in berlin about libre mesh. I was
amazed about
the idea to use clounds and a l3 routing protocol. I
talked a bit later with Pau about a netsplit problem where one cloud is
split up. Then alfred isn't synchonizing, so that the dhcp can't know
wich ip is already in use. Is the problem resolved or further
discussed?
Tim
(Freifunk Franken)
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
--
./p4u
------------------------------------------------------------------------
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev