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, 22 Nov 2016 16:16:09 -0800 From: Alexei Starovoitov <alexei.starovoitov@...il.com> To: David Miller <davem@...emloft.net> Cc: david.lebrun@...ouvain.be, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Lorenzo Colitti <lorenzo@...gle.com>, Roopa Prabhu <roopa@...ulusnetworks.com>, Eric Dumazet <eric.dumazet@...il.com> Subject: Re: [PATCH net-next 1/1] ipv6: sr: add option to control lwtunnel support On Wed, Nov 16, 2016 at 8:32 AM, David Miller <davem@...emloft.net> wrote: > From: David Lebrun <david.lebrun@...ouvain.be> > Date: Tue, 15 Nov 2016 16:14:04 +0100 > >> This patch adds a new option CONFIG_IPV6_SEG6_LWTUNNEL to enable/disable >> support of encapsulation with the lightweight tunnels. When this option >> is enabled, CONFIG_LWTUNNEL is automatically selected. >> >> Fix commit 6c8702c60b88 ("ipv6: sr: add support for SRH encapsulation and injection with lwtunnels") >> >> Without a proper option to control lwtunnel support for SR-IPv6, if >> CONFIG_LWTUNNEL=n then the IPv6 initialization fails as a consequence >> of seg6_iptunnel_init() failure with EOPNOTSUPP: >> >> NET: Registered protocol family 10 >> IPv6: Attempt to unregister permanent protocol 6 >> IPv6: Attempt to unregister permanent protocol 136 >> IPv6: Attempt to unregister permanent protocol 17 >> NET: Unregistered protocol family 10 >> >> Tested (compiling, booting, and loading ipv6 module when relevant) >> with possible combinations of CONFIG_IPV6={y,m,n}, >> CONFIG_IPV6_SEG6_LWTUNNEL={y,n} and CONFIG_LWTUNNEL={y,n}. >> >> Reported-by: Lorenzo Colitti <lorenzo@...gle.com> >> Suggested-by: Roopa Prabhu <roopa@...ulusnetworks.com> >> Signed-off-by: David Lebrun <david.lebrun@...ouvain.be> > > Applied. ipv6 seems to be still broken in the latest net-next when CONFIG_LWTUNNEL is not set: # ping 127.0.0.1 ping: socket: Address family not supported by protocol # ping -4 127.0.0.1 PING localhost.localdomain (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64 time=0.067 ms it works with CONFIG_LWTUNNEL=y Roopa, David, please take a look. Thanks!
Powered by blists - more mailing lists