From: Eric Dumazet <eric.dumazet@gmail.com>
To: nicolas.dichtel@6wind.com
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next 1/3] ipip: advertise tunnel param via rtnl
Date: Fri, 09 Nov 2012 11:42:48 -0800 [thread overview]
Message-ID: <1352490168.19779.776.camel@edumazet-glaptop> (raw)
In-Reply-To: <509D36CB.9030509@6wind.com>
On Fri, 2012-11-09 at 18:00 +0100, Nicolas Dichtel wrote:
> If the principle is approved, yes. If we add it, we will have two
> ways to manage these tunnels, via netlink and via ioctl, is it ok?
>
> A side effect could be to have an option or an argument to the module to not
> create the control interface (tunl0, sit0, ...).
The principle is already used for gre tunnels, so it definitely is
approved ;)
next prev parent reply other threads:[~2012-11-09 19:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 9:51 [PATCH net-next 0/4] Advertise tunnel parameters via netlink Nicolas Dichtel
2012-11-09 9:51 ` [PATCH net-next 1/4] ipip: advertise tunnel param via rtnl Nicolas Dichtel
2012-11-09 13:20 ` Eric Dumazet
2012-11-09 16:09 ` [PATCH net-next 0/3] Advertise tunnel parameters via netlink Nicolas Dichtel
2012-11-09 16:09 ` [PATCH net-next 1/3] ipip: advertise tunnel param via rtnl Nicolas Dichtel
2012-11-09 16:37 ` Eric Dumazet
2012-11-09 17:00 ` Nicolas Dichtel
2012-11-09 19:42 ` Eric Dumazet [this message]
2012-11-09 16:10 ` [PATCH net-next 2/3] sit: " Nicolas Dichtel
2012-11-09 16:10 ` [PATCH net-next 3/3] ip6tnl: " Nicolas Dichtel
2012-11-10 0:36 ` [PATCH net-next 0/3] Advertise tunnel parameters via netlink David Miller
2012-11-09 9:51 ` [PATCH net-next 2/4] sit: advertise tunnel param via rtnl Nicolas Dichtel
2012-11-09 9:51 ` [PATCH net-next 3/4] ip6tnl: " Nicolas Dichtel
2012-11-09 9:51 ` [PATCH net-next 4/4] gre6: fix rtnl dump messages Nicolas Dichtel
2012-11-09 13:22 ` Eric Dumazet
2012-11-09 15:34 ` [PATCH] " Nicolas Dichtel
2012-11-09 16:09 ` Eric Dumazet
2012-11-09 22:11 ` 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=1352490168.19779.776.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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