Date: Fri, 04 Aug 2000 09:27:16 +0600 From: Alexander <arap@oduurl.ru> To: Ben Hacker Jr <strbenjr@yahoo.com> Cc: list DC-FBSD <fug-washdc@Sytex.Net>, questions FBSD <freebsd-questions@FreeBSD.ORG>, Stable FBSD <freebsd-stable@FreeBSD.ORG>, Ben Hacker Jr <bhacker1@csc.com> Subject: Re: Router "ep2" issue Message-ID: <398A3814.FF8C39F6@oduurl.ru> References: <20000803210513.11627.qmail@web4502.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ben Hacker Jr wrote: > > Hello all... > > I built a router about six months back and it has been > > working pretty good except that sometimes I will lose > connectivity to the subnet on one of the ports (ep2). > > I lost connectivity again today and tried to figure > out what > was going wrong. I don't know how to tell if it is > caused > by hardware or my configuration. Same problem with "ep" drivers: - 4x3com579(EISA) in i486DX50 - 3.4-STABLE FreeBSD - cured "ifconfig down/up" I suppose a ethernet problems Problems disapear when I disconnect new station with unnamed network card > > 10Mb 100Mb > +---------------+ > 10.44.17.062/27=|ep0 FreeBSD | > 10.44.17.126/27=|ep1 Router > xl0|=10.44.25.250/30 > 10.44.17.222/27=|ep2 | > +---------------+ > me@FBSD_Router1$ uname -a > FreeBSD FBSD_Router1 3.4-STABLE FreeBSD 3.4-STABLE #2: > Fri Mar 17 11 > :42:33 EST 2000 > me@FBSD_Router1:/usr/src/sys/compile/Router1-4 i386 > me@FBSD_Router1$ > > network_interfaces="xl0 ep2 ep1 ep0 lo0" > ifconfig_xl0="inet 10.44.25.250 netmask > 255.255.255.252" > ifconfig_ep2="inet 10.44.17.222 netmask > 255.255.255.224" > ifconfig_ep1="inet 10.44.17.126 netmask > 255.255.255.224" > ifconfig_ep0="inet 10.44.17.62 netmask > 255.255.255.224" > defaultrouter="10.44.25.249" > > After logging into the router from the ep1 subnet I > tried to ping > out to all the subnets. The results are listed below: > > me@FBSD_Router1$ ping 10.44.17.38 > PING 10.44.17.38 (10.44.17.38): 56 data bytes > VIA ep0 > 64 bytes from 10.44.17.38: icmp_seq=0 ttl=128 > time=1.114 ms > 64 bytes from 10.44.17.38: icmp_seq=1 ttl=128 > time=0.645 ms > 64 bytes from 10.44.17.38: icmp_seq=2 ttl=128 > time=0.594 ms > 64 bytes from 10.44.17.38: icmp_seq=3 ttl=128 > time=0.596 ms > 64 bytes from 10.44.17.38: icmp_seq=4 ttl=128 > time=0.617 ms > 64 bytes from 10.44.17.38: icmp_seq=5 ttl=128 > time=0.611 ms > 64 bytes from 10.44.17.38: icmp_seq=6 ttl=128 > time=0.613 ms > 64 bytes from 10.44.17.38: icmp_seq=7 ttl=128 > time=0.608 ms > > me@FBSD_Router1$ ping 10.44.17.105 > PING 10.44.17.105 (10.44.17.105): 56 data bytes > VIA ep1 > 64 bytes from 10.44.17.105: icmp_seq=0 ttl=128 > time=0.722 ms > 64 bytes from 10.44.17.105: icmp_seq=1 ttl=128 > time=0.600 ms > 64 bytes from 10.44.17.105: icmp_seq=2 ttl=128 > time=0.587 ms > 64 bytes from 10.44.17.105: icmp_seq=3 ttl=128 > time=0.610 ms > 64 bytes from 10.44.17.105: icmp_seq=4 ttl=128 > time=0.578 ms > > me@FBSD_Router1$ ping 10.44.17.200 > VIA ep2 > ping: sendto: No buffer space available > ping: sendto: No buffer space available > ping: sendto: No buffer space available > ping: sendto: No buffer space available (Apparently > this is the problem.) > ping: sendto: No buffer space available > ping: sendto: No buffer space available > ping: sendto: No buffer space available > > me@FBSD_Router1$ ping 10.44.12.150 > PING 10.44.12.150 (10.44.12.150): 56 data bytes > VIA xl0 > 64 bytes from 10.44.12.150: icmp_seq=0 ttl=254 > time=1.629 ms > 64 bytes from 10.44.12.150: icmp_seq=1 ttl=254 > time=1.754 ms > 64 bytes from 10.44.12.150: icmp_seq=2 ttl=254 > time=1.665 ms > > I had found in the past that if I down the adapter ep2 > and brought > it back up again the communications would resume so > that is what > the shellscript "updown2" does. > > me@FBSD_Router1$ su root -c updown2 > Password: > ep2: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> > mtu 1500 > inet 10.44.17.222 netmask 0xffffffe0 broadcast > 10.44.17.223 > inet 10.54.17.222 netmask 0xffffffe0 broadcast > 10.54.17.223 > ether 00:a0:24:23:70:cc > ep2: > flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu > 1500 > inet 10.44.17.222 netmask 0xffffffe0 broadcast > 10.44.17.223 > inet 10.54.17.222 netmask 0xffffffe0 broadcast > 10.54.17.223 > ether 00:a0:24:23:70:cc > > Once I bring the adapter down and back up again it > apparently > functions fine (for a while at least. See below.) > What should I > do now?? > Replace the adapter? > Make some configuration change for that adapter in my > Kernel? > Update to v3.5? (The last time I cvsup'ed was prior > to the > router going online for real work.) > Or... What other config file do you want to see? > > me@FBSD_Router1$ ping 10.44.17.200 > PING 10.44.17.200 (10.44.17.200): 56 data bytes > VIA ep2 > 64 bytes from 10.44.17.200: icmp_seq=0 ttl=128 > time=0.641 ms > 64 bytes from 10.44.17.200: icmp_seq=1 ttl=128 > time=0.588 ms > 64 bytes from 10.44.17.200: icmp_seq=2 ttl=128 > time=0.568 ms > 64 bytes from 10.44.17.200: icmp_seq=3 ttl=128 > time=0.591 ms > 64 bytes from 10.44.17.200: icmp_seq=4 ttl=128 > time=0.575 ms > 64 bytes from 10.44.17.200: icmp_seq=5 ttl=128 > time=0.566 ms > ^C > --- 10.44.17.200 ping statistics --- > 6 packets transmitted, 6 packets received, 0% packet > loss > round-trip min/avg/max/stddev = > 0.566/0.588/0.641/0.025 ms > me@FBSD_Router1$ > > ===== > -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- > Ben Hacker Jr Technical Specialist > Computer Sciences Corporation > (703) 289-3477 MC 291 > bhacker1@csc.com 3170 Fairview Park Drive > strben@altavista.com Falls Church, VA 22304 > -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- > > __________________________________________________ > Do You Yahoo!? > Kick off your party with Yahoo! Invites. > http://invites.yahoo.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?398A3814.FF8C39F6>