[Olsr-dev] olsr strange behaving / nearly no outgoing packets
Henning Rogge
(spam-protected)
Wed Jun 27 15:36:32 CEST 2012
On 06/27/2012 03:10 PM, Bastian Bittorf wrote:
> facts: kernel 3.3.8 / 0.6.3-git_9f34036-hash_398b3410701eda6218b75f8541baaacd
>
> on an openwrt-box (brcm47xx/dell truemobile 2300) we
> cant make the daemon working. playing with tcpdump shows:
>
> we have incoming packets via lan/wifi from another boxes
> with same settings (but other hardware, same architecture e.g.
> linksys wrt54g, tplink1043nd) but:
>
> no outgoing packets
>
> except: 2 packets when we stop the daemon:
>
> (spam-protected):~ tcpdump -vv -ni $LANDEV port 698
> tcpdump: listening on eth0.1, link-type EN10MB (Ethernet), capture size 65535 bytes
> 14:56:22.703533 IP (tos 0xc0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 76)
> 10.63.17.46.698 > 255.255.255.255.698: [udp sum ok] OLSRv4, seq 0x8fdc, length 48
> TC-LQ Message (0xca), originator 10.63.17.46, ttl 255, hop 0
> vtime 576.000s, msg-seq 0x88c7, length 16
> advertised neighbor seq 0x0002
> Hello-LQ Message (0xc9), originator 10.63.17.46, ttl 1, hop 0
> vtime 144.000s, msg-seq 0x88c8, length 28
> hello-time 4.000s, MPR willingness 7
> link-type Lost, neighbor-type Not-Neighbor, len 12
> neighbor 10.63.9.33, link-quality 0.00%, neighbor-link-quality 0.00%
> 14:56:22.704176 IP (tos 0xc0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 76)
> 10.63.17.46.698 > 255.255.255.255.698: [udp sum ok] OLSRv4, seq 0x8fdd, length 48
> TC-LQ Message (0xca), originator 10.63.17.46, ttl 255, hop 0
> vtime 576.000s, msg-seq 0x88c9, length 16
> advertised neighbor seq 0x0002
> Hello-LQ Message (0xc9), originator 10.63.17.46, ttl 1, hop 0
> vtime 144.000s, msg-seq 0x88ca, length 28
> hello-time 4.000s, MPR willingness 7
> link-type Lost, neighbor-type Not-Neighbor, len 12
> neighbor 10.63.9.33, link-quality 0.00%, neighbor-link-quality 0.00%
Something fishy is going on with this dump.
These packets are the "tell your neighbors I am gone" packets, which are
sent during the shutdown before the sockets are closed.
Is "10.63.9.33" a correct neighbor? If yes, the Hello protocol was
running, which means there were some other packets being exchanged
through the mesh.
Henning Rogge
--
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Neuenahrer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961, Fax +49 228 9435 685
mailto:(spam-protected) http://www.fkie.fraunhofer.de
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6169 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20120627/dfa71190/attachment.bin>
More information about the Olsr-dev
mailing list