[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

IPv6 across suspend / resume -- who is responsible for flushing?



I suspended my laptop from my home (wifi) network which has native IPv6.
I resume it on the VIA train which does not have any IPv6.

I still have the prefix from home, so my laptop thinks it should still
use it.  I could turn the lifetime in the RA down a bunch, but that
seems wrong.

marajade-[~] mcr 10013 %sudo ip -6 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 2607:f0b0:f:4:205:4eff:fe4a:55da/64 scope global dynamic 
       valid_lft 85432sec preferred_lft 13432sec
    inet6 fe80::205:4eff:fe4a:55da/64 scope link 
       valid_lft forever preferred_lft forever

Whose fault is this?  Should the kernel aggressively do RS' when it
resumes?  Should some userspace thing run rdisc6 upon resume?    
Should the kernel flush IPv6 routes when the essid is changed?
Should NetworkManager be doing this?

I'm running squeeze, with 2.6.32-bpo.5-686.  (because I got here upgrade
From lenny+backports) 

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

Attachment: pgpdSNJfMGpeX.pgp
Description: PGP signature


Reply to: