From: zhuyj <zyjzyj2000@gmail.com>
To: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net,
linux-kernel@vger.kernel.org, zhuyj <zyjzyj2000@gmail.com>
Subject: Re: How to identify different ip tunnels
Date: Thu, 23 Jan 2014 16:54:48 +0800 [thread overview]
Message-ID: <52E0D8D8.8040902@gmail.com> (raw)
In-Reply-To: <52E0C5B7.7040908@gmail.com>
The version of the kernel is 3.4.43.
Any reply is appreciated.
Best Regards!
Zhu Yanjun
On 01/23/2014 03:33 PM, zhuyj wrote:
> Hi, Maintainers
>
> We want to identify different ip tunnels.
>
> For example, we use “ip tunnel add xxx” command in linux to create an
> ipv4/6 tunnel interface,then,we can receive a RTM_NEWLINK message from
> linux for the new tunnel interface.
> We will parse the struct ifinfomsg message and get the ifi->ifi_type
> attribute. We need to do somethings depend on the tunnel type here.
> I checked the linux source code and list all the tunnel types here:
>
> #define ARPHRD_TUNNEL 768 /* IPIP tunnel */
> #define ARPHRD_TUNNEL6 769 /* IP6IP6 tunnel */
> #define ARPHRD_SIT 776 /* sit0 device - IPv6-in-IPv4 */
> #define ARPHRD_IPGRE 778 /* GRE over IP */
>
> It means that the linux will report the new link for any ipv4/6 tunnel
> interface with type only within these four types. However, We need
> more tunnel types for ipv4/6 tunnel.
> For example, 4IN4/6IN4/6TO4/GRE/ISATAP for ipv4 tunnel and
> 4IN6/6IN6/IPIN6 for ipv6 tunnel.
>
> Here are the result that we have got:
>
> Actual Tunnel type ifi->ifi_type
> 4IN4 768
> GRE4 778
> 6IN4/6TO4/ISATAP 776
> 4IN6/6IN6/IPIN6 769
>
> So, we can NOT distinguish the actual tunnel type via ifi_type
> attribute except the GRE4 and 4IN4 tunnel. However we need the actual
> type. That is our question.
>
> BTW, for the 6IN4 and 6TO4 tunnel, Can we distinguish them before the
> interface ip address configured? Because we need to do different
> things for them when we received the new link message and the tunnel
> has NOT any ip address in this time.
>
> Best Regards!
> Zhu Yanjun
>
next prev parent reply other threads:[~2014-01-23 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 7:33 How to identify different ip tunnels zhuyj
2014-01-23 8:54 ` zhuyj [this message]
2014-01-23 18:16 ` Cong Wang
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=52E0D8D8.8040902@gmail.com \
--to=zyjzyj2000@gmail.com \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).