I thought a packet trace might help, so I updated bug report 4612 with the following information (posting here also for those of you who are interested):
Scenario: Internet <----> WRT54GS <--[wireless]--> SB3 <--[wired]--> Mac mini Mac addresses: WRT54GS wireless interface: 00:12:17:19:79:c1 SB3 Bridge: 00:04:20:06:3D:CD Mac Mini: 00:16:cb:a7:27:8a Upon executing "ping6 www.kame.net", and after successful DNS resolution (using IPv4), the mini sends out a neighbor soliciation looking for it's router (Note this is sent to a IPv6 multicast address, which is mapped to a MAC multicast address 33:33:ff....). This is as seen using tcpdump on the mini: 08:35:42.043139 00:16:cb:a7:27:8a > 33:33:ff:19:79:c1, ethertype IPv6 (0x86dd), length 86: 2001:618:400:29a8:216:cbff:fea7:278a > ff02::1:ff19:79c1: ICMP6, neighbor solicitation, who has fe80::212:17ff:fe19:79c1, length 32 The WRT sees (using tcpdump on WRT) this packet (Note WRT sees packet arriving from SB3's bridge MAC addr): 08:35:42.186342 00:04:20:06:3d:cd > 33:33:ff:19:79:c1, ethertype IPv6 (0x86dd), length 86: 2001:618:400:29a8:216:cbff:fea7:278a > ff02::1:ff19:79c1: icmp6: neighbor sol: who has fe80::212:17ff:fe19:79c1 WRT immediately replies with a unicast IP neighbor advertisement (the reply) to the mini's MAC addr: 08:35:42.186790 00:12:17:19:79:c1 > 00:16:cb:a7:27:8a, ethertype IPv6 (0x86dd), length 86: fe80::212:17ff:fe19:79c1 > 2001:618:400:29a8:216:cbff:fea7:278a: icmp6: neighbor adv: tgt is fe80::212:17ff:fe19:79c1 This unicast IPv6 neighbor advertisement never arrives at the mini, so I assume it is dropped by the SB3 bridge. -- smagnuson ------------------------------------------------------------------------ smagnuson's Profile: http://forums.slimdevices.com/member.php?userid=9124 View this thread: http://forums.slimdevices.com/showthread.php?t=30815 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
