Re: FreeBSD 5.3 Networking performance problem

From: Eli Dart (dart_at_nersc.gov)
Date: 11/29/04

  • Next message: Andrew Seguin: "RE: FreeBSD 5.3 Networking performance problem"
    To: Andrew Seguin <asegu@borgtech.ca>, freebsd-net@freebsd.org
    Date: Mon, 29 Nov 2004 08:38:02 -0800
    
    
    

    > [ ... ]
    > > I then tested with the whole school going through the firewall: very bad.
    > > packets were being droped and ping times were around 600ms. Internet was
    > > pretty much unuseable.
    >
    > This report sounds consistent, although you could also have a bad cable or
    > switch port, too. It would be useful to you to look into the output of
    > "netstat -i" and "netstat -s", and any statistics which might be available on
    > your switches (if they have management & per-port stats).

    The other thing to check is your duplex settings. Your host
    interface and/or switch interface may be picking the wrong setting
    when it attempts to autonegotiate. If you have an unmanaged switch
    (or don't have access) you can manually set the interface to full or
    half duplex using ifconfig. In my experience, Foundry switches tend
    to autoneg correctly if the host side is set to auto, and guess wrong
    if the host is set to a specific setting. Cisco switches are
    variable, depending on model and IOS version.

    Note that if your interface is set to full duplex and the switch is
    set to half, you'll see lousy performance and very likely see no
    errors on your side.

                    --eli

    >
    > --
    > -Chuck
    >
    > _______________________________________________
    > freebsd-net@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-net
    > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
    >

    
    



  • Next message: Andrew Seguin: "RE: FreeBSD 5.3 Networking performance problem"

    Relevant Pages

    • Re: two NICs and speed issues
      ... > So if you disconnect the modem the transfers are fast on the ... > will give you a listing of each interface. ... > connections you want to have full duplex set. ... > between the NIC and the switch you will see the error count increase ...
      (Fedora)
    • RE: Duplicate Echo Replies with Channel Bonding
      ... An "ifconfig -a" shows the failover interface with the NOARP parameter ... >the active interface transmits packets. ... >When both eth0 and eth1 are up and I ping from Host C to Host A I get ... Switch B does not have the MAC address in its MAC address ...
      (RedHat)
    • Re: slow sftp/scp access despite fast network
      ... seems extraordinarily slow for transfers on the local machine... ... > (p.s., tried the usual net-problem charachters of switch, full/half duplex ... I definitely would have jumped on duplex being the issue... ... fairly often that the switch autonegotiates to 100Mb/Full but the host ...
      (SSH)
    • Duplicate Echo Replies with Channel Bonding
      ... the active interface transmits packets. ... When both eth0 and eth1 are up and I ping from Host C to Host A I get ... Switch B does not have the MAC address in its MAC address table ...
      (RedHat)
    • RE: started getting repeated "bge0: PHY read timed out" messages
      ... Have you looked at the output of 'netstat -i' to see if there are ... have you looked at the switch-side interface ... negotiation which ended up at 1000tx full duplex to now be 100tx at ... between switch and server. ...
      (freebsd-questions)