Date: Fri, 6 Dec 1996 18:32:46 +0100 (MET) From: Greg Lehey <grog@lemis.de> To: FreeBSD-current@FreeBSD.ORG (FreeBSD current users) Subject: Problems with PLIP driver? Message-ID: <199612061732.SAA02168@freebie.lemis.de>
next in thread | raw e-mail | index | archive | help
Some of you will know that I've been having troubles connecting up the
Ethernet board on my new notebook. One of the consequences is that I
have currently connected it to the net via PLIP. On the up side, it
worked like a dream: two ifconfigs (and a LapLink cable), and it was
up. However, there seem to be a few problems:
1. There seem to be an abnormal number of errors on the line. In the
following, freebie is my FreeBSD machine, and papillon is the
laptop:
=== root@papillon (/dev/ttyp3) /usr/X11R6/lib/X11/app-defaults/allegro 6 -> netstat -nib
Name Mtu Network Address Ipkts Ierrs Ibytes Opkts Oerrs Obytes Coll
lp0 1500 <Link> 29300 27 30801751 24586 3 2163795 0
lp0 1500 192.109.197 192.109.197.159 29300 27 30801751 24586 3 2163795 0
=== root@freebie (/dev/ttyp3) /usr/home/grog 3 -> netstat -bin
Name Mtu Network Address Ipkts Ierrs Ibytes Opkts Oerrs Obytes Coll
lp0 1500 <Link> 71136 99 8082298 93445 1147 89369707 0
lp0 1500 192.109.197 192.109.197.137 71136 99 8082298 93445 1147 89369707 0
The differences in the number of packets are due to intervening
boots.
2. There's definitely a bug in the bpf code, causing 100% of all
messages to be reported as invalid. I think I can find that one
by myself.
3. NFS across the link is very poor, and keeps hanging. With TCP
transport, it's bearable.
4. These problems seem to affect the Ethernet link (ep0) as well.
I've had to take it down and up again to get any kind of response,
and ping shows a strange cyclic behaviour. Succesive pings seem
to complete in pairs, with a difference in time of about 1
second. This only happens after errors on the PLIP interface:
=== grog@allegro (/dev/ttyp2) /home/Book/Debugging/tools 569 -> ping freebie
PING freebie.lemis.de (192.109.197.137): 56 data bytes
64 bytes from 192.109.197.137: icmp_seq=0 ttl=255 time=5.561 ms
64 bytes from 192.109.197.137: icmp_seq=1 ttl=255 time=1381.26 ms
64 bytes from 192.109.197.137: icmp_seq=2 ttl=255 time=387.521 ms
64 bytes from 192.109.197.137: icmp_seq=3 ttl=255 time=1378.96 ms
64 bytes from 192.109.197.137: icmp_seq=4 ttl=255 time=401.851 ms
64 bytes from 192.109.197.137: icmp_seq=5 ttl=255 time=1378.85 ms
64 bytes from 192.109.197.137: icmp_seq=6 ttl=255 time=404.673 ms
64 bytes from 192.109.197.137: icmp_seq=7 ttl=255 time=1380.65 ms
64 bytes from 192.109.197.137: icmp_seq=8 ttl=255 time=405.773 ms
64 bytes from 192.109.197.137: icmp_seq=9 ttl=255 time=1380.38 ms
64 bytes from 192.109.197.137: icmp_seq=10 ttl=255 time=404.27 ms
64 bytes from 192.109.197.137: icmp_seq=11 ttl=255 time=1382.17 ms
64 bytes from 192.109.197.137: icmp_seq=12 ttl=255 time=406.579 ms
64 bytes from 192.109.197.137: icmp_seq=13 ttl=255 time=1378.9 ms
64 bytes from 192.109.197.137: icmp_seq=14 ttl=255 time=403.052 ms
64 bytes from 192.109.197.137: icmp_seq=15 ttl=255 time=1380.25 ms
64 bytes from 192.109.197.137: icmp_seq=16 ttl=255 time=406.041 ms
64 bytes from 192.109.197.137: icmp_seq=17 ttl=255 time=1380.84 ms
64 bytes from 192.109.197.137: icmp_seq=18 ttl=255 time=406.596 ms
=== root@freebie (/dev/ttyp3) /usr/home/grog 4 -> ping allegro
PING allegro.lemis.de (192.109.197.134): 56 data bytes
64 bytes from 192.109.197.134: icmp_seq=0 ttl=255 time=7.502 ms
64 bytes from 192.109.197.134: icmp_seq=1 ttl=255 time=1201.185 ms
64 bytes from 192.109.197.134: icmp_seq=2 ttl=255 time=193.558 ms
64 bytes from 192.109.197.134: icmp_seq=3 ttl=255 time=1179.584 ms
64 bytes from 192.109.197.134: icmp_seq=4 ttl=255 time=173.113 ms
64 bytes from 192.109.197.134: icmp_seq=5 ttl=255 time=1159.442 ms
64 bytes from 192.109.197.134: icmp_seq=6 ttl=255 time=151.659 ms
64 bytes from 192.109.197.134: icmp_seq=7 ttl=255 time=1139.468 ms
64 bytes from 192.109.197.134: icmp_seq=8 ttl=255 time=137.395 ms
64 bytes from 192.109.197.134: icmp_seq=9 ttl=255 time=1120.913 ms
64 bytes from 192.109.197.134: icmp_seq=10 ttl=255 time=125.223 ms
64 bytes from 192.109.197.134: icmp_seq=11 ttl=255 time=1101.818 ms
64 bytes from 192.109.197.134: icmp_seq=12 ttl=255 time=96.483 ms
64 bytes from 192.109.197.134: icmp_seq=13 ttl=255 time=1083.642 ms
64 bytes from 192.109.197.134: icmp_seq=14 ttl=255 time=78.523 ms
64 bytes from 192.109.197.134: icmp_seq=15 ttl=255 time=1059.201 ms
64 bytes from 192.109.197.134: icmp_seq=16 ttl=255 time=53.367 ms
ping: sendto: No buffer space available
ping: wrote allegro.lemis.de 64 chars, ret=-1
64 bytes from 192.109.197.134: icmp_seq=17 ttl=255 time=1039.299 ms
64 bytes from 192.109.197.134: icmp_seq=19 ttl=255 time=1021.237 ms
64 bytes from 192.109.197.134: icmp_seq=20 ttl=255 time=17.304 ms
64 bytes from 192.109.197.134: icmp_seq=21 ttl=255 time=1002.022 ms
64 bytes from 192.109.197.134: icmp_seq=22 ttl=255 time=2.310 ms
64 bytes from 192.109.197.134: icmp_seq=23 ttl=255 time=980.937 ms
64 bytes from 192.109.197.134: icmp_seq=24 ttl=255 time=3.900 ms
64 bytes from 192.109.197.134: icmp_seq=25 ttl=255 time=972.604 ms
64 bytes from 192.109.197.134: icmp_seq=26 ttl=255 time=0.659 ms
64 bytes from 192.109.197.134: icmp_seq=27 ttl=255 time=939.376 ms
64 bytes from 192.109.197.134: icmp_seq=28 ttl=255 time=5.622 ms
64 bytes from 192.109.197.134: icmp_seq=29 ttl=255 time=923.507 ms
64 bytes from 192.109.197.134: icmp_seq=30 ttl=255 time=0.639 ms
64 bytes from 192.109.197.134: icmp_seq=31 ttl=255 time=903.033 ms
64 bytes from 192.109.197.134: icmp_seq=32 ttl=255 time=0.645 ms
64 bytes from 192.109.197.134: icmp_seq=33 ttl=255 time=879.722 ms
64 bytes from 192.109.197.134: icmp_seq=34 ttl=255 time=1870.599 ms
allegro is a BSD/OS 2.1 machine. Normally, a ping between these
machines taks about 600 microseconds, as the fastest results show.
After rebooting freebie, things return to normal, so I'm pretty
sure the problem isn't on the BSD/OS side.
I'm not asking anybody to jump in and fix these problems, but if this
rings a bell with anybody, I'd be grateful for some pointers.
Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612061732.SAA02168>