Recommended Posts

I have native IPv6 PPPoE service with my ISP and am having some issues with addresses assigned to my workstations becoming "Deprecated" when they are left inactive/in sleep for several hours (see the image below).

M0sIf.png

I'm not familiar with what "Deprecated" even means in this case, is this similar to a lease expiring?

Unfortunately, ipconfig /release and /renew don't seem to work for the IPv6 address, and the only way to grab a new address is to disable and re-enable IPv6 on the connection.

Some extra info:

- I was issued a /64 from my ISP.

- I'm using a WRT54GL loaded with Tomato/MLPPP/IPv6 (a custom distro of Tomato/MLPPP developed by my ISP to include IPv6 support. It doesn't support DHCPv6, ip6tables or anything like that yet.)

This is what the config looks like...

1FR8F.png

(Obviously, I replaced the Xs with the correct values)

- Workstations are all running Windows 7, one of which is freshly formated.

Any thoughts? Or does this just seem like shoddy implementation of IPv6 support in Tomato?

Link to comment
https://www.neowin.net/forum/topic/917904-ipv6-address-becomes-deprecated/
Share on other sites

  On 07/07/2010 at 05:14, The_Decryptor said:

Something is causing it to think the address is going to become invalid, so it's deprecating it.

Do you know exactly what software is on the firmware? My OpenWRT install doesn't suffer from this issue.

I'm not sure actually. Here's the respective thread about it at Broadband Reports, but little information is provided: http://www.dslreports.com/forum/r23849317-IPv6-beta

Is your OpenWRT config for native IPv6 service or are you using a tunnel?

I'm using a static tunnel, but due to how it's configured it shows up as a native v6 interface to the router, so I use the same config options as I would for native IPv6 from the ISP.

From a quick reading of that thread, it seems the firmware uses radvd, which is also what I'm using on my router.

  • 3 weeks later...

"Unfortunately, ipconfig /release and /renew don't seem to work for the IPv6 address"

thats because that is for IPv4

Options:

/? Display this help message

/all Display full configuration information.

/release Release the IPv4 address for the specified adapter.

/release6 Release the IPv6 address for the specified adapter.

/renew Renew the IPv4 address for the specified adapter.

/renew6 Renew the IPv6 address for the specified adapter.

/flushdns Purges the DNS Resolver cache.

/registerdns Refreshes all DHCP leases and re-registers DNS names

/displaydns Display the contents of the DNS Resolver Cache.

/showclassid Displays all the dhcp class IDs allowed for adapter.

/setclassid Modifies the dhcp class id.

/showclassid6 Displays all the IPv6 DHCP class IDs allowed for adapter.

/setclassid6 Modifies the IPv6 DHCP class id.

Do people even bother to use a /? on a command when they don't know its options?

  On 27/07/2010 at 12:45, BudMan said:

Do people even bother to use a /? on a command when they don't know its options?

Did someone **** on your Wheaties this morning, BudMan? :p

Good info, as always, though! I wouldn't have realized that the command wouldn't work on IPv6.

/release6 and /renew6 didn't occur to me since this is SLAAC and not DHCP. I'll see if it helps in my environment, though it doesn't address the underlying issue. Having to /release6 and /renew6 every time after waking from sleep isn't a solution.

I'm running DD-WRT, which also uses radvd. I tried decreasing the RA send interval to 4 seconds. Windows processes the RA and updates the valid lifetime for the address (verified with netsh), but the address still shows deprecated and isn't used for new connections.

The_Decryptor, can you share your radvd config?

FWIW, /release6 and /renew6 doesn't seem to help anyway. Afterwards, the SLAAC addresses are still deprecated:

C:\Windows\system32>netsh int ipv6 show addr

Interface 9: Wireless Network Connection

Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Temporary  Deprecated   23h59m57s   3h59m57s 2607:f068:ffff:ffff:ffff:ffff:dab1:2eee
Public     Deprecated   23h59m57s   3h59m57s 2607:f068:ffff:ffff:ffff:ffff:79b1:3ce
Other      Preferred     infinite   infinite fe80::ffff:ffff:79b1:3ce%9

Despite the preferred life at 4 hours.

I don?t think it has anything to do with your firmware, did you upgraded or downgraded it recently? If yes, that might be the cause of it. If you didn?t do anything to it, I believe that there is something with you router; you might want to try it out at another place using the same router. You should try it out too with a different router as well to see the results. It might give you an idea related to it.

  On 28/07/2010 at 16:24, BudMan said:

Um -- then why did you bring it up?

"Unfortunately, ipconfig /release and /renew don't seem to work for the IPv6 address"

I brought it up, not realjerimiah.

Thanks for the tip though, it never occurred to me that there would be separate commands to refresh IPv4 and IPv6 addresses individually. But, hey, now I know, always check /?.

  On 29/07/2010 at 00:56, commando677 said:

Why not just use IPv4 for your internal network and avoid all the problems, just because your router gets assigned an IPv6 doesn't mean all your internal clients need IPv6.

My network is running both IPv4 and IPv6. I'm trialling IPv6 just for the hell of it.

  • 1 month later...

I've been able to confirm that this only happens when the address expires while the system is suspended. IOW, I can leave the system running and it processes RAs normally and the address is never deprecated. I can also suspend and resume before the preferred life expires and the system will continue to process RAs normally and update the valid lifetime.

  • 6 months later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.