Date: Tue, 5 Mar 2002 09:57:30 -0500 From: Bill Vermillion <bv@wjv.com> To: stable@FreeBSD.ORG Subject: Re: recent networking troubles Message-ID: <20020305145730.GB43968@wjv.com> In-Reply-To: <bulk.58273.20020305053448@hub.freebsd.org> References: <bulk.58273.20020305053448@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> ------------------------------ > > Date: Mon, 04 Mar 2002 09:16:52 -0800 > From: Michael Sierchio <kudzu@tenebras.com> > Subject: Re: recent networking troubles > > Peter Schultz wrote: > > > At system boot I see this message twice: > > Starting final network daemons:rpc.umntall: 10.0.0.103: RPCPROG_MNT: > > RPC: Port mapper failure - RPC: Unable to send > > That's normal -- your pccard stuff probably hasn't settled down yet, but > you've got nfs compiled into the kernel rather than using a lkm, right? > > > If I try to mount NFS exports I can only successfully do one, the others > > will fail with: > > 10.0.0.100:/usr/ports/distfiles: RPCPROG_MNT: RPC: Timed out > > What kind of network card are you using? Are you using DHCP, or do > you have a fixed address? And is there a hostname entry in the local > DNS in every local /etc/hosts for these hosts on the RFC 1918 net? > What's your network setup? > > > Another clue that something is wrong is when I try to ping one of my > > local machines: > > PING bebox.jocose.org (216.239.16.183): 56 data bytes > > 64 bytes from 216.239.16.183: icmp_seq=1 ttl=62 time=4035.362 > > 64 bytes from 216.239.16.183: icmp_seq=2 ttl=62 time=3025.446 > > 64 bytes from 216.239.16.183: icmp_seq=3 ttl=62 time=2015.578 > > 64 bytes from 216.239.16.183: icmp_seq=4 ttl=62 time=1005.654 > > 64 bytes from 216.239.16.183: icmp_seq=5 ttl=62 time=0.752 > That's pretty funny. If you keep pinging, do the times keep getting > smaller? ;-) You will see that if the network comes up before the previous byte is considered lost. I used to get a big screen flash up when my outgoing ppp hadn't finished negotiating. Notice that each of the first four is almost exactly 1 second [1000ms] smaller than the previous. The packets are sent one each second and the interface came up just about 4 seconds after the first ping was sent that is why the first ping reply took 4 seconds, the next 3, and so on. Bill -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020305145730.GB43968>