[OLSR-users] duplicate IP behaviour
Sun Feb 12 22:17:52 CET 2006
Sounds like a fair plan. DAD must be done on layer3 (or higher) as long
as our mesh routing protocol works on this layer. So olsrd should prabably
take action when a duplicate is detected.
I think having a config option on what action to take in such a case is
solution. This could be either executing a command or terminating olsrd.
A restart should not be required in your case since olsrd picks up changes
in interface configurations. I think we should add logic for olsrd to stop
emitting messages when a duplicate is detected for as long as the IP does
not change. Hmm... I'll have a look at this the next time I sit down with
Kosta Welke wrote:
> Andreas Tønnesen wrote:
>> I agree that the best solution might be that olsrd exits when
>> a IP duplicate.. but I'm not 100% sure(perhaps this should be yet
>> configurable option). But multiple nodes using the same main address
>> have a very bad impact on the network. So I guess what I'm saying is
>> we should enforce some sort of DAD which tries to make the network
>> kind of
>> "self healing" bu terminating the conflicting clients.
> What about olsrd just invoking a script when it detects an IP duplicate?
> (Or should be "olsrd stops, invokes script, restarts?", I think this
> is unnecessary, but you're the olsr guru)
> I am using IP zeroconf and olsr (in a small research envrionment) and
> if could olsr detect IP address conflicts, that would be great (ARP
> doesnt really help in an olsr'd net). For me, invoking a script that
> rolls the dice for just another IP address would seem like a good
> Just my 2 cents,
> olsr-users mailing list
More information about the Olsr-users