From: Nicolas Dichtel <nicolas.dichtel@6wind•com>
To: netdev@vger•kernel.org, itk-intern@samfundet•no,
sesse@samfundet•no,
Hannes Frederic Sowa <hannes@stressinduktion•org>
Subject: Re: fe80::/64 route missing on GRE tunnels
Date: Mon, 17 Feb 2014 10:37:07 +0100 [thread overview]
Message-ID: <5301D843.4020802@6wind.com> (raw)
In-Reply-To: <20140215121027.GC8634@order.stressinduktion.org>
Le 15/02/2014 13:10, Hannes Frederic Sowa a écrit :
> Hi Nicolas!
>
> On Sat, Feb 15, 2014 at 08:45:59AM +0100, Hannes Frederic Sowa wrote:
>> 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@altersex:~$ ip -6 route add fe80::/64 dev k_molvenfinnoy
>>> root@altersex:~$ ip -6 route add fe80::/64 dev k_sessesveits
>>> RTNETLINK answers: File exists
>>> root@altersex:~$ ip -6 route del fe80::/64 dev k_molvenfinnoy
>>> root@altersex:~$ ip -6 route add fe80::/64 dev k_sessesveits
>>> root@altersex:~$
>>
>> 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.
>
> f7cb8886335dea ("sit/gre6: don't try to add the same route two times") causes
> this problem, because dev->dev_addr will never get initialized and thus
> ipv6_generate_eui64 and addrconf_add_linklocal will never get called.
>
> Ok for revert or do you have a better idea?
I'm not sure to understand the problem. In the case described above, there is no
fe80::/64 route because there is no link local address.
What source address will be used to communicate over this gre interface?
next prev parent reply other threads:[~2014-02-17 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 21:55 fe80::/64 route missing on GRE tunnels Steinar H. Gunderson
2014-02-11 21:59 ` Steinar H. Gunderson
2014-02-15 7:45 ` Hannes Frederic Sowa
2014-02-15 12:10 ` Hannes Frederic Sowa
2014-02-17 9:37 ` Nicolas Dichtel [this message]
2014-02-17 9:45 ` Steinar H. Gunderson
2014-02-17 9:59 ` Nicolas Dichtel
2014-02-17 10:17 ` Steinar H. Gunderson
2014-02-17 10:34 ` Nicolas Dichtel
2014-02-17 13:04 ` Hannes Frederic Sowa
2014-02-17 13:22 ` [PATCH net] gre: add link local route when local addr is any Nicolas Dichtel
2014-02-17 19:09 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5301D843.4020802@6wind.com \
--to=nicolas.dichtel@6wind$(echo .)com \
--cc=hannes@stressinduktion$(echo .)org \
--cc=itk-intern@samfundet$(echo .)no \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sesse@samfundet$(echo .)no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox