From: zhuyj <zyjzyj2000@gmail.com>
To: nicolas.dichtel@6wind.com,
"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
Subject: Re: How to identify 6to4 and 6in4 tunnels
Date: Tue, 28 Jan 2014 15:32:51 +0800 [thread overview]
Message-ID: <52E75D23.10909@gmail.com> (raw)
In-Reply-To: <52E65817.1090904@6wind.com>
On 01/27/2014 08:59 PM, Nicolas Dichtel wrote:
> Le 27/01/2014 11:39, zhuyj a écrit :
>> Hi, Maintainers
>>
>> In our scene, we will create the 6in4/6to4 tunnel firstly and need to
>> check the
>> tunnel type, secondly, we will configure the ip address on it. So,
>> Could we have
>> any way to get the actual tunnel for 6in4 and 6to4 from current linux
>> version?
>>
>> Both 6in4 and 6to4 have the same protocol “IPPROTO_IPV6” in Linux
>> kernel. The
>> only difference is the ip address on the tunnel. Can we distinguish
>> them in
>> Linux kernel?
> Just check the prefix, like it is done in check_6rd().
>
>
> Regards,
> Nicolas
>
Hi, Nicolas
Thanks for your reply. Maybe I can configure 6to4 tunnel by the
following commands:
ip tunnel add tun6to4 mode sit remote any local 1.202.252.122 ttl 64
ip link set dev tun6to4 up
ip -6 addr add 2002:01ca:fc7a::0012:0225:2122/128 dev tun6to4
ip -6 route add 2000::/3 via ::192.88.99.1 dev tun6to4 metric 1
But the kernel can not identify the tunnel is 6to4 tunnel or 6in4 tunnel
immediately. After the packets travel through this tunnel, the kernel
can identify the type of the tunnel by check_6rd.
Is it right?
Best Regards!
Zhu Yanjun
next prev parent reply other threads:[~2014-01-28 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 10:39 How to identify 6to4 and 6in4 tunnels zhuyj
2014-01-27 12:59 ` Nicolas Dichtel
2014-01-28 7:32 ` zhuyj [this message]
2014-01-28 7:39 ` zhuyj
2014-01-28 10:18 ` zhuyj
2014-01-28 15:20 ` Nicolas Dichtel
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=52E75D23.10909@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=nicolas.dichtel@6wind.com \
--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).