This is not related to IPv6 per se, but to java and/or the nettools maintainers that decided to SILENTLY switch off the transparent IPv6-to-IPv4 bridging
Comment net.ipv6.bindv6only = 1 in /etc/sysctl.d/bindv6only
Another one like that and I switch to Ubuntu ... I'm really getting tired with Debian maintainers of core packages that don't care at all about their users.
If you're:
- running production environment on Sid,
- not reading changelogs from updated packages
- throwing tantrums like this,
then you're getting exactly what you deserve for not thinking, what you're actually doing.
The change is not a bug, it exposes bugs in other software.
I think your title is misleading. To claim that IPv6 "sucks" probably reflects worse on yourself than on IPv6. If the problem is indeed caused by bindv6only, then the application is broken, and "sucks". I think it is great that Marco is pushing such changes because at some point we need to disable compatibility and put the blame on the applications that are broken. IPv6 is 20 years old, after all!
#7
martin f. krafft
(Homepage)
on
2010-01-12 20:43
I've had success with
ip -6 route add unreachable default
for routers advertising non-existing IPv6 functionality before as a one-time fix. YMMV.
If advertising is the problem, set
net.ipv6.conf.*.autoconf = 0
net.ipv6.conf.*.accept_ra = 0
net.ipv6.conf.*.accept_ra_defrtr = 0
net.ipv6.conf.*.accept_ra_pinfo = 0
net.ipv6.conf.*.accept_source_route = 0
net.ipv6.conf.*.accept_redirects = 0
net.ipv6.conf.*.forwarding = 0
with sysctl. Note that the * doesn't actually work. :(
You also only need the first two, but those who do usually want the others as
well.
#9
martin f. krafft
(Homepage)
on
2010-01-14 09:06