Dnia 16-11-2004, Wto o godzinie 13:38 +1030, Daniel O'Connor napisa(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
On Tue, 16 Nov 2004 19:22, Tomek Tylec wrote:
I've found vr(4) devices (which are very common in Via chipset
motherboards) don't like talking to some switches and I need to force
half duplex then unplug and replug the cable :(
I've tried all possible combinations with media and mediaopts,
Dnia 16-11-2004, Wto o godzinie 20:08 +1030, Daniel O'Connor napisa(a):
Hmm, I'm not sure what changed sorry - perhaps you could look for changes in
the code by using cvsweb.freebsd.org.
I made an experiment. I downloaded if_vr.c from cvs which was tagged as
5.2.1-RELEASE. Then I substituted
I think that something is wrong with VIA Rhine II network device driver.
I run FreeBSD 5.3. Behaviour of network seems to be random: one time
everything is OK but a second later I can't connect to host in my local
network. But when I connect to other host, not in my network and then
try to connect
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).
Zoltan
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
