[Olsr-dev] os x issue help

Mark K. (spam-protected)
Sat Jan 10 14:30:28 CET 2009


Thanks for taking a look.  Here's the information you requested.

Here's the tcpdump from tap0.  Tap1 is the same with the ip changed.

07:27:18.371678 IP (tos 0x0, ttl 1, id 4960, offset 0, flags [none],  
proto UDP (17), length 48) 192.168.2.21.olsr > 192.168.2.255.olsr:  
[udp sum ok] OLSR, seq 0x7b7f, length 20
	Hello-LQ Message (201), originator 192.168.2.21, ttl 1, hop 0
	  vtime 20.000s, msg-seq 0x53a9, length 16
	  hello-time 2.000s, MPR willingness 3
07:27:18.372302 IP (tos 0x0, ttl 1, id 4960, offset 0, flags [none],  
proto UDP (17), length 48) 192.168.2.21.olsr > 192.168.2.255.olsr:  
[udp sum ok] OLSR, seq 0x7b7f, length 20
	Hello-LQ Message (201), originator 192.168.2.21, ttl 1, hop 0
	  vtime 20.000s, msg-seq 0x53a9, length 16
	  hello-time 2.000s, MPR willingness 3
07:27:18.372360 IP (tos 0x0, ttl 1, id 36435, offset 0, flags [none],  
proto UDP (17), length 48) 192.168.2.21.olsr > 192.168.2.255.olsr:  
[udp sum ok] OLSR, seq 0xbbac, length 20
	Hello-LQ Message (201), originator 192.168.2.21, ttl 1, hop 0
	  vtime 20.000s, msg-seq 0x53aa, length 16
	  hello-time 2.000s, MPR willingness 3
07:27:18.372916 IP (tos 0x0, ttl 1, id 36435, offset 0, flags [none],  
proto UDP (17), length 48) 192.168.2.21.olsr > 192.168.2.255.olsr:  
[udp sum ok] OLSR, seq 0xbbac, length 20
	Hello-LQ Message (201), originator 192.168.2.21, ttl 1, hop 0
	  vtime 20.000s, msg-seq 0x53aa, length 16
	  hello-time 2.000s, MPR willingness 3



And, for the olsrd.conf file.  I only changed the interface name and  
the broadcast address.  It's attached though.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: olsrd.conf
Type: application/octet-stream
Size: 7328 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20090110/779a429e/attachment.obj>
-------------- next part --------------




On Jan 10, 2009, at 3:45 AM, L. Aaron Kaplan wrote:

>
> I think I can reproduce it... hmmm... have to look deeper into that.
>
> a.
>



More information about the Olsr-dev mailing list