On 19/08/2010 09:03, Antonio Kless wrote: > # ifconfig igb0 media 100BaseTX > # ifconfig igb0 > igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4> > ether 00:30:48:de:9a:4e > inet 1.2.3.4 netmask 0xffffff00 broadcast 1.2.3.255 > media: Ethernet 100baseTX (100baseTX <half-duplex>) > status: active > > # scp -C u...@remote-server.net:/usr/bak/* /usr/bak > Password: > dump.2010.08.19_07-46-58.sql > 100% 1291MB 3.1MB/s 07:00 > > > That's works! But why half-duplex? Go next:
Connections running at half-duplex is a classic sign of a mismatch
between you and your provider's ideas about using autonegotiation on the
connection. Either you both configure your network interfaces to
autoneg, or neither of you do. No, it's not good enough to force your
NIC to be fixed to the settings it would have had through
autonegotiation: that will cause the *other* end of the connection to
run at half-duplex.
Looks like you should certainly be using autoneg -- the corrupted MAC is
probably a symptom of some other problem. Possibly hardware troubles.
Eliminate the cheap stuff first: check network cables for kinks or
breakages, swap out for fresh ones, replug jacks into sockets.
Try alternative NICs if you have them available.
FreeBSD doesn't have a setting that lets you specify the max speed you
want a NIC to run at while still allowing autoneg up to that speed --
which is something that a number of higher-end switches do provide -- so
if you need bandwidth limitation, you should look into using dummynet or
ALTQ.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
