On Thu, Nov 17, 2016 at 2:57 PM, Jan Danielsson <jan.m.daniels...@gmail.com> wrote: > On 2016-11-17 22:36, Andy Ruhl wrote: >>> - The router can ping6 the host1's IPv6 address. >> >> I'm not really sure if this is relevant, but what source IP are you >> using when this happens? Can you force it to be the external global >> address? > > Using -S of ping6? > > router$ ping6 -S <external global address> <host1> > > .. seems to work fine. > > I honestly don't know what -I is supposed to do, and if it's at all > relevant, but: > > router$ ping6 -I re0 <host1> > > .. yields "ping6: sendmsg: No route to host". (Maybe it's grabbing > the link-local address?)
Packets going out but not coming back seems to be the key. IPv6 likes to have ICMP enabled for path mtu discovery, might look into that. Also wondering if there is some issue receiving traffic, like you're firewalled? If you don't see ping replies they could be getting dropped before you can see them. Woud be nice to confirm by sniffing the outside interface somehow. Seems like not a forwarding issue like you say if you can ping the outside global address. Andy
