Menu
What's new
By:
Filters Better Search

[RT-AC66U] no IPv6 data pass thru

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

C

Cliff Hood

New Around Here
I'm using the Asuswrt-Merlin software, 380.59, and trying to configure the IPv6 settings. From my Windows 10 system, I can ping the router and the gateway but nothing else (requests time out). From the router I can ping the Windows 10 system and ipv6.google.com.

The DNS seems to work in the Windows 10 system (I can get a resolution on ipv6.google.com).

Any suggestions on getting the data through the router?

I'm a Comcast customer with their modem set in bridging mode (I have a static IPv4 number.) The Comcast test site, test-ipv6-ct.comcast.net, does not detect an IPv6 number but the router received one and provided a number to the Windows 10 system.
 
What do the two links below tell you about your IPv6 connectivity?

http://test-ipv6.com/

http://ipv6-test.com/



Have you performed a full reset to factory defaults after flashing the 380.59 firmware along with a minimal and manual configuration to secure your router and connect to your ISP?

http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573


What browser are you using in Windows 10? Try IE and Edge.

Have you changed any settings on your router or the clients away from defaults?
 
The test-ipv6.com is the same as the test-ipv6-ct.comcast.net site (no IPv6 address detected).

The ipv6-test.com also cannot find a IPv6 address.

I use Firefox but Edge & Chrome yield the same results.

I have not reset between firmware versions. I've updated this router with each new firmware version since December 2014.
 
Cliff Hood said:
The test-ipv6.com is the same as the test-ipv6-ct.comcast.net site (no IPv6 address detected).

The ipv6-test.com also cannot find a IPv6 address.

I use Firefox but Edge & Chrome yield the same results.

I have not reset between firmware versions. I've updated this router with each new firmware version since December 2014.
Click to expand...


With two and a half years of updates on it, it is finally time for a full and proper reset. :)

http://www.snbforums.com/threads/rt-ac66u-slow-wan-to-lan.12973/page-3#post-269410

http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573

http://www.snbforums.com/threads/faq-nvram-and-factory-default-reset.22822/

http://www.snbforums.com/threads/user-nvram-save-restore-utility-r24.19521/


Take your time and do it methodically (taking notes along the way is also recommended). These type of glitches is exactly why a reset to factory defaults is needed. At the very least, it will rule out previous code and obsolete settings from interfering with the settings currently available. ;)
 
I ran through the first check list ...

3:57 reboot via gui, waited
4:05 flashed firmware, factory settings, powered down
4:08 reconfigured router (enough to get internet access), ran through check list
4:22 reboot via gui
4:27 reboot via gui
4:34 enabled ipv6, from router pinged ipv6.google.com, windows 10 system (ping worked for both)
4:38 from Windows 10 pinged router & gateway (both worked), pinged ipv6.google.com (DNS provided IP number, Request timed out) , no difference in IPv6 test web sites (IPv6 address found).

Not sure that was the problem.
 
This afternoon I pluged the Windows 10 system directly into the Comcast modem, bypassing the RT-AC66U.

I received an IPv6 number but no DNS Server numbers. After manually entering Google's IPv6 DNS Servers, I had internet connectivity. I had IPv4 disabled, so not all web sites were available.

Plugged it back into the RT-AC66U, kept the manually entered Google DNS IPv6 Severs, and I have no IPv6 connectivity.
 
okay.. Comcrap, AC66U router and windows 10. I don't know which cable modem your using, but the fact that you have to put it into a bridge mode tells me it's likely one of Comcast's leased Pieces of Fecal Matter.

Here's my configuration for my AC3200... The configuration page should be similar for the AC66: (These are google IPv6 DNS servers)

Connection Type: Native
DHCP-PD: Enable
Auto Configuration Setting: Stateless
Connect to DNS Server automatically: Disable
IPv6 DNS Server 1: 2001:4860:4860:0:0:0:0:8888
IPv6 DNS Server 2: 2001:4860:4860:0:0:0:0:8844
Enable Router Advertisement: Enable

