High latency when more than one lan cable plugged into modem

D

dotcat

Expert Member
Joined
Nov 18, 2005
Messages
1,154
Reaction score
263
Location
kzn
This started a few days back. I have billion adsl modem that has been rock steady. Now when I connect my pc directly to the modem I get 20ms ping time to google.co.za. As soon as I connect a wireless router (i have tried 3) pings go through the roof. 500ms to 1000ms. This is with the pc still connected via lan cable. Disconnect the wireless router and ping is back down to 20ms. modem has latest firmware.

Any ideas?
 
Is there anything connected to the the wireless router, like a laptop or something ?
 
i connect my mobile phone to the wireless - but very little traffic as I am not downloading anything..
 
can you check the below:

Has the billion router and wireless AP got different IP address ?
Have you tried a different LAN cable and port on the billion
Can you change the wireless password to make 100% sure nothing is connected to it for the test.

We just got to be 100% sure that nothing is sending traffic and saturating the upload of the DSL, hence induced latency.
 
Last edited:
Is it the latency to the modem that is that high or the latency to the first hop on the Internet?

Perhaps your wireless routers are sending lots of data and thus saturating your Internet link, causing the high ping values.
 
Has the billion router and wireless AP got different IP address ? yes
Have you tried a different LAN cable and port on the billion yes - no change
Can you change the wireless password to make 100% sure nothing is connected to it for the test. yes changed to new ssid.
I have done some further testing....

Running a speedtest from speedtest.net while pinging google.co.za

PING www.google.co.za (74.125.233.87): 56 data bytes
64 bytes from 74.125.233.87: icmp_seq=0 ttl=54 time=21.973 ms
64 bytes from 74.125.233.87: icmp_seq=1 ttl=54 time=22.066 ms
64 bytes from 74.125.233.87: icmp_seq=2 ttl=54 time=20.980 ms
64 bytes from 74.125.233.87: icmp_seq=3 ttl=54 time=22.017 ms
64 bytes from 74.125.233.87: icmp_seq=4 ttl=54 time=21.986 ms
64 bytes from 74.125.233.87: icmp_seq=5 ttl=54 time=21.416 ms
64 bytes from 74.125.233.87: icmp_seq=6 ttl=54 time=21.913 ms
64 bytes from 74.125.233.87: icmp_seq=7 ttl=54 time=21.791 ms
64 bytes from 74.125.233.87: icmp_seq=8 ttl=54 time=21.541 ms
64 bytes from 74.125.233.87: icmp_seq=9 ttl=54 time=129.139 ms
64 bytes from 74.125.233.87: icmp_seq=10 ttl=54 time=79.088 ms
64 bytes from 74.125.233.87: icmp_seq=11 ttl=54 time=116.552 ms
64 bytes from 74.125.233.87: icmp_seq=12 ttl=54 time=77.661 ms
64 bytes from 74.125.233.87: icmp_seq=13 ttl=54 time=114.842 ms
64 bytes from 74.125.233.87: icmp_seq=14 ttl=54 time=98.209 ms
64 bytes from 74.125.233.87: icmp_seq=15 ttl=54 time=79.127 ms
64 bytes from 74.125.233.87: icmp_seq=16 ttl=54 time=106.091 ms
64 bytes from 74.125.233.87: icmp_seq=17 ttl=54 time=91.744 ms
64 bytes from 74.125.233.87: icmp_seq=18 ttl=54 time=96.434 ms
64 bytes from 74.125.233.87: icmp_seq=19 ttl=54 time=97.402 ms
64 bytes from 74.125.233.87: icmp_seq=20 ttl=54 time=91.383 ms
64 bytes from 74.125.233.87: icmp_seq=21 ttl=54 time=74.568 ms
64 bytes from 74.125.233.87: icmp_seq=22 ttl=54 time=72.104 ms
64 bytes from 74.125.233.87: icmp_seq=23 ttl=54 time=69.438 ms
64 bytes from 74.125.233.87: icmp_seq=24 ttl=54 time=75.024 ms
64 bytes from 74.125.233.87: icmp_seq=25 ttl=54 time=21.759 ms
64 bytes from 74.125.233.87: icmp_seq=26 ttl=54 time=20.691 ms
64 bytes from 74.125.233.87: icmp_seq=27 ttl=54 time=21.563 ms
64 bytes from 74.125.233.87: icmp_seq=28 ttl=54 time=834.896 ms
Request timeout for icmp_seq 29
64 bytes from 74.125.233.87: icmp_seq=29 ttl=54 time=1136.143 ms
64 bytes from 74.125.233.87: icmp_seq=30 ttl=54 time=901.794 ms
64 bytes from 74.125.233.87: icmp_seq=31 ttl=54 time=643.636 ms
64 bytes from 74.125.233.87: icmp_seq=32 ttl=54 time=863.976 ms
64 bytes from 74.125.233.87: icmp_seq=33 ttl=54 time=1061.518 ms
64 bytes from 74.125.233.87: icmp_seq=34 ttl=54 time=619.797 ms
64 bytes from 74.125.233.87: icmp_seq=35 ttl=54 time=479.609 ms
64 bytes from 74.125.233.87: icmp_seq=36 ttl=54 time=394.375 ms
64 bytes from 74.125.233.87: icmp_seq=37 ttl=54 time=282.272 ms
64 bytes from 74.125.233.87: icmp_seq=38 ttl=54 time=490.536 ms
64 bytes from 74.125.233.87: icmp_seq=39 ttl=54 time=564.881 ms
64 bytes from 74.125.233.87: icmp_seq=40 ttl=54 time=829.761 ms
64 bytes from 74.125.233.87: icmp_seq=41 ttl=54 time=465.451 ms
64 bytes from 74.125.233.87: icmp_seq=42 ttl=54 time=189.383 ms
64 bytes from 74.125.233.87: icmp_seq=43 ttl=54 time=21.249 ms

