SixXS::Sunset 2017-06-06

Netgear R8000 Router endpoint does not respond to IGMPv6 ping
[nz] Shadow Hawkins on Monday, 21 September 2015 07:07:02
Hi, I am replacing an Apple Airport Extreme with a Netgear Nighthawk X6 R8000 I have configured the router to bring up tunnel T41969 with 6rd (surprisingly simple) and the tunnel has come up and devices attached to the router are getting routed subnet addresses on R18205 and are working fine and are communicating on IPv6. I am using PoP nzwlg01 ( [AS18119]) The Live Tunnel Status shows "Up" The Netgear Nighthawk X6 R8000 is running the latest firmware V1.0.2.46_1.0.97 Pings to the subnet attached computer are answered. I'm not clear how to resolve this
$ ping6 -c 10 -s 56 2001:4428:24e::cd1e:788a:6886:5ea6 PING6(104=40+8+56 bytes) 2001:4d48:1337:5afe::2 --> 2001:4428:24e:0:cd1e:788a:6886:5ea6 64 bytes from 2001:4428:24e:0:cd1e:788a:6886:5ea6, icmp_seq=0 hlim=45 time=323.147 ms 64 bytes from 2001:4428:24e:0:cd1e:788a:6886:5ea6, icmp_seq=2 hlim=45 time=310.995 ms 64 bytes from 2001:4428:24e:0:cd1e:788a:6886:5ea6, icmp_seq=3 hlim=45 time=319.268 ms 64 bytes from 2001:4428:24e:0:cd1e:788a:6886:5ea6, icmp_seq=4 hlim=45 time=316.081 ms 64 bytes from 2001:4428:24e:0:cd1e:788a:6886:5ea6, icmp_seq=5 hlim=45 time=316.782 ms 64 bytes from 2001:4428:24e:0:cd1e:788a:6886:5ea6, icmp_seq=7 hlim=45 time=322.552 ms 64 bytes from 2001:4428:24e:0:cd1e:788a:6886:5ea6, icmp_seq=8 hlim=45 time=316.003 ms --- 2001:4428:24e::cd1e:788a:6886:5ea6 ping6 statistics --- 10 packets transmitted, 7 packets received, 30.0% packet loss round-trip min/avg/max/std-dev = 310.995/317.833/323.147/3.907 ms $ $ ping6 -c 10 -s 56 2001:4428:200:91::2 PING6(104=40+8+56 bytes) 2001:4d48:1337:5afe::2 --> 2001:4428:200:91::2 $ ping6 -c 10 -s 56 2001:4428:200:91::1 PING6(104=40+8+56 bytes) 2001:4d48:1337:5afe::2 --> 2001:4428:200:91::1 64 bytes from 2001:4428:200:91::1, icmp_seq=0 hlim=47 time=278.481 ms 64 bytes from 2001:4428:200:91::1, icmp_seq=1 hlim=47 time=278.433 ms 64 bytes from 2001:4428:200:91::1, icmp_seq=2 hlim=47 time=278.125 ms 64 bytes from 2001:4428:200:91::1, icmp_seq=3 hlim=47 time=278.262 ms 64 bytes from 2001:4428:200:91::1, icmp_seq=4 hlim=47 time=278.177 ms 64 bytes from 2001:4428:200:91::1, icmp_seq=5 hlim=47 time=279.134 ms 64 bytes from 2001:4428:200:91::1, icmp_seq=6 hlim=47 time=278.234 ms 64 bytes from 2001:4428:200:91::1, icmp_seq=7 hlim=47 time=278.206 ms 64 bytes from 2001:4428:200:91::1, icmp_seq=8 hlim=47 time=278.257 ms 64 bytes from 2001:4428:200:91::1, icmp_seq=9 hlim=47 time=278.292 ms $
Thanks for your help Robert Gray RJG4-SIXXS
Netgear R8000 Router endpoint does not respond to IGMPv6 ping
[ch] Jeroen Massar SixXS Staff on Monday, 21 September 2015 10:51:14
Likely firewalling options are quite limited in standard software, that is, if firewalling is the problem you would not be able to disable it. Check the FAQ: Tunnel endpoint didn't ping for a long list of things that could cause these kind of issues. If you want more control over the host, you'll have to upgrade it to a firmware that allows you to control things better. Currently only option on R8000 is DD-WRT and those firmware versions are still in beta, though they mostly work, just a few corner cases that are not completely happy.
Netgear R8000 Router endpoint does not respond to IGMPv6 ping
[nz] Shadow Hawkins on Saturday, 16 January 2016 05:10:07
Hi Robert Can you tell me what settings to put where; on the 6rd Tunnel page? Also will this give all devices connected to the R8000, their own IPv6 IP's etc? Thanks Justin.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker