After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 646703 - stateless autoconfigured IPv6 addresses persist after unplugging from network.
stateless autoconfigured IPv6 addresses persist after unplugging from network.
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.8.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2011-04-04 12:01 UTC by Gavin McCullagh
Modified: 2011-04-04 15:56 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screenshot of ifconfig before and after unplugging.... (7.81 KB, image/png)
2011-04-04 12:09 UTC, Gavin McCullagh 		Details

Description Gavin McCullagh 2011-04-04 12:01:25 UTC 
On a debian wkeezy system, if I:

1. Plug laptop into Network1 with IPv6 router advertisements enabled, see IPv6 
   address auto-configured correctly.
2. Unplug from Network1
3. Plug into another Network2.

My IPv6 address from Network1 will still be assigned to the interface, even though network manager will have removed the IPv4 address and rerun the DHCP configuration for IPv4.  This means that if I try to go to any IPv6 hosts, they will time out as I'm using an invalid address for this new network.

It seems logical that network-manager should do the same for IPv6 as it does for v4, ie remove the address when the link goes down and attempt to configure again as usual when plugged into the same or different network afterward.
Comment 1 Gavin McCullagh 2011-04-04 12:09:07 UTC 
Created attachment 185102 [details]
screenshot of ifconfig before and after unplugging....
Comment 2 Dan Williams 2011-04-04 15:27:07 UTC 
Which specific version of NetworkManager are you seeing this with?  0.8.2? 0.8.1?
Comment 3 Dan Williams 2011-04-04 15:31:46 UTC 
I think this is fixed by commit 36ef4a22 which was pushed for bug 641333.  I'll dupe to that bug for now, and you can test with 0.8.4 and if that does not fix the issue, lets re-open this bug.

*** This bug has been marked as a duplicate of bug 641333 ***
Comment 4 Gavin McCullagh 2011-04-04 15:36:22 UTC 
The exact debian package version is:

  0.8.3.998-1

which I presume is based on 0.8.3.

I should have stated also that if Network2 has router advertisements you end up with both IPv6 addresses, one for each network.

Gavin
Comment 5 Gavin McCullagh 2011-04-04 15:56:17 UTC 
Oh, my apologies, I didn't realise I had to configure network-manager to pay attention to IPv6.

It turns out that on Debian the default is "ignore", which leads to this result. If you change it to "Automatic" the address does get removed as it should.

Is it safe to leave "Automatic" on all the time or is there some down side to that?  Would it make sense for me to suggest to the packagers to make "Automatic" the default?

Sorry for wasting your time.

Gavin