netdev - Re: fe80::/64 route missing on GRE tunnels

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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 15 Feb 2014 08:45:59 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	netdev@...r.kernel.org, itk-intern@...fundet.no
Subject: Re: fe80::/64 route missing on GRE tunnels

On Tue, Feb 11, 2014 at 10:59:28PM +0100, Steinar H. Gunderson wrote:
> On Tue, Feb 11, 2014 at 10:55:11PM +0100, Steinar H. Gunderson wrote:
> > but on 3.13.1, no such route shows up. I can add it manually, though.
> 
> Correction; I can add it manually, but only to one GRE device at a time:
> 
>   root@...ersex:~$ ip -6 route add fe80::/64 dev k_molvenfinnoy
>   root@...ersex:~$ ip -6 route add fe80::/64 dev k_sessesveits
>   RTNETLINK answers: File exists
>   root@...ersex:~$ ip -6 route del fe80::/64 dev k_molvenfinnoy
>   root@...ersex:~$ ip -6 route add fe80::/64 dev k_sessesveits
>   root@...ersex:~$

Sorry for the long delay, I was busy with other stuff...

So basically a workaround you can do for the time being is to add the tunnel
with a local address:

ip tunnel add foo mode gre local 4.3.2.1 remote 1.2.3.4 ttl 64

The reason is that link local address generation fails in ipv6/addrconf as
long as dev->dev_addr is zero.

I have not yet found the change which causes this change in behaviour, but
will do so soon.

Bye,

  Hannes

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html