> > As I said, I used ttcp. ttcp is a "network only" test - it can source > > or sink traffic itself. This is nice because you avoid other sources of > > problems (disk bandwidth etc). I tended to run the tests for 30 seconds > > to one minute. > > Oops, must have missed that one. How do I do the ttcp test? By reading the man page? (This is no longer freebsd-hackers stuff, methinks...) ttcp -r on the receiver and ttcp -t on the sender is a good start. Proceed from there. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: poor ethernet performance? Vincent Poy
- Sv: poor ethernet performance? Leif Neland
- Re: Sv: poor ethernet performance? Vincent Poy
- Re: poor ethernet performance? Karl Pielorz
- Re: poor ethernet performance? sthaug
- Re: poor ethernet performance? Vincent Poy
- Re: poor ethernet performance? sthaug
- Re: poor ethernet performance? Vincent Poy
- Re: poor ethernet performance? sthaug
- Re: poor ethernet performance? Vincent Poy
- Re: poor ethernet performance? sthaug
- Re: poor ethernet performance? Vincent Poy
- Re: poor ethernet performance? Vincent Poy
- Re: poor ethernet performance? Modred
- Re: poor ethernet performance? Vincent Poy
- Re: poor ethernet performance? Matthew Dillon
- Re: poor ethernet performance? Vincent Poy
- Re: poor ethernet performance? Matthew Dillon
- Re: poor ethernet performance? Vincent Poy
- Re: poor ethernet performance? Leif Neland
- Re: poor ethernet performance? sthaug