lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAF6-1L5cxguK8tHxjMACZJ8xNmAXLLXwP086eF4_SEctZdiZ3g@mail.gmail.com>
Date:	Thu, 14 Mar 2013 20:33:32 +0100
From:	Sylvain Munaut <s.munaut@...tever-company.com>
To:	netdev@...r.kernel.org
Cc:	lorenzo@...gle.com
Subject: Who/What is supposed to remove IPv6 address from interface when
 moving from one network to another ?

Hi,


In a nutshell, I'm experiencing the same behavior as described here
http://kerneltrap.org/mailarchive/linux-netdev/2010/10/26/6288280 ...
but 2.5 years later ...

When switching network, my interface doesn't necessarily goes down and
so IPv6 prefixes from my old location are kept, causing issues.

I read the thread above, but it just seem to "stop" without really a
solution ...

So what's the proper thing to do ?  How is it supposed to work ?
I searched for a while and except for the thread above, I couldn't
find any reference on whose responsibility it is to cleanup. Given the
kernel added the address itself, I'd tend to agree with the original
poster and that the kernel should handle the cleanup.


Cheers,

     Sylvain
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