Regular Visitor
•
6 Messages
Slow connection to my home server
I work/play remotely sometimes from a different location where I have Comcast internet.
A. Home - on AT&T 100 fiber
B. Work - Comcast on Performance Internet
Generally, using the internet is plenty fast as I would expect. Except if I need to access files on my home server (large media files and CAD files).
I was seeing slow file transfers from Work to Home. Super slow.
Testing against a server at home, I run `iperf` (I'm on linux in both locations) from a server in NJ to my house to get a general baseline of speeds to that server:
root@NJ ~ # iperf3 -p 22 -c HOME Connecting to HOME, port 22 [ 5] local 45.79.131.243 port 38884 connected to xxx.xxx.xxx.xxx port 22 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 13.7 MBytes 115 Mbits/sec 39 683 KBytes [ 5] 1.00-2.00 sec 13.8 MBytes 115 Mbits/sec 0 775 KBytes [ 5] 2.00-3.00 sec 13.8 MBytes 115 Mbits/sec 9 591 KBytes [ 5] 3.00-4.00 sec 12.5 MBytes 105 Mbits/sec 0 634 KBytes [ 5] 4.00-5.00 sec 15.0 MBytes 126 Mbits/sec 0 659 KBytes [ 5] 5.00-6.00 sec 13.8 MBytes 115 Mbits/sec 0 673 KBytes [ 5] 6.00-7.00 sec 15.0 MBytes 126 Mbits/sec 0 680 KBytes [ 5] 7.00-8.00 sec 13.8 MBytes 116 Mbits/sec 0 680 KBytes [ 5] 8.00-9.00 sec 13.8 MBytes 115 Mbits/sec 0 680 KBytes [ 5] 9.00-10.00 sec 15.0 MBytes 126 Mbits/sec 0 683 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 140 MBytes 117 Mbits/sec 48 sender [ 5] 0.00-10.00 sec 137 MBytes 115 Mbits/sec receiver iperf Done.
I'm seeing expected speeds from other servers on the internet back to the HOME network.
So testing from WORK to HOME:
$ iperf -p 22 -c HOME ------------------------------------------------------------ Client connecting to HOME, TCP port 22 TCP window size: 64.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.23 port 8267 connected with xxx.xxx.xxx.xxx port 22 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 7.38 MBytes 6.15 Mbits/sec
To re-iterate - that's giving me 6.15 Mbits/second... (Performance internet is supposed to be around 60 Mbits/s.
This is roughly the same after a few dozen tests at various times throughout the day.
Here's the kicker. If I create an SSH tunnel from WORK to HOME
$ ssh HOME -L 22:localhost:22
and then re-run the iperf test through the SSH tunnel:
$ iperf -p 22 -c localhost ------------------------------------------------------------ Client connecting to localhost, TCP port 22 TCP window size: 64.0 KByte (default) ------------------------------------------------------------ [ 3] local 127.0.0.1 port 8282 connected with 127.0.0.1 port 22 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 163 MBytes 137 Mbits/sec
Just to clarify, connecting from WORK to HOME through an SSH tunnel lets me see 137 Mbits/s of transfer - awesome!
Connecting from WORK to HOME across the internet shows me 6.15 Mbits/s.
The raw speed is obviously there without a problem as evidenced by the speeds through an SSH tunnel.
So what is going on here? Why would my speeds be so poor in this one specific instance to this particular server?
@ComcastJohnN or @ComcastChe ?
Broomsweeper
Contributor
•
116 Messages
6 years ago
run iperf Work to Home test without tunneling using a different port other than port 22 because sshd listens on that port as well.
I think this is affecting the reading you get when hitting port 22 with your Work to Home test (that is without tunneling) because sshd thinks it is being attacked and is limiting badwidth?
Am not sure.
But change the port with that Non tunneling test you do to a non port 22 one for starters.
0
0
pat-david
Regular Visitor
•
6 Messages
6 years ago
I've got my ssh running on a different port for these tests.
There is nothing listening on port 22 other than the iperf server.
To test, I re-did everything using port 80, and I'm still seeing a measly 6.5 Mbit/sec transfer (no ssh tunnel)...
0
0
pat-david
Regular Visitor
•
6 Messages
6 years ago
Just tested again to see if it might be dependent on day.
Nope. Still awful.
NJ = Server in NJ
WORK = Comcast performance internet from my off-site location
WORK2 = Separate network (ATT) elsewhere in my city
These are all testing speeds back to my home (ATT Fiber) server:
Something is happening on the Comcast side that is severly effecting my speeds to my server (again, on an AT&T fiber connection) at home.
Is this known? Is there something Comcast is doing to throttle this speed so much when it's fine from other locations, and even worse, just fine when tested through an encrypted SSH tunnel?
@ComcastJohnN or @ComcastChe do you have any insight to add here?
0
0