All tests ran on fresh install, after I was getting the "better" speeds. The old install was getting KB second transfers on all files. The new install, well see my last post. I have tested connected to the eth0 port but got slower speeds on the eth1 port. So one thing at a time.
First the results of the test's you wanted. I'll do some hardware testing this weekend. I have a cable tester I can use, as for testing the nics them self's I'll use IPERF..
First of all, try to understand (draw) your connection. What's your WAN interface, what's your LAN interface (fe in my case is LAN: eth0, WAN: eth1). This way you know where you're looking. A picture is saying a lot more then some words.
Been their done that, networking 101 I have a quick and dirty google doc if you can send me an email. I'm not a complete noob
just no expert.
I'll put some basic test here that can point you to the right place where to look...
Can you connect with ssh to your core? I'll assume you're using a linux client.
With ifconfig, you'll see a lot more about your network cards.
ifconfig-> do you see any errors on the interfaces (collisions)? In fact, you should only see RX/TX packets here...
-> What the subnetmask of you interfaces (the same as for your routing table)?
eth0 Link encap:Ethernet HWaddr 20:cf:30:c0:ff:46
inet addr:192.168.3.80 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fe80::22cf:30ff:fec0:ff46/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:643754728 errors:0 dropped:3991875718 overruns:0 frame:0
TX packets:156841564 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:1054057917 (1.0 GB) TX bytes:1290091923 (1.2 GB)
I noticed the dropped packets this many raises a flag
For more information, you can always do following:
sudo ethtool -S eth0This should give you more information:
$ sudo ethtool -S eth0
Not perfect but nothing big here.
netstat -rn-> should give you a clear routing table
$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.80.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
220.127.116.11 0.0.0.0 255.0.0.0 U 0 0 0 eth1
0.0.0.0 192.168.3.1 0.0.0.0 UG 0 0 0 eth0
With a traceroute you'll see the connection path. This is useful to see where your connections goes, and if any devices are taking a long time to respond.
This is best done from you client machine on (i don't have direct access to a client now, so i can't show you my result, sorry).
fe (this is done from another network, so it won't be the same for you). The most important thing in here are the first lines, with your private ip's, and the first public ip (your internetrouter):
$ traceroute linuxmce.org
traceroute to linuxmce.org (18.104.22.168), 30 hops max, 40 byte packets
1 192.168.3.1 (192.168.3.1) 0.668 ms 1.804 ms 2.200 ms
2 X.X.X.X (X.X.X.X) 8.378 ms 12.214 ms 13.201 ms
3 XX.XX.XX.XXX.com (XX.XX.XX.XX) 13.566 ms 13.753 ms 13.921 ms
4 XXX.XX.XX.XX.com (XX.XX.XX.XX) 19.750 ms 20.698 ms 23.063 ms
I marked out the IPs with XXs, why your having me test the out side network is beyond me.
Send us the results of this, from there on we can maybe start troubleshoot a bit more ...
Of course, it's best that you do all this tests from all the machines (or at least all the machines that are in the loop). This is the reason why i wrote that's always best to have a small drawing beside... This way, you can isolate the problem to a certain point/connection...