Topic 'Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used' in forum 'AT&T U-verse' - dslreports.com

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Tue, 13 Jun 2017 11:14:52 EDT

sandman_1 posted :

Anyone else with merlin firmware and AT&T with working native?

There is a post by sandman_1 in this thread saying his Asus router works in native mode, but he has a NVG599 and is bypassing it somehow

"I don't have my NVG599 hooked up, bypassed with a switch and powered off"

I am using a managed switch and VLAN to bypass the gateway. There is a thread here on how to do it. My NVG599, isn't even powered on. I just use it to authenticate and once it does that then I just physically swap the cables. Super simple...

I have the Merlin firmware 380.59.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 21:44:33 EDT

Jim721 posted : I would also like to try out the new 210 but as of yet it's not available here. As far a pass through on the Asus as I said before be careful you have no active firewall using that mode. Not sure if this may or may not be a security issue.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 21:20:51 EDT

sean8102 posted :

said by Jim721:

I am using a 599 in Pass through mode and a Asus RT-AC3100 router and i have no issues with IPv6 using Native mode on the Asus router. What i do notice is that the working v6 connection is not real time, it takes about 5 or 10 minutes then IPv6 works perfectly from then on. I have a uptime of days and weeks no issues.

Yeah I tried waiting over a hour with it on native mode. Never got ipv6 connectivity. When I put the Asus in ipv6 passthrough mode I get ipv6 connectivity instantly. So I'm pretty sure its something to do with the 5268AC gateway not the Asus router.

Like I've said thankfully passthrough mode works perfectly so I guess it dose not matter to much. If AT&T would let me have a BGW-210 I'd change gateways but I'll stick with the 5268 until then.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 20:48:30 EDT

Jim721 posted : I am using a 599 in Pass through mode and a Asus RT-AC3100 router and i have no issues with IPv6 using Native mode on the Asus router. What i do notice is that the working v6 connection is not real time, it takes about 5 or 10 minutes then IPv6 works perfectly from then on. I have a uptime of days and weeks no issues.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 18:17:06 EDT

sean8102 posted :

said by Napsterbater:

Anyone else with merlin firmware and AT&T with working native?

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 18:10:23 EDT

sean8102 posted :

said by Napsterbater:

I bet the Asus is not responding to sothing like Neighbors Solicitation

I found this in the settings, but maybe its not working correctly. One again thanks for your help!

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 17:58:21 EDT

Napsterbater posted : I bet the Asus is not responding to sothing like Neighbors Solicitation or one of the other processes either at all or not correctly. On mobile might look deeper into the PD process later.

Yeah the 5268AC setting wouldn't matter. It seems to do anything correctly. Based on others success.

Somthing with the Asus is not correct though.

Anyone else with merlin firmware and AT&T with working native?

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 17:52:44 EDT

sean8102 posted :

said by Napsterbater:

said by sean8102:

"Jun 12 14:32:25 6relayd[13438]: Failed to relay to 2600:1700:d750:2a80:fa32:e4ff:fe51:20%br0 (Network is unreachable)"

Any kind of Ping Block or "Stealth" option anything on the ASUS?

In theory this shouldn't matter, but....

Just took a look through all the config pages of the Asus. I already had it set to respond to ping requests, and I didn't see any sort of "Stealth" option.

Took a look on the 5268AC for the heck of it and it dose have a "Stealth Mode" option enabled under the firewall options. I don't know if that matters or not but I gave it by switching it off and it still didn't work.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 17:35:51 EDT

Napsterbater posted :

said by sean8102:

"Jun 12 14:32:25 6relayd[13438]: Failed to relay to 2600:1700:d750:2a80:fa32:e4ff:fe51:20%br0 (Network is unreachable)"

Any kind of Ping Block or "Stealth" option anything on the ASUS?

In theory this shouldn't matter, but....

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 17:29:42 EDT

