[SOLVED] Fedora 14 Slow outbound ethernet

[japettyjohn]

Just started recently on a fedora 14 machine where my upload speed between 2 machines on gigabit switches over SFTP went from 11-12mbs to 33kbs.

I have tried the following: restarted the network service, FTP instead of SFTP, restarted the machine, checked the cables, used iptraf and found nothing really going on, testing sftp to the machine I'm normally sending from and it was 12mbs and tried uploading from another machine to the same endpoint and the speed was about 12mbs. Only outbound from this machine to anywhere is dog slow.

Iptables is not on. I'm tapped for ideas.

[Dan]

F14 is End Of Life. (No longer supported by updates.)

Moved to EOL.

[japettyjohn]

Just started recently on a fedora 14 machine where my upload speed between 2 machines on gigabit switches over SFTP is now 33kbs when it was 11-12mbs.

I have tried the following: restarted the network service, FTP instead of SFTP, restarted the machine, checked the cables, used iptraf and found nothing really going on, testing sftp to the machine I'm normally sending from and it was 12mbs and tried uploading from another machine to the same endpoint and the speed was about 12mbs. Only outbound from this machine to anywhere is dog slow.

Iptables is not on. I'm tapped for ideas.

[stevea]

I'd run wireshare and look at where the delays are occurring.
nuttcp is a better tool and can help instrument one-way UDP traffic.
I predict your thread will be moved to legacy.

[japettyjohn]

Thanks for the suggestions - nuttcp is awesome and I'd never heard of it before.

So I'm getting 94Mbps inbound and a solid 0.2922 Mbs outbound.

Hard to tell with wireshark on that.

Now I just wiresharked HTTP, once for each direction. Same results but for the outbound there are 3 TCP Out-Of-Order messages every 4 packet. So far I haven't found anything to indicate why.

Seems odd that it could be a bad NIC card given the inbound is just fine.

[Dan]

japettyjohn:

OK. I move this to EOL yesterday, and now you've opened another one. Bzzzzz! Wrong answer! <....>

Please have a careful read through the guidelines and posting rules ...

(In a typical Godfather accent) ... and don't make me hafta come do dis again. <..:insert violin music here:..> <....>

Threads merged ... in EOL.

[japettyjohn]

Looks like this was an issue with the CISCO I was plugged into. Wireshark indicated this was possible, looks like my packets were being managled coming out the machine.

[stevea]

Makes sense. The out of order problem typically occurs when packets are lost somewhere along the line.

With wireshark on tcp you can config it to follow one connection. If there is a big delay between a packet and the receive ACK it implies a remote problem.