With that configured, under Windows 10, here are the relevant results from "ipconfig /all" (Some items deleted for privacy)
Code: 
Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : (my local domain name)
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I218-V
   Physical Address. . . . . . . . . : 00-00-00-00-00-00
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . :  (valid global IP here)(Preferred)
   Temporary IPv6 Address. . . . . . : (valid global IP here)(Preferred)
   Link-local IPv6 Address . . . . . : (valid link local IP here)(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.50(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, July 18, 2016 8:27:49 PM
   Lease Expires . . . . . . . . . . : Tuesday, July 19, 2016 12:27:47 AM
   Default Gateway . . . . . . . . . : (link local IP of my router)%12
                                       192.168.1.1
   DHCP Server . . . . . . . . . . . : (ipv4 of my router)
   DHCPv6 IAID . . . . . . . . . . . : (deleted for privacy)
   DHCPv6 Client DUID. . . . . . . . : (deleted for privacy)
   DNS Servers . . . . . . . . . . . : (link local of my domain DNS server)%12
                                       (link local of my router)%12
                                       (ipv4 of my domain DNS server)
                                       (ipv4 of my router)
   Primary WINS Server . . . . . . . : (ipv4 of my domain server)
   NetBIOS over Tcpip. . . . . . . . : Enabled

You'll notice that my DNS settings are probably different from yours. The reason is that I override certain aspects of dnsmasq for my home domain. On that windows 10 box, try to use "nslookup" to see if you can resolve IPv6 addresses (such as ipv6.google.com.) With 'nslookup', you can force it to use a specific DNS server via the command "server xxxxx" So:

nslookup
server <put link local ipv6 of router here>
ipv6.google.com

You can also try to ping an IPv6 directly from the Win10 box. (just ping one of the google DNS servers listed above: ping 2001:4860:4860:0:0:0:0:8888)


For reference, my setup is an AC3200 using Merlin's current beta 2, a windows 10 box wired via a switch to the router, and two days ago a surfboard 6120 - which I replaced with an arris tm822g. (I own both cable modems... and absolutely REFUSE to allow any comcast owned equipment in my house that emits any wifi signal.)
 
Our modem, SMC's SMCD3G-CCR, is in bridging mode so we can have a static IP for our on-site web & mail servers. We thought our own router would be easier to manage when adding or changing servers behind the fire wall than dealing with the Comcast provided modem.

My settings in the AC66U match yours, including the DNS Servers.

Here is the result of my Windows 1o ipconfig /all command:

Code: 
Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : deleted
   Description . . . . . . . . . . . : Inventec PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 48-deleted-EB
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2601:deleted:184c(Preferred)
   Lease Obtained. . . . . . . . . . : Sunday, July 17, 2016 12:33:57 PM
   Lease Expires . . . . . . . . . . : Tuesday, July 19, 2016 10:09:20 PM
   IPv6 Address. . . . . . . . . . . : 2601:deleted:16c3(Preferred)
   Temporary IPv6 Address. . . . . . : 2601:deleted:4958(Preferred)
   Link-local IPv6 Address . . . . . : fe80:deleted:16c3%4(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.50(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, July 17, 2016 12:33:54 PM
   Lease Expires . . . . . . . . . . : Tuesday, July 19, 2016 6:33:59 PM
   Default Gateway . . . . . . . . . : fe80:deleted:a168%4
                                       192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.11
   DHCPv6 IAID . . . . . . . . . . . : 2deleted5
   DHCPv6 Client DUID. . . . . . . . : 00-deleted-EB
   DNS Servers . . . . . . . . . . . : 2001:4860:4860::8888
                                       2001:4860:4860::8844
                                       192.168.0.11
                                       192.168.0.13
                                       8.8.8.8
   NetBIOS over Tcpip. . . . . . . . : Enabled

When I issuer the command "ping ipv6.google.com" here is the result:

Code: 
Pinging ipv6.l.google.com [2607:f8b0:400e:c04::71] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2607:f8b0:400e:c04::71:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

I assume that this means the DNS function worked because a number was returned.

Although issuing the command "nslookup" gave this result:

Code: 
DNS request timed out.
  timeout was 2 seconds.
Default Server:  Unknown
Address: 2001:4860:4860::8888

It seems that I have the correct settings, does anyone else have an RT-AC66U working for IPv6?
 
Your default gateway is 192.168.0.1, but your DHCPv4 is 192.168.0.11. Is .1 your router and .11 an internal DHCP server? Is fe80:deleted:a168 the link local address of your router? Can you ping that address from your windows 10 machine?

Are you familiar with the "tracert" tool in windows 10? (It's similar to 'traceroute' in un*x.) In windows10, try:

tracert -6 -d 2001:4860:4860::8888

(None of this will solve your problem, but it might help to point to where the issue exists.)
 
My router is 192.168.0.1 and my IPv4 DHCP & DNS server is 192.168.0.11.

As I said before I can ping the default gateway "fe80:deleted:a168" and the router "2601:deleted:1" but nothing else.

The results from the "tracert" command look like this:

Code: 
Tracing route to 2001:4860:4860::8888 over a maximum of 30 hops

  1     4 ms    <1 ms    <1 ms  2601:deleted:1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
 
Some guesses...

"fe80:deleted:a168" and "2601:deleted:1" both belong to the router?

You seem to have DHCPv6 running and it's not running from the router (but from another machine.) If so, I'd suggest examining the routing table on the router to ensure packets coming from link local are getting routed across the ROUTER'S default gateway (which should point to a comcast address.) (unlike IPv4, routing tables with IPv6 can be annoying due to each interface having multiple IP addresses.)

Do you have shell access enabled for the router?

I know linux (runs on the router) has a /proc filesystem file for enabling/disabling ipforwarding. I'm not sure if there's one specific for IPv6. That might be one avenue of investigation.

I'd also examine the output of "ebtables -L" and "iptables -L" on the router to ensure nothing is blocking there on the bridge or netfilter.

Finally, if all else fails, I'd suggest saving your firmware configuration, disconnecting your DNS/DHCP server from the LAN, doing a factory reset on the router, and only plugging your Win10 machine into the router. Then do a quick and dirty config on the router to enable ipv6 and see if IPv6 forwarding is working then with the default config. Then, put one element of your desired configuration back at a time, testing after each step, to determine which step might be causing the problem.

(I know that the advice isn't very helpful, but I've run out of obvious ideas...)
 
The "fe80:deleted:a168" does not appear in the IPv6 set up page, I have no idea where it comes from. Thanks for looking at this for me.

I think I did the factory reset and minimal configuration a few messages back....

Here is the result of the ebtables & iptables command:

Code: 
ASUSWRT-Merlin RT-AC66U 380.59-0 Tue May 10 15:46:02 UTC 2016
administrator@RT-AC66U-A168:/tmp/home/root# ebtables -L
Bridge table: filter

Bridge chain: INPUT, entries: 0, policy: ACCEPT

Bridge chain: FORWARD, entries: 0, policy: ACCEPT

Bridge chain: OUTPUT, entries: 0, policy: ACCEPT

administrator@RT-AC66U-A168:/tmp/home/root# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
DROP       icmp --  anywhere             anywhere            icmp echo-request
DROP       all  --  anywhere             anywhere            state INVALID
ACCEPT     all  --  anywhere             anywhere            state RELATED,ESTAB                              LISHED
ACCEPT     all  --  anywhere             anywhere            state NEW
ACCEPT     all  --  anywhere             anywhere            state NEW
ACCEPT     icmp --  anywhere             anywhere            icmp !echo-request
DROP       all  --  anywhere             anywhere

Chain FORWARD (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere            state RELATED,ESTAB                              LISHED
DROP       all  --  anywhere             anywhere
DROP       all  --  anywhere             anywhere            state INVALID
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere            ctstate DNAT
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain FUPNP (0 references)
target     prot opt source               destination

Chain PControls (0 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere

Chain SECURITY (0 references)
target     prot opt source               destination
RETURN     tcp  --  anywhere             anywhere            tcp flags:FIN,SYN,R                              ST,ACK/SYN limit: avg 1/sec burst 5
DROP       tcp  --  anywhere             anywhere            tcp flags:FIN,SYN,R                              ST,ACK/SYN
RETURN     tcp  --  anywhere             anywhere            tcp flags:FIN,SYN,R                              ST,ACK/RST limit: avg 1/sec burst 5
DROP       tcp  --  anywhere             anywhere            tcp flags:FIN,SYN,R                              ST,ACK/RST
RETURN     icmp --  anywhere             anywhere            icmp echo-request l                              imit: avg 1/sec burst 5
DROP       icmp --  anywhere             anywhere            icmp echo-request
RETURN     all  --  anywhere             anywhere

Chain logaccept (0 references)
target     prot opt source               destination
LOG        all  --  anywhere             anywhere            state NEW LOG level                               warning tcp-sequence tcp-options ip-options prefix `ACCEPT '
ACCEPT     all  --  anywhere             anywhere

Chain logdrop (0 references)
target     prot opt source               destination
LOG        all  --  anywhere             anywhere            state NEW LOG level                               warning tcp-sequence tcp-options ip-options prefix `DROP '
DROP       all  --  anywhere             anywhere
administrator@RT-AC66U-A168:/tmp/home/root#
 
Another obvious thing:

On the router, "cat /proc/sys/net/ipv6/conf/all/forwarding". It should spit out a "1".
 
The windows firewall blocks IPv6 echo requests (ping) by default.....try disabling it and see if things change
 
If that was for me, that's not it as I do not use Windows, and don't even get a global link IP so it's not a firewall issue :)
 
Gee
Since you asked, I'll tell you none of the recommendations I received worked.

The problem is still open. (and it is not a Windows Firewall issue.)

Cliff
 
Thank you for the reply!
I wonder what makes our cases special since it works for others.
 
You must log in or register to reply here.

Similar threads

M
Can't ping ipv6 with all connected devices
Replies
0
Views
101
mdpatel9558
M
G
Client IPv6 unable to access internet on Windows Server 2019 Essentials with RT-AC86U AsusWRT Firmware 3.0.0.4.386_51925
Replies
2
Views
553
GAndreone
G
B
IPv6 and NextDNS Configuration Assistance Request
Replies
19
Views
993
easyriider
easyriider
zerowalker
RT-AC56U - Make DNS resolve DHCP client names?
Replies
2
Views
296
bennor
B
A
Suspicious Outgoing traffic on RT-AC86U
2 3
Replies
52
Views
3K
vaboro
vaboro
Similar threads
Thread starter Title Forum Replies Date
G AiMesh problems with ASUS RT-AC86U Firmware version 3.0.0.4.386_51925 and ASUS RT-AC66U B1 Firmware version 3.0.0.4.386_51685 ASUS AC Routers & Adapters (Wi-Fi 5) 3
pasha4ur Need help with restoration of AC66u B1 + last Merlin ASUS AC Routers & Adapters (Wi-Fi 5) 12
M RT-AC66U-B1 behind 4G mobole router in Bridge Mode ASUS AC Routers & Adapters (Wi-Fi 5) 1
L VPN - AC66U FW 382.52287 ASUS AC Routers & Adapters (Wi-Fi 5) 4
G Client IPv6 unable to access internet on Windows Server 2019 Essentials with RT-AC86U AsusWRT Firmware 3.0.0.4.386_51925 ASUS AC Routers & Adapters (Wi-Fi 5) 2

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 849 (members: 25, guests: 824)
Top