Open GoogleCodeExporter opened 9 years ago
bump! any solutions?
Original comment by lifehack...@gmail.com
on 13 Jan 2014 at 8:45
Just chiming in here - same problem with RT-N56U_3.0.3.7-079_base. My settings
are as follows:
IPv6 Connection Type: Native DHCPv6
WAN IPV6 Settings: DHCPv6 (Stateful, IA-NA)
Get DNSv6 servers automatically: Yes
Get LAN IPv6 address via DHCPv6: Yes
Enable LAN Router Advertisement: Yes
Enable LAN DHCPv6 Server: No
The router itself gets a WAN IPv6, as well as a LAN IPv6 subnet. I can even
wget ipv6/ping6 websites from within the router. Clients behind (wired and
wireless) are getting IPv6 addresses via RA, and are getting assigned the
link-local IPv6 of the router (br0) as their default gateway, but they're not
able to browse IPv6. If I run a tcpdump on the WAN interface on the router, I
can see requests going out from the clients, but nothing is coming back in.
Original comment by meta...@gmail.com
on 19 Feb 2014 at 6:42
This is still broken in RT-N56U_3.0.3.8-081.
Original comment by meta...@gmail.com
on 12 Apr 2014 at 8:43
It works for me with Comcast under RT-N65U_3.0.3.8-081_base. Here are my
settings:
IPv6 Connection Type: Native DHCPv6
Get WAN IPv6 Address From Souce: From both sources
Enable Privacy Extensions (RFC 4941)? Yes
Get DNSv6 Servers Automatically? Enabled
Get LAN IPv6 Address via DHCPv6 IA-PD? Enabled
Enable LAN Router Advertisement? Enabled
Enable LAN DHCPv6 Server? No
After restarting the router and modem, it usually takes some time, maybe 5 to
10 minutes before my devices get IPv6 addresses.
Original comment by jdwhite9...@gmail.com
on 30 Apr 2014 at 1:49
Interesting - no go for me even using the same settings. Is your default route
a link local address?
Original comment by meta...@gmail.com
on 3 May 2014 at 12:06
How do you tell if it's a link local address?
Original comment by jdwhite9...@gmail.com
on 8 May 2014 at 7:24
[deleted comment]
[deleted comment]
Right-click on the network icon in the system tray, left-click on "Network and
Sharing Center" from resulting menu, left-click on network adapter indicated by
"Connections", then left-click on the "Details..." button. Towards the bottom
of the window that opens, there is an entry for "Link-local IPv6 Address". In
Internet Protocol Version 6 (IPv6), the address block fe80::/10 has been
reserved for link-local unicast addressing.
I have RT-N65U_3.0.3.8-081_full on my router behind an Arris TG852G gateway.
It is set for NAT & DHCP by default. I can get IPv6 addresses for all the
devices on my local network if I set my RT-N65U as an access point. When it is
set as a router, I have to set it as a DHCP server with NAT, or I don't get any
Internet connectivity. Even then, I get only IPv4.
May I suggest a "gateway" setting in addition to "Access Point" and "Router",
like dd-wrt?
Original comment by pcarlson...@gmail.com
on 8 May 2014 at 10:14
Under Network Connection Details tested with both a wired and a wireless
connection I'm getting:
IPv6 Address 2601:...
Temporary IPv6 Address 2601:...
Link-local IPv6 Address fe80:...
IPv6 Default Gateway fe80:...
IPv6 DNS Server (blank)
I hope that helps.
Original comment by jdwhite9...@gmail.com
on 12 May 2014 at 2:46
Your IPv6 DNS server line is empty? Assuming you're on Windows, what happens if
you do 'ping -6 google.com -n 5'?
Original comment by meta...@gmail.com
on 14 May 2014 at 8:38
IPv6 is now working for me as well, however, I get 2001:558:feed::1 &
2001:558:feed::2 in the IPv6 DNS server line. At least some of the following
seemed to help:
1) Connected computer directly to Xfinity gateway (mine is a TG852G) to get
Link-local IPv6 and Default gateway addresses.
2) Entered these values in the Gateway > Connection > Local IP Configuration
page of the TG852G.
3) On RT-N65U Advanced settings> LAN > Route, I enabled "Use DHCP Routes". IPv6
settings per "jdwhite9" post #4 above.
4) Powered off the RT-N65U, then switched on.
Result:
'ping -6 google.com -n 5'
Pinging google.com [2800:3f0:4001:814::1003] with 32 bytes of data:
Reply from 2800:3f0:4001:814::1003: time=207ms
Reply from 2800:3f0:4001:814::1003: time=187ms
Reply from 2800:3f0:4001:814::1003: time=186ms
Reply from 2800:3f0:4001:814::1003: time=185ms
Reply from 2800:3f0:4001:814::1003: time=172ms
Ping statistics for 2800:3f0:4001:814::1003:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 172ms, Maximum = 207ms, Average = 187ms
Thanks, jdwhite9!
Original comment by pcarlson...@gmail.com
on 21 May 2014 at 8:49
You're welcome pcarlson. I'm glad it helped.
When I try 'ping -6 google.com -n 5', it sometimes does not get a response from
the first ping attempt. The other 4 respond though.
I tried the command several times. Most of the time all 5 pings responded as
expected.
Original comment by jdwhite9...@gmail.com
on 22 May 2014 at 3:35
Original issue reported on code.google.com by
ceeKayyy...@gmail.com
on 30 Dec 2013 at 10:40