Project

General

Profile

Bug #9070

After performing in-place upgrade from 2.4.3-RELEASE-p1 to 2.4.4 DHCPV6 client fails to retireve a WAN address

Added by Tom Hebert 8 months ago. Updated 8 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
10/25/2018
Due date:
% Done:

0%

Estimated time:
Affected Version:
Affected Architecture:

Description

I upgraded my system a few days ago and realized last night that the hosts were no longer receiving IPV6 addresses. The ISP is Cox Communication using dual stack with IPV6 auto configuration and prefix delegation.

I tried everything, I could think of, (but I am not an expert in the internal settings for this router) to get IPV6 running on 2.4.4, with no joy. I restored the VM guest to a time before the upgrade and it's all back online.

For now, I will have to leave the system at 2.4.3 as IPV6 is actually quite important to us.

I am certainly willing to perform diagnostic tasks but do not assume I know where and how to collect various logs. It would be a simple matter for me to shutdown the VM hosting the router, take a snapshot and upgrade. I can always revert to the snapshot.

Any thoughts on what happened or how to proceed?

History

#1 Updated by Jim Pingle 8 months ago

  • Status changed from New to Feedback

Sounds like symptoms that others saw when using Hyper-V.

If you are using Hyper-V then this is a duplicate of #9019

Also available in: Atom PDF