| 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
| ||
|
Date: Tue, 08 Feb 2011 23:12:30 +0100 From: Hadmut Danisch <hadmut@...isch.de> To: David Miller <davem@...emloft.net> CC: akpm@...ux-foundation.org, netdev@...r.kernel.org, bugzilla-daemon@...zilla.kernel.org, bugme-daemon@...zilla.kernel.org Subject: Re: [Bugme-new] [Bug 28282] New: forwarding turns autoconfiguration off On 08.02.2011 22:44, David Miller wrote: > > This is a case where we're probably just following what the RFC documents > state we should do, which means unless you can provide clear reference to > a specification that states we should behave otherwise this isn't changing. Could you cite where exactly this is stated in the RFC documents? (Would save me the time to dig through all the RFCs to find that particular statement and help avoid misunderstanding.) It appears to me to be a contradiction in terms. IPv6 interfaces must be able to have several IP addresses, and IPv6 does not have a default route (or 0::0/0). IPv6 interfaces are designed to participate in multiple independend logical networks (and several address ranges have been reserved for future extensions and uses). It therefore does not make sense if autoconfiguration for one network and routing for another are mutually exclusive. I'd like to check this (and maybe file a bug in the RFC). regards Hadmut -- 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