Date: Tue, 16 Nov 2004 09:52:30 +0100 From: Tomek Tylec <my-buziaki@interecho.com> To: Daniel O'Connor <doconnor@gsoft.com.au>, freebsd-stable@freebsd.org Subject: Re: VIA Rhine II network card Message-ID: <1100595150.614.6.camel@agape> In-Reply-To: <200411161338.52340.doconnor@gsoft.com.au> References: <000201c4cb88$03b76d40$e001a8c0@p4> <200411161338.52340.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Dnia 16-11-2004, Wto o godzinie 13:38 +1030, Daniel O'Connor napisa=B3(a): > On Tue, 16 Nov 2004 13:27, Zoltan Frombach wrote: > > It could be a full-duplex/half duplex mismatch issue. Try not to use > > auto-negotiation. You can set your interface to "fixed" full-duplex (or > > half-duplex) in /etc/rc.conf You must match the setting with the other > > side of your connection (eg. your switch). >=20 > I've found vr(4) devices (which are very common in Via chipset motherboar= ds)=20 > don't like talking to some switches and I need to force half duplex then=20 > unplug and replug the cable :( >=20 I've tried all possible combinations with media and mediaopts, and I get nothing. When I try to set half-duplex it doesn't work at all. I didn't mentioned before that under FreeBSD 4.10 everything worked fine. I found also some interesting (but not clear for me) behaviour of ping: $ ping 213.25.86.88 [cut few lines] 64 bytes from 213.25.86.88: icmp_seq=3D5 ttl=3D64 time=3D0.311 ms 64 bytes from 213.25.86.88: icmp_seq=3D6 ttl=3D64 time=3D0.944 ms 92 bytes from 192.168.3.1: Redirect Host(New addr: 213.25.86.88) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 0105 0 0000 40 01 8a7d 192.168.3.13 213.25.86.88 64 bytes from 213.25.86.88: icmp_seq=3D7 ttl=3D64 time=3D0.314 ms 64 bytes from 213.25.86.88: icmp_seq=3D8 ttl=3D64 time=3D0.288 ms I'm not local network, my IP is 192.168.3.13, 192.168.3.1 is my gateway.=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1100595150.614.6.camel>