sean8102 posted : The reboot was no luck :(

I found this in the link tree part of the 5268AC gui. Could "prefix_spread" being set to 0/disabled have anything to do with it? I know next to nothing about all this ipv6 stuff lol.

Also I found this in the log of the Asus router when I tried native ipv6 again.
"Jun 12 14:32:25 6relayd[13438]: Failed to relay to 2600:1700:d750:2a80:fa32:e4ff:fe51:20%br0 (Network is unreachable)"

This isn't a big deal by any means, I'm thankful it works perfectly in "Passthrough" mode. Still appreciate the help! I'm mainly just curious why it wouldn't work with native. I saw a post by someone here with a Asus router and his works with native mode, but I think they have a NVG599.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 17:22:39 EDT

Napsterbater posted :

said by maartena:

In a nutshell, it utilizes the AT&T DHCPv6 server to issue IPv6 addresses to devices in your network. Your router basically passes requests for IP's through to AT&T so they can decide what unique IP you will get on that device.

I believe this is the same as what PFSense calls "track interface" on the LAN side, basically tracking whatever the WAN interface is doing, with the WAN interface set to DHCPv6.

No what pfsense (and any normal router) does with track interface is based on DHCP-PD working, it gets a Delegated Prefix form the upstream devices and uses it for downstream interfaces. Note these prefixes would be diffrent. Which is what the native option should be on the Asus.

This (passthrough) seem more like a IPv6 bridge then anything, supported by the fact there are no LAN IPv6 prefixes listed in the Asus when set to passthrough.

said by maartena:

You need such a setting if you are utilizing your own router behind AT&T's router.

The AT&T router support DHCP-PD, you should not need passthrough.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 17:14:25 EDT

maartena posted :

said by Napsterbater:

I can't seem to find any info on what "Passthrough" entails, based on you pictures it seems it bridges IPv6 from WAN to LAN, which I guess works, but curious why Native is not able to get a PD from the 5268AC.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 17:05:36 EDT

sean8102 posted :

said by Artakamoose:

A couple of thoughts...

1) Are you running the stock ASUS firmware or Merlin? Whenever I've had an ASUS, I've always found Merlin's firmware to be much better. ASUS even rolls some of his changes into the stock firmware. I seem to remember having IPv6 problems with the stock firmware on my old N66U, and then Merlin got it working; but that was a few years ago.

2) Check this out.
»techreport.com/forums/vi ··· t=102404
These people reported success with the Native setting only after rebooting the router. Merely changing the setting didn't work.

Yeah I'm using the latest version of Merlin. I'll give rebooting a try. Didn't think about it because the router seems to partially reboot when I change the ipv6 settings. Gonna crack me up if this makes it work :P

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 17:00:34 EDT

Artakamoose posted : A couple of thoughts...

1) Are you running the stock ASUS firmware or Merlin? Whenever I've had an ASUS, I've always found Merlin's firmware to be much better. ASUS even rolls some of his changes into the stock firmware. I seem to remember having IPv6 problems with the stock firmware on my old N66U, and then Merlin got it working; but that was a few years ago.

2) Check this out.
»techreport.com/forums/vi ··· t=102404
These people reported success with the Native setting only after rebooting the router. Merely changing the setting didn't work.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 16:06:49 EDT

sean8102 posted :

said by Napsterbater:

said by sean8102:

I'll just leave the Asus ipv6 option on passthrough instead of native since that dose work and gets ipv6 connectivity on everything.

Oh i Misunderstood, I thought you meant passthrough on the 5268AC.

I can't seem to find any info on what "Passthrough" entails, based on you pictures it seems it bridges IPv6 from WAN to LAN, which I guess works, but curious why Native is not able to get a PD from the 5268AC.

Yeah I haven't been able to find any info on what exactly the ipv6 passthrough option on the Asus router dose. But for whatever reason it makes ipv6 work somehow and the native option dose not.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 15:50:34 EDT

Napsterbater posted :

said by sean8102:

I'll just leave the Asus ipv6 option on passthrough instead of native since that dose work and gets ipv6 connectivity on everything.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 15:42:14 EDT

sean8102 posted :

said by Napsterbater:

said by sean8102:

Passthrough mode on the router will make it work but I figured native should work now that I have dual stack.

If using a 2nd router you should want passthough anyways no?

