[OLSR-users] Routes never added

[John Gorkos]

Tcpdump from the .1 router listening to broadcast pings:

(spam-protected):~# tcpdump -e -n -i eth1 host 192.168.7.47 and port not 22 and icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
11:48:56.718086 00:13:10:42:b4:39 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 98: IP 192.168.7.47 > 192.168.7.255: icmp 64: echo request 
seq 1
11:48:57.731957 00:13:10:42:b4:39 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 98: IP 192.168.7.47 > 192.168.7.255: icmp 64: echo request 
seq 2
11:48:58.735463 00:13:10:42:b4:39 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 98: IP 192.168.7.47 > 192.168.7.255: icmp 64: echo request 
seq 3
11:48:59.731909 00:13:10:42:b4:39 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 98: IP 192.168.7.47 > 192.168.7.255: icmp 64: echo request 
seq 4
11:49:01.731858 00:13:10:42:b4:39 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 98: IP 192.168.7.47 > 192.168.7.255: icmp 64: echo request 
seq 6
11:49:02.731822 00:13:10:42:b4:39 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 98: IP 192.168.7.47 > 192.168.7.255: icmp 64: echo request 
seq 7
11:49:03.731871 00:13:10:42:b4:39 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 98: IP 192.168.7.47 > 192.168.7.255: icmp 64: echo request 
seq 8
11:49:05.731774 00:13:10:42:b4:39 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 98: IP 192.168.7.47 > 192.168.7.255: icmp 64: echo request 
seq 10
11:49:06.731761 00:13:10:42:b4:39 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 98: IP 192.168.7.47 > 192.168.7.255: icmp 64: echo request 
seq 11


Looks legit to me.
Here's a slice of a tcpdump -i wl0 -n -e port 698 on the .47 (problematic) 
router:
11:50:47.960163 00:12:17:d0:0f:6b > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 958: 192.168.7.42.698 > 192.168.7.255.698: UDP, length 916
11:50:47.995540 00:0f:66:01:a5:2f > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 262: 192.168.7.21.698 > 192.168.7.255.698: UDP, length 220
11:50:48.065289 00:0f:66:01:a5:3e > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 822: 192.168.7.33.698 > 192.168.7.255.698: UDP, length 780
11:50:48.082916 00:13:10:42:b4:39 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 154: 192.168.7.47.698 > 192.168.7.255.698: UDP, length 112
11:50:48.180537 00:12:17:3e:c1:0e > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 494: 192.168.7.46.698 > 192.168.7.255.698: UDP, length 452
11:50:48.213605 00:13:10:42:b4:42 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 638: 192.168.7.50.698 > 192.168.7.255.698: UDP, length 596
11:50:48.272717 00:0f:66:01:a5:47 > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 1510: 192.168.7.30.698 > 192.168.7.255.698: UDP, length 1468
11:50:48.372274 00:13:10:e9:c7:7e > ff:ff:ff:ff:ff:ff, ethertype IPv4 
(0x0800), length 1498: 192.168.7.1.698 > 192.168.7.255.698: UDP, length 1456

Note that the 4th packet down is FROM the .47 router.  Doesn't appear to be 
any different than any other packet.  :(

John Gorkos

On Wednesday 12 July 2006 11:38, Thomas Lopatic wrote:
> Hey John.
>
> Could you perform another tcpdump on the problematic router, this time
> with the "-e" option, so that we can see the destination Ethernet
> address that outgoing OLSR HELLOs carry? Let's make sure that it really
> is the Ethernet broadcast address. Let's then compare it to the Ethernet
> address that outgoing ICMP Echo messages of the broadcast ping carry.
>
> -Thomas
>
> _______________________________________________
> olsr-users mailing list
> (spam-protected)
> https://www.olsr.org/mailman/listinfo/olsr-users