Hey, thanks for the answers,
so .. I firstly got rid of the alias and the manual routes. 1.) "Can you ping your own IPv6 address ?" Yes i can. Works as expected. 2.) "tcpdump -ni vio0 -s 1500 icmp6" results in alot of "neigbor sol". 3.) "Who are you trying to ping?" I have a /64 for myself so I tried to ping google.com for example. 4.) "You must see them for your gateway" This i do not. When trying to ping google I see the echo requests for the IPv6 of google but not for my gateway. I haven't configured a gateway for IPv6 at all. That could be the problem ? Do I have to do that ? 5.) "ndp -a" I am missing the entry for my gateway completely. 6.) "netstat -s" Looks fine. No zeros. So I guess it has to do with my gateway that I haven't configured anywhere to act as one. When trying to add the gateway (which i learnt from looking at the tcpdump output) manually i get "network is unreachable". Hmm... Can you pull anything from that ? Regards, Stephan On 8/14/19 11:05 PM, gwes wrote: > > > On 8/14/19 2:36 PM, list wrote: >> My hostname.vio0 now looks like this: >> >> inet6 alias <IP>/64 >> !route add -inet6 default fe80::2de:361a:24aa:d7a6%vio >> When doing a "ifconfig vio0" I get: >> >> vio0: flags=8843 mtu 1500 >> >> [...] >> inet6 fe80::2de:361a:24aa:d7a6%vio0 prefixlen 64 scopeid 0x1 >> inet6 <configured IPv6> prefixlen 64 > Take the "alias" out of your inet6 line in your hostname.vio0 > > Since your interface is vio0 I am assuming you are running a > guest VM on a server. I am also assuming that ip4 traffic is passing. > > Your VM server should be sending you Route Advertisement messages. > You shouldn't have to set any route yourself. Doing so will confuse > things mightily. > > Can you ping your own ipv6 address? If not something is really strange. > > If you say > # tcpdump -ni -s 1500 icmp6 > > You should eventually see (lines wrapped) > > 13:17:46.508540 fe80::669e:f3ff:feec:fc7f > ff02::1: > icmp6: router advertisement [class 0xe0] > Along with > > 13:17:19.309191 your_gateway_ip6 > 2xxx0::1: > icmp6: neighbor sol: who has 2xxx0::1 > 13:17:19.311828 2xxx0::1 > 2xxx0::2: > icmp6: neighbor adv: tgt is 2xxx0::1 [class 0xe0] > > It may take up to 20 minutes to see these messages. > > If you never see any route advertisements your server isn't configured > to give you inet6 service. > > Who are you trying to ping? Someone on your /64 or someone outside? > You must see neighbor solicitation msgs if you try to ping someone > on your /64. You must see them for your gateway if you try to ping > someone outside. Keep the tcpdump running and do the pings from > another virtual terminal. > > If you say > # ndp -a > > You should see > > Neighbor Linklayer Address Netif > Expire S Flags > your_gateway 64:9e:f3:ec:fc:7f vio0 > 4s D R > your_hostname 52:54:00:27:22:43 vio0 > permanent R l > fe80::669e:f3ff:feec:fc7f%vio0 64:9e:f3:ec:fc:7f vio0 > 23h58m18s S R > fe80::bd8b:afb3:be72:bd06%vio0 52:54:00:27:22:43 vio0 > permanent R l > > If you say > # netstat -s > Among a ***lot*** of other statistics you should see something like > ip6: > 1312572 total packets received <<< > 907754 packets for this host <<< > 1107139 packets sent from this host <<< > ..... > icmp6: > 640 calls to icmp6_error > Output packet histogram: > unreach: 640 > echo reply: 1328 > multicast listener report: 6 > neighbor solicitation: 137965 > neighbor advertisement: 137761 > .... > Input packet histogram: > echo: 1328 > router advertisement: 56998 <<<< > neighbor solicitation: 137770 <<<< > neighbor advertisement: 137956 <<<< > > ..... > > The netstat -s output should show nonzero in the marked lines. > > If you CAN ping hosts on your /64 and you CAN'T ping anyone else > if you CAN ping your gateway as a last resort set your default > ipv6 route via that host. > > If things still don't work, excerpts of netstat -s > and the output from ndp -an and tcpdump -ni icmp6 should be informative. > > geoff steckel > > >