Maybe the 5268AC wont sub delegate its prefixes without passthrough. I cant test this maybe someone else has more info.

IDK lol. I have ethernet going from the 5268AC to the WAN port of the Asus router. On the 5268AC I applied DMZ+ to the Asus router. I'll just leave the Asus ipv6 option on passthrough instead of native since that dose work and gets ipv6 connectivity on everything. This is the ipv6 info the Asus gets when its ipv6 is set to passthrough.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 15:28:55 EDT

Napsterbater posted :

said by sean8102:

Passthrough mode on the router will make it work but I figured native should work now that I have dual stack.

If using a 2nd router you should want passthough anyways no?

Maybe the 5268AC wont sub delegate its prefixes without passthrough. I cant test this maybe someone else has more info.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 15:24:57 EDT

sean8102 posted :

said by sandman_1:

After I ran that speed test, for some reason I lost IPv6 even though everything was showing connected in that respect. I got it working again and got similar results with the same server in GA.

For some reason even though my 5268AC is now showing native dual stack ipv6, I still can not get ipv6 to work with my Asus RT-AC88U if its set to native ipv6 mode. Passthrough mode on the router will make it work but I figured native should work now that I have dual stack.

This is what the 5268AC shows for my ipv6 info

Dual-Stack IPv6 Internet Connection
Type Value
Dual-Stack IPv6 Internet Address 2001:506:7d75:2a8::1
Dual-Stack IPv6 Default Gateway fe80::2d0:f6ff:feac:cd80
Dual-Stack IPv6 Delegated Prefix 2600:1700:d750:2a80::/60

The screenshots are what I get on my router, its like its not pulling the right info from the 5268AC or something. IDK I'm a newb to the ipv6 stuff.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 14:44:55 EDT

sean8102 posted :

said by Napsterbater:

Did you blank out the IPv6 Dual Stack Internet address? You need to blank out the prefix. The Internet address is useless anyways as its blocked from sending or receiving traffic from off ATT network.

Ah thank you for the tip. Will do.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 14:42:22 EDT

Napsterbater posted : Did you blank out the IPv6 Dual Stack Internet address? You need to blank out the prefix. The Internet address is useless anyways as its blocked from sending or receiving traffic from off ATT network.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 14:35:29 EDT

sean8102 posted : My gateway just changed over to native dual stack ipv6 :)

I had the 6rd ipv6 already working with my Asus router it just had to be in pass through mode. I did do the firmware upgrade to my 5268AC manually a while ago, but haven't had any issues with it.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 12:37:05 EDT

maartena posted :

said by sean8102:

I have the 5268AC gateway (firmware 10.5.6.529428-att). I'm going to try again later but I could not get ipv6 connectivity with my Asus router set to native ipv6. I have my Asus set to passthrough ipv6.

As for speed my tier is 100 down 20 up so it seems to not be impacting performance at all.

Not all areas might have native dual stack ipv6 deployed yet.... Did you get the firmware from AT&T or did you have to update manually?

If you updated manually, you may update to a firmware version that contains functionality your local area hasn't been prepared for.... so I would always wait on the official firmware rollouts, as they may flip a switch on the network at that point too.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Mon, 12 Jun 2017 10:18:25 EDT

