Re: Node soliciting neighbour twice, results in duplicate IPv6 address

Philipp Kern <[email protected]> Sun, 3 Jan 2016 11:10:41 +0100

Newsgroups	gmane.linux.debian.devel.ipv6
Organization	The Debian Project (http://www.debian.org)
Message-ID	<[email protected]>

Hi,

On Sun, Jan 03, 2016 at 10:48:13AM +1300, martin f krafft wrote:
> Attached are the two packet dumps, and here's a diff between them,
> with timestamps and identical stuff stripped:
> 
>   -Frame 1: 78 bytes on wire (624 bits), 78 bytes captured (624 bits) on interface 0
>   +Frame 2: 78 bytes on wire (624 bits), 78 bytes captured (624 bits) on interface 0
>   […]
>   -Ethernet II, Src: 28:d2:44:8c:05:bd, Dst: 33:33:ff:8c:05:bd
>   -    Destination: 33:33:ff:8c:05:bd
>   -        Address: 33:33:ff:8c:05:bd
>   -        .... ..1. .... .... .... .... = LG bit: Locally administered address (this is NOT the factory default)
>   -        .... ...1 .... .... .... .... = IG bit: Group address (multicast/broadcast)
>   +Ethernet II, Src: 28:d2:44:8c:05:bd, Dst: 28:d2:44:8c:05:bd
>   +    Destination: 28:d2:44:8c:05:bd
>   +        Address: 28:d2:44:8c:05:bd
>   +        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
>   +        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
> 
> Correct me if I am wrong, but that second frame should not be sent,
> right? Why would the node send a solicitation to itself?

wacky guess: This laptop does not have Intel AMT (sort of aka vPro)
enabled, right? If so, try turning it off.

What was actually solicited? 2001:4428:29c:0:2ad2:44ff:fe8c:5bd?
Link-local?

Kind regards
Philipp Kern

signature.asc (application/pgp-signature, 473 B)