* kernel bug 14839
@ 2010-12-17 15:18 Ian Shorter
2010-12-17 15:31 ` David Lamparter
0 siblings, 1 reply; 2+ messages in thread
From: Ian Shorter @ 2010-12-17 15:18 UTC (permalink / raw)
To: netdev
At the end of 2009 I reported kernel bug 14839: "Trying to use a TUN device for IPv6 traffic, cannot set destination address". I was wondering whether any progress has been made towards resolving the problem? Regards.
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: kernel bug 14839 2010-12-17 15:18 kernel bug 14839 Ian Shorter @ 2010-12-17 15:31 ` David Lamparter 0 siblings, 0 replies; 2+ messages in thread From: David Lamparter @ 2010-12-17 15:31 UTC (permalink / raw) To: Ian Shorter; +Cc: netdev [-- Attachment #1: Type: text/plain, Size: 784 bytes --] On Fri, Dec 17, 2010 at 07:18:58AM -0800, Ian Shorter wrote: > At the end of 2009 I reported kernel bug 14839: "Trying to use a TUN > device for IPv6 traffic, cannot set destination address". I was > wondering whether any progress has been made towards resolving the > problem? Regards. The bug is invalid. You are incorrectly assuming the IPv4 pattern of a "local" and a "remote" address applies to IPv6. Also, you are incorrectly using an fe80:: address with a /128 mask. (fe80:: with anything but /64 is usually gross mis-setup) Please change the application to do the following: * add a fe80::/64 address to the tun device * use either device-only routes ("2001:db8::/32 dev tun0") or get the peer link-local address (might be complicated) and use that as nexthop. -David [-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --] ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-12-17 15:31 UTC | newest] Thread overview: 2+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2010-12-17 15:18 kernel bug 14839 Ian Shorter 2010-12-17 15:31 ` David Lamparter
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).