Re: Disable IPv4-mapped - enforce IPV6_V6ONLY

2013-02-25 Thread Alexander Holler
Am 25.02.2013 14:23, schrieb David Laight: A proper solution would be to either return false if net.ipv6.bindv6only is true and optval is false (which would break downward compatibility because it wouldn't just be a default and setsockopt might return an error) or to introduce a new sysctl var

RE: Disable IPv4-mapped - enforce IPV6_V6ONLY

2013-02-25 Thread David Laight
> > A proper solution would be to either return false if net.ipv6.bindv6only is > > true and optval is false > (which would break downward compatibility because it wouldn't just be a > default and setsockopt might > return an error) or to introduce a new sysctl variable like > net.ipv6.bindv6onl

Re: Disable IPv4-mapped - enforce IPV6_V6ONLY

2013-02-25 Thread YOSHIFUJI Hideaki
Hello. Alexander Holler wrote: > Am 22.02.2013 16:21, schrieb Alexander Holler: >> Hello, >> >> I'm searching for a way to either enforce IPV6_V6ONLY or to block >> IPv4-mapped addresses on ipv6-sockets (e.g. by using iptables) system-wide. >> >> E.g. net.ipv6.bindv6only doesn't help if something

Re: Disable IPv4-mapped - enforce IPV6_V6ONLY

2013-02-23 Thread Alexander Holler
Am 22.02.2013 16:21, schrieb Alexander Holler: Hello, I'm searching for a way to either enforce IPV6_V6ONLY or to block IPv4-mapped addresses on ipv6-sockets (e.g. by using iptables) system-wide. E.g. net.ipv6.bindv6only doesn't help if something calls int v6on = 0; setsockopt(sd, IPPROTO_IPV6