| 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: Fri, 10 Jan 2014 18:16:13 +0100 From: Hannes Frederic Sowa <hannes@...essinduktion.org> To: Nicolas Dichtel <nicolas.dichtel@...nd.com> Cc: sohny thomas <sohny.kernel@...il.com>, linux-kernel@...r.kernel.org, yoshfuji@...ux-ipv6.org, davem@...emloft.net, kumuda <kumuda@...ux.vnet.ibm.com>, netdev <netdev@...r.kernel.org> Subject: Re: ipv6: default route for link local address is not added while assigning a address On Fri, Jan 10, 2014 at 05:33:08PM +0100, Nicolas Dichtel wrote: > CC: netdev > > Le 10/01/2014 13:20, sohny thomas a écrit : > >Default route for link local address is configured automatically if > >NETWORKING_IPV6=yes is in ifcfg-eth*. > >When the route table for the interface is flushed and a new address is > >added to > >the same device with out removing linklocal addr, default route for link > >local > >address has to added by default. > I would say that removing the link local route but not the link local > address > is a configuration problem. > If you remove a connected route but not the associated address, you will > have > the same problem. We have some user accessible routes that are essential for IPv6 stack to work at all. So I don't know if I can agree with that. Maybe flush is a bit too aggressive? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists