Dan Nelson wrote:
In the last episode (Mar 16), Olivier Dony said:
o On the server I was talking about earlier, here is an excerpt of
netstat while switching from half to full-duplex and back :
input (Total) output
packets errs bytes packets errs bytes colls
900 0 141953 1261 0 1351094 633
-> going full-duplex... here I guess
462 12 61552 546 0 649187 0
-> back to half-duplex with autoselect .. looks like here
815 0 150286 1128 0 1841082 749
The input errors and other numbers were consistent during the few
minutes of testing in all 3 cases, but I cut it to a few lines for
the sake of the mailing-list. Is this increase in input errors and
drop in bytes throughput a problem? I guess the input errors are not
good, when we can see that there are
Input errors probably means that whatever you're plugged into does not
support full-duplex (i.e. it's a hub), which is why autoselect selected
half-duplex.
You know, now that he brings this up, I tend to agree.
It's possible that the hub you're plugging into is saturated: that will
result in high collision rates and poor performance. You won't get
anything better because that's the best the hub can do.
If I'm right on this guess, you need to take it up with your ISP, as it's
something they need to address.
--
Bill Moran
Potential Technologies
http://www.potentialtech.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
