From: Peter Bieringer <pb@bieringer.de>
To: Zoltan NAGY <nagyz@nefty.hu>
Cc: usagi-users@linux-ipv6.org, linux-kernel@vger.kernel.org
Subject: Re: (usagi-users 02525) sit tunnel/iptunnel bug?
Date: Sun, 07 Sep 2003 11:48:22 +0200 [thread overview]
Message-ID: <17150000.1062928102@worker.muc.bieringer.de> (raw)
In-Reply-To: <FEEILOIHCEAEMLNJIDEJOELICFAA.nagyz@nefty.hu>
--On Sunday, September 07, 2003 01:28:08 AM +0200 Zoltan NAGY
<nagyz@nefty.hu> wrote:
> hi!
>
> i've got some really odd behavior.. if i do:
> ip tunnel add t12 mode sit remote 195.70.51.141 local 195.70.37.175 ttl 64
> then ip link set t12 up i got:
> RTNETLINK answers: No such device
> it must be a bug, because i only get this if i have another 12 or more
> tunnels added before this one.. and just with specific ip address, if i
> change it or simply use ip tunnel add t12 mode sit remote 195.70.51.141,
> then it's working..
> this problem exists in 2.4.20, and .22; .21 is not tested..
> is this a real bug? has anyone experienced it before?
This single command line works fine here. Perhaps you have used the same
destination a second time on tunnel "t12".
Check this, because of a bug in "ip", adding of tunnel with the same
destination silenty fails (exit code = 0).
This is why my initscript-ipv6 package checks whether destination address
is already applied on another tunnel.
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
prev parent reply other threads:[~2003-09-07 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 23:28 Zoltan NAGY
2003-09-07 9:48 ` Peter Bieringer [this message]
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=17150000.1062928102@worker.muc.bieringer.de \
--to=pb@bieringer.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nagyz@nefty.hu \
--cc=usagi-users@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
Powered by JetHome