[Babel-users] babels bug with uninitialized data somewhere?

[Matthieu Boutier]

Le 27 juin 2014 à 20:39, Juliusz Chroboczek a écrit :

>> the two captures are at: http://snapon.lab.bufferbloat.net/~cero2/babcap/
> 
> There's nothing obviously wrong.  Here's an example of a source-specific
> TLV (the one at time 06:20.362230 in the wifi capture):
> 
>  0d 16 02 20 00 00 06 40 65 8a 00 e0 40 00 20 01 04 70 82 36 02 61 02 00 
> 
>  Type = 0d (13)
>  Length = 16 (32)
>  AE = 02
>  Flags = 20
>  Plen = 00
>  Omitted = 00
>  Interval = 0640 (16s)
>  Seqno = 658a
>  Metric = 00e0 (224)
>  Prefix = (empty) (::)
>  Src Plen = 40 (64)
>  src Omitted = 00
>  src Prefix = 20 01 04 70 82 36 02 61 (2001:0470:8236:0261:0261::)
>  Sub-TLV: 02 00 (diversity empty)
> 
> Matthieu, do you have any ideas?

I don't see any problem with that TLV.

However, an interesting one is the last of that packet (babel.pcap):

00:05:20.966837 IP6 (class 0xc2, hlim 1, next-header UDP (17) payload length: 232) fe80::28c6:8eff:febb:9ff0.6696 > ff02::1:6.6696: [udp sum ok] babel 2 (220)
	Next Hop 172.21.2.1
	Router Id ea:94:f6:ff:fe:91:2e:a4
	Update 172.21.3.4/32 metric 143 seqno 53263 interval 160.0s
	Update 172.21.18.1/32 metric 143 seqno 53263 interval 160.0s
	Update 172.21.18.65/32 metric 143 seqno 53263 interval 160.0s
	Update 172.21.18.161/32 metric 143 seqno 53263 interval 160.0s
	Router Id ee:a8:6b:ff:fe:fe:09:a2
	Update/prefix fd20::2/128 metric 256 seqno 37335 interval 160.0s
	Update 172.21.50.2/32 metric 256 seqno 37335 interval 160.0s
	Update 172.21.51.1/32 metric 256 seqno 37335 interval 160.0s
	Router Id a2:21:b7:ff:fe:ac:e4:56
	SS-Update/src-prefix ::/0 from 2001:470:8236:261::/64 metric 224 seqno 25993 interval 160.0s
	SS-Update/prefix ::/0 from ::/128 metric 224 seqno 25993 interval 160.0s

The last line show we have sent a 'from ::/128', which is martian.

Who is fe80::28c6:8eff:febb:9ff0 ?  Does it have a config file ?  (If yes, which contents ?)

Matthieu