On Sat, Feb 02, 2002 at 09:32:18PM +0300, kuznet@ms2.inr.ac.ru wrote:
> Hello!
>
> > Dead loop on virtual device tun1, fix it urgently!
>
> Is this "tun1" user space tap device?
You seem to have skipped this part of the mail:
>> The device in question is a tunnel device, it does ipv6 over
>> ipv4.
It's a "sit" device. CONFIG_TUN is not
set.
> Well, describe the configuration in more details: setup of tunnel,
> ifconfig etc.
It's a basic ipv6 tunnel configuration. It's not the first time
I set it up, it's the first time I get the message.
The setup was with:
ip tunnel add tun1 remote x.x.x.x local x.x.x.x mode sit ttl 64
ip link set tun1 up
ip addr add x:x:x:x::1/126 dev tun1
ip route add 2000::/3 dev tun1
ifconfig tun1 returns:
tun1 Link encap:IPv6-in-IPv4
inet6 addr: fe80::x:x/128 Scope:Link
inet6 addr: x:x:x:x::1/126 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:2181995 errors:0 dropped:0 overruns:0 frame:0
TX packets:10417287 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
ip -6 route | grep tun1:
x:x:x:x::/126 via :: dev tun1 proto kernel metric 256 mtu 1480
2000::/3 dev tun1 metric 1024 mtu 1480
fe80::/10 via :: dev tun1 proto kernel metric 256 mtu 1480
ff00::/8 dev tun1 proto kernel metric 256 mtu 1480
There are 2 other tunnels set up simular, except that they don't
have 2000::/3 routed to them.
It's also running radvd. It's acting as our ipv6 gateway.
I just removed that tunnel and and added it again, and I'm still
getting it.
Something I just noticed: For eth0 we have:
RX packets:13934920 errors:0 dropped:0 overruns:0 frame:0
TX packets:13415931 errors:1 dropped:0 overruns:0 carrier:0
collisions:533154 txqueuelen:100
I find that a rather big number of collisions. Could it be
related?
Kurt
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
