| 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
| ||
|
Message-Id: <1446145782.493380.423921913.1E80CAD4@webmail.messagingengine.com> Date: Thu, 29 Oct 2015 20:09:42 +0100 From: Hannes Frederic Sowa <hannes@...essinduktion.org> To: Gilberto Bertin <gilberto.bertin@...il.com> Cc: netdev@...r.kernel.org Subject: Re: [BUG] Any-IP IPv6 support broken On Thu, Oct 29, 2015, at 19:58, Gilberto Bertin wrote: > > > On 29 Oct 2015, at 18:39, Hannes Frederic Sowa <hannes@...essinduktion.org> wrote: > > > > Try the loopback interface: > > > > ip -6 route add local abcd:abcd:abcd:abcd::/64 dev *lo* > > > > Otherwise packets should end up in neighbor subsystem and you don't want > > that, still. ;) > > > > Thanks for the reply. > > I know it’s working on the lo interface, but unluckily I need it on > other interfaces (and aliasing lo is not an option). > > Moreover: > - the IPv6 patch explicitly refers to the possibility to do this with > eth0 interface (i.e. it's not a lo-only feature) > - should it be consistent with the IPv4 behaviour? (or maybe it's not > supposed to work even with IPv4 addresses, and so this is a bug) The routing commands won't automatically enable the ndisc layer to answer neighbour discovery requests for that. The rule thing should work but your clients somehow need to route all packets over the box with the "anyip" route setup. Bye, Hannes -- 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