Just throwing this out there and see if anyone has any ideas.
I have an old P75 with 2 PCI slots and 4 ISA slots. I've been using this as a Bering 1.2 router at a customer location. They asked me to add an additional NIC to it to support another office's internet connection. While I was at it, I upgraded them to Bering uclibc 2.2.2.
I tested this router after it was completed, and got extremely bad throughput (around 50kbs from a local FTP server that can easily deliver
10MBs (that should be megabytes) per second.
I moved some things around, eliminated a 10MB hub, tried various nics (3c59x/tulip in the PCI, smc-ultra/wd in the ISA slots) and found the best throughput I could get was around 100kbs, and that was using all ISA cards!
My theory is that their is some sort of hardware problem with this machine which is limiting this. The slots are all on a riser card, and perhaps that thing is bad.
I'm going to install as is, and inform the customer that we need to replace the hardware.
Anyone have any alternative ideas why this thing is so slow?
Can you be a bit more specific about the setup details? Are you trying to describe a setup like this (I've standardized all numbers to bits, not a mix of bits and bytes the way I think you did):
eth0 - 10 (or 100) Mbps NIC connecting to the Internet
eth1 - 10 (or 100) Mbps NIC connecting to LAN A
eth2 - 10 (or 100) Mbps NIC connecting to LAN B ftp server on LAN A (probably a /24 private-address network)
ftp client on LAN B (probably a different
/24 private-address network from A)
LANs A and B have routes to each other (i.e., the router
does NOT NAT this traffic) ftp throughput is between 50 Kbps and 100 Kbps,
depending on NICs tested? ftp server actually does (not "can easily") deliver 80 Mbps
to an ftp client on LAN AIf I am making any fundamentally incorrect assumptions here, please correct me.
If not ... the first thing to check is whether the problem is specific to ftp or more general. Do scp transfers, for example, between the two LANs exhibit similar slowness?
After a slow transfer, what does "ip -s link show" report? Are there significant numbers of bad packets?
During a slow transfer, what does "top" report about CPU load? If this is high ... is the router running unusually complex iptables (Shorewall) rulesets? (If yes, please report the details.)
Do pings of the ftp server by the client show any unusual latency?
That diagnostic information, combined with the usual basics ("ip addr show"; "netstat -nr"; "more /proc/interrupts"; "more /proc/ioports", and enough description to let us know which eth* interface is associated with which LAN) and perhaps some details about the ftp server and client, should help folks spot the problem.
Also, I cannot tell if this same ftp transfer operated at better speeds under Bering 1.2 (or even if a test was possible, since you don't say how many NICs the old router had), so please clarify that detail.
------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