mdpeterman posted : Downgraded firmware to 9.1.6h1d25 and now 6rd is working perfectly from my cascaded router. Clearly the new NVG599 firmware blocks (well at lest can't handle) protocol 41 traffic from the "LAN" side... Oh well I'll just keep downgrading for now.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Sat, 10 Jun 2017 14:34:50 EDT

Napsterbater posted : Did you get the firmware yet?

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Sat, 10 Jun 2017 14:33:50 EDT

Napsterbater posted : So that would still be 6rd service.. And it's 64 becuase your router is requesting a 64 from the gateway or the gateway only gives out a 64 from its 60..

In theory the switch from 6rd to Native on the Gateway should not change using Native on the 2rd router.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Sat, 10 Jun 2017 13:44:03 EDT

Jim721 posted : I am also connected using the native tab in my Asus router but the gateway still says 6rd. My lan prefix length shows 64 not 60. Every thing else is the same as above except i use Google v6 dns servers.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Sat, 10 Jun 2017 12:15:51 EDT

mdpeterman posted : I don't believe native v6 is available in my area yet. When I go into the WebUI the IPv6 Type is still listed as "6rd" on my gateway.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Sat, 10 Jun 2017 11:50:28 EDT

sandman_1 posted : After I ran that speed test, for some reason I lost IPv6 even though everything was showing connected in that respect. I got it working again and got similar results with the same server in GA.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Sat, 10 Jun 2017 11:33:49 EDT

sean8102 posted :

said by sandman_1:

said by maartena:

said by mdpeterman:

Has anyone had success getting AT&T to replace an NVG599 with a 5268AC? I figure it's worth a try to see if I can get 6rd working behind it since it sure as heck won't work with the 599 anymore...

You should not need 6rd anymore with dual stack. Just DHCPv6 should work fine. IPv6 on dual stack does work here (although I do have a 5268AC), it is just absolutely worthless. The routing sucks, the speed sucks, AT&T has a lot to learn when it comes to IPv6.

I don't have my NVG599 hooked up, bypassed with a switch and powered off, but had 6rd setup on my Asus router. I always got horrible results on speed tests with 6rd but since I set it to "Native", I have noticed a big improvement. Hell, I was lucky to break 100Mbps on 6rd!

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Sat, 10 Jun 2017 11:28:27 EDT

sandman_1 posted :

said by maartena:

said by mdpeterman:

Has anyone had success getting AT&T to replace an NVG599 with a 5268AC? I figure it's worth a try to see if I can get 6rd working behind it since it sure as heck won't work with the 599 anymore...

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Sat, 10 Jun 2017 03:34:19 EDT

sean8102 posted :

said by Jim721:

I'm using the 599 with the new firmware and have no issues with IPv6 and my own router in fact it works better then ever.

Same here. I just put my Asus RT-AC88U ipv6 mode to "passthrough" and its working perfectly with my 5268AC. I still have 6rd ipv6, not native dual stack yet. It seems this latest firmware for the 5268AC (10.5.6.529428-att) did something to let this work, because I tried and tried a few months ago and could never get ipv6 to work when using my own router. Glad I decided to hook the asus back up and give it another shot :)

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Sat, 10 Jun 2017 03:17:07 EDT

maartena posted :

said by mdpeterman:

Has anyone had success getting AT&T to replace an NVG599 with a 5268AC? I figure it's worth a try to see if I can get 6rd working behind it since it sure as heck won't work with the 599 anymore...

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Fri, 09 Jun 2017 06:17:49 EDT

gadawg posted : Call customer service and tell them you want a that gateway. Since the 599 is an older gateway there may not be any left where it ships from. No guarantee of what model you get.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Thu, 08 Jun 2017 22:53:32 EDT

mdpeterman posted : Has anyone had success getting AT&T to replace an NVG599 with a 5268AC? I figure it's worth a try to see if I can get 6rd working behind it since it sure as heck won't work with the 599 anymore...

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 22:39:17 EDT

Kett2000 posted :

said by mdpeterman:

Yeah that would be great except delegated prefix only delegates a /64 prefix good for one subnet. I have 7 different subnets I need /64s for, so I needed to setup my own 6rd tunnel with a /60 so I could give all of my networks v6 addressing.

Good point. I've successfully used (2) /64 delegated prefixes from the NVG599 to two separate routers assigned with static IPs, but I didn't try any more than that. You've got a unique setup going on there.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 22:35:16 EDT

mdpeterman posted : Yeah that would be great except delegated prefix only delegates a /64 prefix good for one subnet. I have 7 different subnets I need /64s for, so I needed to setup my own 6rd tunnel with a /60 so I could give all of my networks v6 addressing.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 22:24:44 EDT

Kett2000 posted :

said by mdpeterman:

