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?
thanks,
--
Zoltan NAGY,
Network Administrator,
Nefty Informatics and Providing Ltd.,
[email protected],
+36702269471
--On Sunday, September 07, 2003 01:28:08 AM +0200 Zoltan NAGY
<[email protected]> 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/