you will see that before the speedtest starts in it around 20ms
download portion around 100ms and then upload portion even up to 1000ms
then as soon as the speedtest finishes it is back to 20ms.
 
This is normal dotcat.

Your latency will spike heavily once your downlink/uplink gets saturated (thats exactly what speedtest does). Its not like you have infinite bandwidth at your disposal...

So this test doesn't really tell you anything that might help in solving the problem.


dotcat said:
Has the billion router and wireless AP got different IP address ? yes
Have you tried a different LAN cable and port on the billion yes - no change
Can you change the wireless password to make 100% sure nothing is connected to it for the test. yes changed to new ssid.
I have done some further testing....

Running a speedtest from speedtest.net while pinging google.co.za

PING www.google.co.za (74.125.233.87): 56 data bytes
64 bytes from 74.125.233.87: icmp_seq=0 ttl=54 time=21.973 ms
64 bytes from 74.125.233.87: icmp_seq=1 ttl=54 time=22.066 ms
64 bytes from 74.125.233.87: icmp_seq=2 ttl=54 time=20.980 ms
64 bytes from 74.125.233.87: icmp_seq=3 ttl=54 time=22.017 ms
64 bytes from 74.125.233.87: icmp_seq=4 ttl=54 time=21.986 ms
64 bytes from 74.125.233.87: icmp_seq=5 ttl=54 time=21.416 ms
64 bytes from 74.125.233.87: icmp_seq=6 ttl=54 time=21.913 ms
64 bytes from 74.125.233.87: icmp_seq=7 ttl=54 time=21.791 ms
64 bytes from 74.125.233.87: icmp_seq=8 ttl=54 time=21.541 ms
64 bytes from 74.125.233.87: icmp_seq=9 ttl=54 time=129.139 ms
64 bytes from 74.125.233.87: icmp_seq=10 ttl=54 time=79.088 ms
64 bytes from 74.125.233.87: icmp_seq=11 ttl=54 time=116.552 ms
64 bytes from 74.125.233.87: icmp_seq=12 ttl=54 time=77.661 ms
64 bytes from 74.125.233.87: icmp_seq=13 ttl=54 time=114.842 ms
64 bytes from 74.125.233.87: icmp_seq=14 ttl=54 time=98.209 ms
64 bytes from 74.125.233.87: icmp_seq=15 ttl=54 time=79.127 ms
64 bytes from 74.125.233.87: icmp_seq=16 ttl=54 time=106.091 ms
64 bytes from 74.125.233.87: icmp_seq=17 ttl=54 time=91.744 ms
64 bytes from 74.125.233.87: icmp_seq=18 ttl=54 time=96.434 ms
64 bytes from 74.125.233.87: icmp_seq=19 ttl=54 time=97.402 ms
64 bytes from 74.125.233.87: icmp_seq=20 ttl=54 time=91.383 ms
64 bytes from 74.125.233.87: icmp_seq=21 ttl=54 time=74.568 ms
64 bytes from 74.125.233.87: icmp_seq=22 ttl=54 time=72.104 ms
64 bytes from 74.125.233.87: icmp_seq=23 ttl=54 time=69.438 ms
64 bytes from 74.125.233.87: icmp_seq=24 ttl=54 time=75.024 ms
64 bytes from 74.125.233.87: icmp_seq=25 ttl=54 time=21.759 ms
64 bytes from 74.125.233.87: icmp_seq=26 ttl=54 time=20.691 ms
64 bytes from 74.125.233.87: icmp_seq=27 ttl=54 time=21.563 ms
64 bytes from 74.125.233.87: icmp_seq=28 ttl=54 time=834.896 ms
Request timeout for icmp_seq 29
64 bytes from 74.125.233.87: icmp_seq=29 ttl=54 time=1136.143 ms
64 bytes from 74.125.233.87: icmp_seq=30 ttl=54 time=901.794 ms
64 bytes from 74.125.233.87: icmp_seq=31 ttl=54 time=643.636 ms
64 bytes from 74.125.233.87: icmp_seq=32 ttl=54 time=863.976 ms
64 bytes from 74.125.233.87: icmp_seq=33 ttl=54 time=1061.518 ms
64 bytes from 74.125.233.87: icmp_seq=34 ttl=54 time=619.797 ms
64 bytes from 74.125.233.87: icmp_seq=35 ttl=54 time=479.609 ms
64 bytes from 74.125.233.87: icmp_seq=36 ttl=54 time=394.375 ms
64 bytes from 74.125.233.87: icmp_seq=37 ttl=54 time=282.272 ms
64 bytes from 74.125.233.87: icmp_seq=38 ttl=54 time=490.536 ms
64 bytes from 74.125.233.87: icmp_seq=39 ttl=54 time=564.881 ms
64 bytes from 74.125.233.87: icmp_seq=40 ttl=54 time=829.761 ms
64 bytes from 74.125.233.87: icmp_seq=41 ttl=54 time=465.451 ms
64 bytes from 74.125.233.87: icmp_seq=42 ttl=54 time=189.383 ms
64 bytes from 74.125.233.87: icmp_seq=43 ttl=54 time=21.249 ms

you will see that before the speedtest starts in it around 20ms
download portion around 100ms and then upload portion even up to 1000ms
then as soon as the speedtest finishes it is back to 20ms.
Click to expand...
 
Thanks for your help and I feel a bit stupid. I believe I have solved the problem. So all 3 of my Android devices had received an update which enabled autobackup. This includes the local folders on the devices. So 3x16GB upload going on in the background saturating the upload ....hence the massive latencies.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X