Hello,
We have a AS 2100 with the standard netcard (tu0) and a 10/100 (tu1) one.
We don't use tu0 to anything, but why can't it be deleted? I can get it
down,
but not deleted. But if I put it down, something still tries to do something
to it, because this leads to the "no buffer space available" and this also
leads to a crash of the whole system. But if I leave it up, this also
happens,
but much later.
This is what I have:
xxxx root > ifconfig -a
tu0: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
tu1: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
inet 192.xx.x.xx netmask ffffff00 broadcast 192.xx.x.255 ipmtu 1500
sl0: flags=10<POINTOPOINT>
lo0: flags=100c89<UP,LOOPBACK,NOARP,MULTICAST,SIMPLEX,NOCHECKSUM>
inet 127.0.0.1 netmask ff000000 ipmtu 4096
xxxx root > netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs
Coll
tu0 1500 <Link> 08:00:xx:xx:xx:xx 0 0 989 989
0
tu0 1500 DLI none 0 0 989 989
0
tu1 1500 <Link> 00:00:xx:xx:xx:xx 12035895 1 14840756 3
0
tu1 1500 ournet xxxx 12035895 1 14840756 3 0
tu1 1500 DLI none 12035895 1 14840756 3
0
sl0* 296 <Link> 0 0 0 0
0
lo0 4096 <Link> 2335279 0 2335279 0
0
lo0 4096 loop localhost 2335279 0 2335279 0
0
As you see something is sending something to tu0. I found out, that
lat was one of the bad guys, but that i corrected with: latcp -e
tu1
Now i still have this.. How do I prevent these?
tahma root xterm > tcpdump -i tu0
tcpdump: listening on tu0
Using kernel BPF filter
09:27:35.488699 8:0:xx:xx:xx:xx ab:0:0:2:0:0 moprc 34:
2000 0700 0000 0100 0304 0000 0200 0241
0064 0001 cb90 0101 0107 0006 0800 2be2
497c
09:27:35.488699
0700 0000 0100 0304 0000 0200 0241 0064
0001 cb90 0101 0107 0006 0800 2be2 497c
0a00 104e 1fb3 b2c2 e9d3 01ff ffff
--
Tony Lindström * System Manager * Tekla Oy
tel:+358 9 887 9441 gsm:+358 40 762 0768
http://www.iki.fi/tonyk/ mailto:tonyk_at_iki.fi
Received on Wed Feb 23 2000 - 07:44:59 NZDT