From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Vaittinen, Matti (EXT-Other - FI/Oulu)" <matti.vaittinen.ext@nsn.com>
Cc: netdev@vger.kernel.org
Subject: RE: IPv6 routing requests ignore NLM_F_CREATE and NLM_F_REPLACE
Date: Tue, 18 Oct 2011 08:54:28 +0200 [thread overview]
Message-ID: <1318920868.2571.52.camel@edumazet-laptop> (raw)
In-Reply-To: <82C9FC7ED59434458AD4E09AFF2DE230B534F9@FIESEXC006.nsn-intra.net>
Le mardi 18 octobre 2011 à 09:02 +0300, Vaittinen, Matti (EXT-Other -
FI/Oulu) a écrit :
> Hi again.
>
...
> I do not intend pushing this topic but is this the correct list to ask
> this? Is there something I could clarify regarding my question? If this
> is not correct list, could someone please point me the right one.
>
Well, this is the correct list. And yes, please send us a patch.
IPv6 lacks some features found in IPv4, not on purpose, but because
nobody wanted them or had the time to implement them.
next prev parent reply other threads:[~2011-10-18 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 6:02 IPv6 routing requests ignore NLM_F_CREATE and NLM_F_REPLACE Vaittinen, Matti (EXT-Other - FI/Oulu)
2011-10-18 6:54 ` Eric Dumazet [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-17 9:06 Vaittinen, Matti (EXT-Other - FI/Oulu)
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=1318920868.2571.52.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=matti.vaittinen.ext@nsn.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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