v6 being enable on the NVG599 isn't the problem - that works fine. However I have a cascaded router with my static IP block behind it and was running a 6rd tunnel from my own router and that was working perfectly until this firmware update. That now doesn't work at all :(

I've got a NVG599 with the updated firmware, a routed static ip block, and a cascaded router using a static ip from a /29 static block and IPv6 works great. The router was previously configured to use a 6rd tunnel to provide IPV6 connectivity to devices behind my router, but that stopped working a few weeks ago. I setup the router to configure IPv6 automatically and it works great with a IPv6 Delegated Prefix Subnet obtained from the NVG599 and full routed IPV6 connectivity to all devices downstream of the router.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 21:20:56 EDT

mdpeterman posted : v6 being enable on the NVG599 isn't the problem - that works fine. However I have a cascaded router with my static IP block behind it and was running a 6rd tunnel from my own router and that was working perfectly until this firmware update. That now doesn't work at all :(

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 18:10:23 EDT

Jim721 posted : V6 enabled here im getting a constant 1ms to 2ms ping time to lan.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 09:42:58 EDT

mdpeterman posted : All services. IPv4 and v6. In fact it seems to me that something causes the NVG599s CPU to go to 100% because after I enable the 6rd tunnel, pinging the NVG599s LAN interface is 250-300ms every time. With the 6rd tunnel down its less than 1ms.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 07:53:10 EDT

Jim721 posted : unfortunately 6rd at this time.

10/10 for your IPv6 stability and readiness, when publishers are forced to go IPv6 only

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 06:58:16 EDT

Napsterbater posted :

said by Jim721:

I'm using the 599 with the new firmware and have no issues with IPv6 and my own router in fact it works better then ever.

6rd or Native on the gateway?

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 06:50:43 EDT

Jim721 posted : I'm using the 599 with the new firmware and have no issues with IPv6 and my own router in fact it works better then ever.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 01:59:08 EDT

Napsterbater posted :

said by mdpeterman:

anytime I try to bring up the 6rd tunnel from my router my latency goes to 300+ ms and I cant get more than about 750kbps through the NVG599

To/From an IPv6 service or in general?

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 01:55:04 EDT

mdpeterman posted : Even after a full reboot (unplug from wall and re-plug) and full factory reset, anytime I try to bring up the 6rd tunnel from my router my latency goes to 300+ ms and I cant get more than about 750kbps through the NVG599. Very disappointed AT&T screwed this up.
Moving my service to a new address in 3 weeks, so I will hope I can get a 5268AC from the installer when they come to do the install.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Wed, 07 Jun 2017 01:04:19 EDT

Napsterbater posted : Wow, utter fail..

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Fri, 02 Jun 2017 20:26:58 EDT

Jim721 posted : Glad your up and working. But doing a complete factory reset and reconfigure after a firmware (Code) update is always a good thing and personally i would not do it any other way. It clears out all the old settings to start over fresh. I do this with any device that i install firmware on. My 599 is working excellent with the new d80 code. :)

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Fri, 02 Jun 2017 20:22:02 EDT

Frodo posted : My 5031NV-030's firmware was also updated to version 10.5.1.525948-att overnight. This morning, I found IPv6 not working. For that matter IPv4 wasn't working either.

It was pulling a 6rd address and an IPv4 address. Another thing I noticed was that it wasn't picking up the computer name when looking at connected devices. It was showing mac address only. I rebooted, still no go.

So I unplugged that modem, and hooked the power supply to my other 5031NV with older firmware, and that one worked, right away.

Later on, I decided I would do a factory reset on the malfunctioning modem, thinking maybe some setting was incompatible with the new firmware. But, it came up and everything Ipv4 and 6rd was working, no reset necessary. It was once again displaying the computer name when looking at connected devices.

So, the last thing before the thing would work again was to disconnect power from the device.

Re: NVG599 Updated Overnight - IPv6 tunnel no longer can be used

Fri, 02 Jun 2017 17:11:42 EDT

m00ster posted : I was converted to dual stack, but upon the conversion ipv6 was broken. Conversing with ATT tells me that they are not ready for dual stack yet and still need to do more work on the network side.

not sue why they pushed the change to our devices when the underlying network changes weren't ready yet.

Their recommended solution is to disable ipv6 entirely.