Date: Tue, 30 Sep 1997 16:54:24 +0930 From: Greg Lehey <grog@lemis.com> To: Annelise Anderson <andrsn@leland.Stanford.EDU> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Network Connection Not Working Message-ID: <19970930165424.08430@lemis.com> In-Reply-To: <Pine.GSO.3.96.970929231230.3884A-100000@elaine24.Stanford.EDU>; from Annelise Anderson on Mon, Sep 29, 1997 at 11:26:02PM -0700 References: <Pine.GSO.3.96.970929231230.3884A-100000@elaine24.Stanford.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 29, 1997 at 11:26:02PM -0700, Annelise Anderson wrote:
> Some time after I left the office today my computer lost its ability
> to talk to the outside world--I can dial in to it but can't ping
> anything, I'm not getting mail, can't telnet, etc. (So this is
> being written from a different e-mail account.)
>
> Relevant parts of /var/log/messages (I rebooted) look like this:
>
> Sep 29 20:03:49 andrsn /kernel: 1 3C5x9 board(s) on ISA found at 0x300
> Sep 29 20:03:49 andrsn /kernel: ep0 at 0x300-0x30f irq 10 on isa
> Sep 29 20:03:49 andrsn /kernel: ep0: aui/utp/bnc[*BNC*] address 00:20:af:be:eb:e0
> Sep 29 20:03:50 andrsn named[92]: starting. named 4.9.6-REL Fri Sep 5 16:37:03 PDT 1997 andrsn@andrsn.stanford.edu:/usr/obj/usr/src/usr.sbin/named
> Sep 29 20:03:50 andrsn named[93]: Ready to answer queries.
> Sep 29 20:04:04 andrsn routed[67]: sendto(ep0, 224.0.0.1): No route to host
> Sep 29 20:04:20 andrsn routed[67]: sendto(ep0, 224.0.0.1): No route to host
> Sep 29 20:07:41 andrsn routed[67]: ignore RTM_ADD without gateway
> Sep 29 20:12:57 andrsn routed[67]: sendto(ep0, 224.0.0.1): No route to host
> Sep 29 20:16:07 andrsn routed[67]: interface ep0 to 36.33.0.163 broken: in=0 ierr=0 out=3 oerr=3
Well, I don't use (nor recommend) routed, but this appears to be
telling you that it can't output on this interface.
> Sep 29 20:16:27 andrsn routed[67]: interface ep0 to 36.33.0.163 restored
> Sep 29 20:16:46 andrsn routed[67]: sendto(ep0, 224.0.0.1): No route to host
> Sep 29 20:17:03 andrsn routed[67]: sendto(ep0, 224.0.0.1): No route to host
> Sep 29 20:19:26 andrsn routed[67]: interface ep0 to 36.33.0.163 broken: in=0 ierr=0 out=1 oerr=1
> Sep 29 20:19:41 andrsn routed[67]: interface ep0 to 36.33.0.163 restored
> Sep 29 20:38:28 andrsn routed[67]: sendto(ep0, 224.0.0.1): No route to host
>
> The network before looked like this:
>
>> From root@andrsn.stanford.edu Mon Sep 29 22:18:41 1997
> Date: Mon, 29 Sep 1997 02:00:01 -0700 (PDT)
> From: "A. Anderson" <root@andrsn.stanford.edu>
> Subject: andrsn daily run output
>
> network:
> Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
> lp0* 1500 <Link> 0 0 0 0 0
> ep0 1500 <Link> 00.20.af.be.eb.e0 4675592 812 523700 1 0
> ep0 1500 36.33/16 andrsn 4675592 812 523700 1 0
> tun0* 1500 <Link> 210 0 167 0 0
> sl0* 552 <Link> 0 0 0 0 0
> sl1* 552 <Link> 0 0 0 0 0
> ppp0* 1500 <Link> 540 15 481 0 0
> lo0 16384 <Link> 193928 0 193928 0 0
> lo0 16384 your-net localhost 193928 0 193928 0 0
>
> It looks similar now (netstat -in)--but lots of collisions and errors.
>
> Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
> lp0* 1500 <Link> 0 0 0 0 0
> ep0 1500 <Link> 00.20.af.be.eb.e0 282 0 1126 836 836
> ep0 1500 36.33/16 36.33.0.163 282 0 1126 836 836
Well, it looks like you are (or were) getting something in, but
obviously 836 errors out of a total of 1126 packets suggest that
something is seriously wrong. Also, it looks like you got 282 packets
in, and sent
> tun0* 1500 <Link> 0 0 0 0 0
> sl0* 552 <Link> 0 0 0 0 0
> sl1* 552 <Link> 0 0 0 0 0
> ppp0* 1500 <Link> 0 0 0 0 0
> lo0 16384 <Link> 203 0 203 0 0
> lo0 16384 127 127.0.0.1 203 0 203 0 0
>
>
> Routing tables (when it was working)
> ...
> Routing tables after it quit working are identical except for a fer numbers:
Yes, so this isn't very interesting.
> 19 10:37pm ~ # ifconfig -au
>
> ep0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet 36.33.0.163 netmask 0xffff0000 broadcast 36.33.255.255
> ether 00:20:af:be:eb:e0
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
> inet 127.0.0.1 netmask 0xff000000
>
> The right stuff seems to be up--
Or claims to be up.
> I'm not sure if netstat -a contains useful information or not:
No, that's a higher level. We're looking at the link layer here.
> I tried quite a few things--reinstating resolv.conf although I'd
> moved it when I set up the cache only nameserver (with forwarders);
> rebooting; killing routed -s and later restarting it. Everthing seems
> to be running--httpd, sendmail, named, etc.
All these things run at higher levels. The error rate on the
interface show that what we're seeing here is pretty certainly at the
link layer.
> So here is some output-- my current guess is that wire that goes
> from the Ethernet card connector (10-Base-2)
10-Base 2? Your boot message says BNC. How do you configure the
interface? Do you set the link flags specifically? I don't see
anything in the ifconfig output above. Check the link flags:
-link0 Use the BNC port (default).
link0 -link1 Use the AUI port.
link0 link1 Use the UTP port.
This would suggest that you should be showing LINK0 and LINK1 in the
output above.
> is broken--does this look consistent with that? And if so, do I
> just cut it and reattach it?
It's consistent, but it doesn't have to be the right answer. Your
board could have got itself confused--I've seen this happen with the
3C509, and occasionally I have been able to fix it with the following
sequence:
# ifconfig ep0 down
# ifconfig ep0 up
This won't cost you much, and you can do it from where you are
(assuming you haven't gone to bed yet).
Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970930165424.08430>