Date: Thu, 23 Mar 2000 07:20:36 -0800 (PST) From: David Daugherty <doc@wcug.wwu.edu> To: Martin MacT <martinm@visualedge.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Setting up a box to use remotely by way of an X-server Message-ID: <Pine.LNX.3.96.1000323071523.16887A-100000@sloth> In-Reply-To: <03ae01bf94d8$0d7bb0c0$7400a8c0@visualedge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 23 Mar 2000, Martin MacT wrote: > Well, I bought a new hub, and, um... well, it still don't work, though I > think that I do get less packet loss now (72% instead of about 79%)... > > Could it be because my card (macronix 98715 based NC-100 from LinkSys) > is set to half duplex instead of full? Also, it seems pretty consistent: > It's good for right around 500 pings, then goes down for aprroximately 820 > seconds and then comes back for 500 pings or so... Well, I suppose I'd start swapping NICs around. It could be the NIC is bad also. That is what I originally did before I realized my hub was bad. Try putting a known reliable NIC in there. Unless you're doing something weird it should be running at half-duplex. You should see something similar to below in your /var/log/messages Mar 19 12:44:06 roosevelt /kernel: pn1: <82c169 PNIC 10/100BaseTX> rev 0x20 int a irq 12 on pci0.11.0 Mar 19 12:44:06 roosevelt /kernel: pn1: Ethernet address: 00:a0:cc:28:81:a0 Mar 19 12:44:06 roosevelt /kernel: pn1: autoneg complete, link status good (half-duplex, 100Mbps) Of course the computer name (roosevelt) and device name (pn1) will most probably be different. David doc@wcug.wwu.edu Washington State Resident ICQ 21106703 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?Pine.LNX.3.96.1000323071523.16887A-100000>