20 Nov
2007
20 Nov
'07
11:29 a.m.
Hi,
Marek Lindner wrote:
Hi,
But thats definitely whats happening, on OpenWrt WRAP (x86)
as well as
on BroadCom (mipsel). It happened more than once, and the only thing
what was done to change the behavior was killing and starting batmand
again. Which doesn't changed every time the behavior.
05:12:09.512310 arp who-has 192.168.43.255 tell
192.168.42.25
05:12:10.512178 arp who-has 192.168.43.255 tell 192.168.42.25
These ARP request are not issued by BATMAN itself. BATMAN does only send
broadcast packets - your system creates these requests.
This is two times the same node, first time it
recognizes the broadcast
the right way, second time not.
BATMAN askes the system for the IP and broadcast addresses. In both cases the
system responds with the same answer. I don't see much difference from
batmans point of view. You have multihomed OLSR nodes with a single IP and
that works ? Can anyone of
the OLSR folks say something about that ? I can't imagine how the routing
daemon can distinguish 2 distinct connections with the same address ...
Works
perfect, we use for instance the WRAP-boards in our network with
two WIFI- and one LAN-Interface, all three having the same IP.
The related patch is at
http://titan.www.opennet-initiative.de/olsrd_patches/mipip.patch, but
its since a while part of olsrd.
Regards,
Rene