netdev - Re: kernel bug 14839

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20101217153131.GD2164726@jupiter.n2.diac24.net>
Date:	Fri, 17 Dec 2010 16:31:31 +0100
From:	David Lamparter <equinox@...c24.net>
To:	Ian Shorter <mcisho@...oo.com>
Cc:	netdev@...r.kernel.org
Subject: Re: kernel bug 14839

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

Content of type "application/pgp-signature" skipped