Re: [lime-dev] L2 netsplit

The L2 domain should never keep running split, there's no clean way of merging that again. Option 1: never split. Use a backup l2 vpn between all border gateways, so that they can reach each other in the event of an internal mesh split. Traffic will flow between the two segments over the internet, with limited bandwidth. It should be configured with minimum priority so that it's never used under normal circumstances. Ninux.org pdf detailing the network diagram implements this. It's on ninux blog post dated 2012 ipv6 day. Idea 2: fencing. If one of the two segments happen to be left without gateways, it might turn off dhcp servers, or throw away the given (temp, short-timed) leases when the split dissolves (a gateway reappears) Daydream 3: maybe none of this is a problem, with our hybrid setup... batman only cares about macs (and they are unique), and bmx6 routes on the first hop out, so there's a chance having duplicate ipv4 addresses for some time is not really a conflict? (?) Red herring 4/6: dhcp database? I thought we were using stateless RA! I don't really get what you people are talking about. There's no sync needed, ips are autoconfigured by hosts themselves! :P On April 8, 2014 5:49:13 AM GMT-03:00, Pau <pau(a)dabax.net> wrote: