:>From the workstation:
:Name Mtu Network Ipkts Ierrs Opkts Oerrs Coll Drop
:fxp0 1500 <Link#1> 32102492 0 31653667 0 30900 0
:
:>From the fileserver:
:Name Mtu Network Ipkts Ierrs Opkts Oerrs Coll Drop
:xl0 1500 <Link> 32504173 28967 32900227 0 0 0
:
: I did find it a little unusual that I was getting collisions on a
:crossover cable, but when I looked at the mail archives related to that
:problem I read that the intel cards are very aggressive packet pushers,
:and that this isn't all that unusual. The ratio of good packets to
:collisions seemed healthy enough to not warrant too much concern.
28967 input errors on xl0? Problem!
But the real problem is that you are attempting to do 10BaseT
full-duplex. Full-duplex operation with 10BaseT is problematic
at best. Full duplex has good interoperability at 100BaseTX speeds,
but not at 10BaseT speeds.
Crossover cables work fine, usually, but I personally *never* use them.
I always throw a switch in between the machines and let it negotiate
the duplex mode with each machine independantly, plus it gives me nice
shiny LEDs that tell me what the switch thinks the port is doing as
a sanity check.
:always worked before. I ran 'ping -f' simultaneously on both hosts, and
:did experience a 4% packet loss on one host, and 1% on the other. Changing
:to an explicit:
:
:ifconfig fxp0 inet 10.0.0.2 netmask 255.255.255.0 media 10baseT/UTP
:mediaopt full-duplex
:
:gets me 0 packet loss on both sides. So you may be right Matt, it may be a
:network error after all. I'll give it another test run and see what I can
:see.
:...
:Thanks,
:
:Doug
Given what you've described, I'm dead certain it is (or was :-)).
p.s. Throw away your 10BaseT switches and hubs and go get 100BaseTX
switches, they're getting real cheap and modern machines can push the
bandwidth just fine (even the crappy cards). Don't buy HUBs (10 or 100),
switches are a whole lot faster and a whole lot easier to troubleshoot.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
