Hello, Im new to the list, and I have a new problem, one that I havent seen before. I have a pcmcia card, a CNET SiglePoint 10/100 FastEthernet PCcard atached to a Compaq Presario 1711LA computer. This is eth1. Eth0 is the internal Ethernet card and is atached to a ADSL modem. Eth1 is the intranet. Suddently something started to go wrong. I just cant figure whats that, because I cant thing of something I have done. The intranet started to fail a lot. I send some pings of 56Bytes and everythin was ok for the first paquets, until more less 10 pakets after the test began, a paquet intsead of returning in .3ms returned in 10000ms, the next to 8000ms, next 6000ms or so. That went for some packets and then again 10 pakets at .3ms and the cycle began again. I tested with a ping size paket of 2048 and the same happened just of instad .3ms it was 3ms... But I also tested for values of 1024 and 1500 (the MTU value) and then, there where lots of pakets that never arrived. (using flood option) and I got this messages in kern.log: (at the end Ill post some tests I did)
Jul 8 14:19:07 pablap kernel: NETDEV WATCHDOG: eth1: transmit timed out Jul 8 14:19:07 pablap kernel: eth1: Tx queue start entry 32 dirty entry 28. Jul 8 14:19:07 pablap kernel: eth1: Tx descriptor 0 is 00002000. (queue head) Jul 8 14:19:07 pablap kernel: eth1: Tx descriptor 1 is 00002000. Jul 8 14:19:07 pablap kernel: eth1: Tx descriptor 2 is 00002000. Jul 8 14:19:07 pablap kernel: eth1: Tx descriptor 3 is 00002000. Jul 8 14:19:07 pablap kernel: eth1: Setting 100mbps full-duplex based on auto-negotiated partner ability 45e1. ------------------- pablap:/var/log# ping -s 1024 192.168.30.200 PING 192.168.30.200 (192.168.30.200): 1024 data bytes 1032 bytes from 192.168.30.200: icmp_seq=0 ttl=128 time=0.9 ms 1032 bytes from 192.168.30.200: icmp_seq=5 ttl=128 time=11001.0 ms 1032 bytes from 192.168.30.200: icmp_seq=6 ttl=128 time=10001.1 ms 1032 bytes from 192.168.30.200: icmp_seq=7 ttl=128 time=9001.1 ms 1032 bytes from 192.168.30.200: icmp_seq=8 ttl=128 time=8001.4 ms 1032 bytes from 192.168.30.200: icmp_seq=9 ttl=128 time=7002.0 ms 1032 bytes from 192.168.30.200: icmp_seq=10 ttl=128 time=6002.0 ms 1032 bytes from 192.168.30.200: icmp_seq=14 ttl=128 time=2002.2 ms 1032 bytes from 192.168.30.200: icmp_seq=15 ttl=128 time=1002.6 ms 1032 bytes from 192.168.30.200: icmp_seq=16 ttl=128 time=2.8 ms 1032 bytes from 192.168.30.200: icmp_seq=17 ttl=128 time=0.8 ms --- 192.168.30.200 ping statistics --- 21 packets transmitted, 11 packets received, 47% packet loss round-trip min/avg/max = 0.8/4910.7/11001.0 ms ------------------ I couldnt reproduce what happened when using 56B and 2048B, in 56B all packets where back in .2ms and in 2048B where back in 1.1ms exept 2 of 25 that where back in 56ms ---------------- flood testespablap:/var/log# ping -f -s 56 192.168.30.200 PING 192.168.30.200 (192.168.30.200): 56 data bytes ... --- 192.168.30.200 ping statistics --- 49421 packets transmitted, 49418 packets received, 0% packet loss round-trip min/avg/max = 0.1/0.2/6.1 ms ---------------- pablap:/var/log# ping -f -s 2048 192.168.30.200 PING 192.168.30.200 (192.168.30.200): 2048 data bytes ................................. --- 192.168.30.200 ping statistics --- 11679 packets transmitted, 11646 packets received, 0% packet loss round-trip min/avg/max = 0.9/14.3/28.2 ms ---------------- pablap:/var/log# ping -f -s 1024 192.168.30.200 PING 192.168.30.200 (192.168.30.200): 1024 data bytes ......................................................... --- 192.168.30.200 ping statistics --- 59 packets transmitted, 1 packets received, 98% packet loss round-trip min/avg/max = 18.1/18.1/18.1 ms ---------------- ifconfig: pablap:/var/log# ifconfig eth0 Link encap:Ethernet HWaddr 00:02:A5:9B:89:09 inet addr:x.x.x.x Bcast:x.x.x.x Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3119 errors:0 dropped:0 overruns:0 frame:0 TX packets:3133 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1722708 (1.6 MiB) TX bytes:389532 (380.4 KiB) Interrupt:9 Base address:0xf000 eth1 Link encap:Ethernet HWaddr 00:10:60:75:30:A6 inet addr:192.168.30.1 Bcast:192.168.30.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:74238 errors:0 dropped:0 overruns:0 frame:0 TX packets:74072 errors:0 dropped:0 overruns:16 carrier:0 collisions:0 txqueuelen:100 RX bytes:29954078 (28.5 MiB) TX bytes:30184567 (28.7 MiB) Interrupt:10 Base address:0x4000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:402 errors:0 dropped:0 overruns:0 frame:0 TX packets:402 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:20312 (19.8 KiB) TX bytes:20312 (19.8 KiB) ppp0 Link encap:Point-to-Point Protocol inet addr:x.x.x.x P-t-P:x.x.x.x Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:2555 errors:0 dropped:0 overruns:0 frame:0 TX packets:2499 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1632530 (1.5 MiB) TX bytes:302633 (295.5 KiB) It is pppoe... --------------- Any ideas???? any other tests I should include in a future mail? Thanks in advance Pablo E. Limon __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]