On Thursday 19 July 2007 14:56, Etaoin Shrdlu wrote: > IIUC, icmpv6 echo request packets enter the router/firewall from the > bond2 interface, and leave the box using the bond0 interface > (confirming that forwarding works). But, the router/firewall is trying > to get the link-layer address of the interface whose ipv6 global > address is dead:beef:2:136:204:23ff:fed7:e86a (thus an internal host), > but for some reason it sends these neighbor solicitation messages out > of the Internet interface. Not surprisingly, it gets no answers.
More precisely, it seems that these neighbor solicitation messages come from the far end router, like it somehow believes that your internal host is on its same subnet, and is trying to resolve its ipv6 address to its link layer address (similar to what ARP does in ipv4). Is fe80::214:f600:b67e:b4db the address of your provider's router? There could be a misconfiguration somewhere. -- [EMAIL PROTECTED] mailing list
