From: Ulf Samuelsson <ulf.samuelsson@ericsson•com>
To: David Miller <davem@davemloft•net>
Cc: <dcbw@redhat•com>, <netdev@emagii•com>,
<hannes@stressinduktion•org>, <netdev@vger•kernel.org>
Subject: Re: netlink NETLINK_ROUTE failure & Can the kernel really handle IPv6 properly
Date: Mon, 6 Oct 2014 13:25:16 +0200 [thread overview]
Message-ID: <54327C1C.7060808@ericsson.com> (raw)
In-Reply-To: <20141003.114949.826855678619123407.davem@davemloft.net>
On 10/03/2014 08:49 PM, David Miller wrote:
> From: Ulf Samuelsson <ulf.samuelsson@ericsson•com>
> Date: Fri, 3 Oct 2014 09:59:39 +0200
>
>> The kernel module is a control module which collects information
>> both from the kernel and from H/W, and talks to a userspace interface
>> manager.
>>
>> There is a proprietary management application which is used to
>> configure the stack.
>> This talks to the interface manager to handle different operations for
>> IPv6.
>>
>> The kernel module needs to know when interfaces are ready to use,
>> I.E: know when it exits "tentative" mode to do its job properly,
>> so the kernel module has to listen for RTM_NEWADDR.
>>
>> In a simpler system, your approach would be OK.
> Sorry, we're not going to help you with a proprietary driver
> of this kind.
>
> They should really just follow our upstream efforts to design
> a usable kernel framework for bridge and routing hardware offloads.
Whether to use a kernel framework or not is not my decision,
and I don't even work with that code.
What should interest the community is that a lot of stuff is probably
not working properly, when IPv6 link-local addresses are used.
Listening for NETDEV_UP, which is used in many places in the kernel,
seems incorrect,
since connection to the link-local address will fail until the
link-local address is verified.
It is not immediately obvious, since after 1-2 seconds the problem
disappears.
For that, listening to the RTM_NEWADDR seems mandatory, so
any framework would benefit from a solution as well.
Best Regards,
Ulf Samuelsson
'
next prev parent reply other threads:[~2014-10-06 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 20:28 netlink NETLINK_ROUTE failure & Can the kernel really handle IPv6 properly Ulf Samuelsson
2014-10-01 21:30 ` Hannes Frederic Sowa
2014-10-02 12:38 ` Ulf samuelsson
2014-10-02 15:44 ` Dan Williams
2014-10-03 5:59 ` Ulf Samuelsson
2014-10-03 7:59 ` Ulf Samuelsson
2014-10-03 18:49 ` David Miller
2014-10-06 11:25 ` Ulf Samuelsson [this message]
2014-10-06 3:35 ` Gao feng
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=54327C1C.7060808@ericsson.com \
--to=ulf.samuelsson@ericsson$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dcbw@redhat$(echo .)com \
--cc=hannes@stressinduktion$(echo .)org \
--cc=netdev@emagii$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/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