Jump to content

Ping Issues


Recommended Posts

I've disconnected ny netduma, on Friday my upload/download halved and the ping doubled. Thought it was my IPS that what causing the problem, test it tonight without the Netduma and all seems fine.

Can you guys advise on anything that might help the connection with the netduma?

Link to comment
Share on other sites

  • Replies 68
  • Created
  • Last Reply
  • Netduma Staff

I've disconnected ny netduma, on Friday my upload/download halved and the ping doubled. Thought it was my IPS that what causing the problem, test it tonight without the Netduma and all seems fine.

Can you guys advise on anything that might help the connection with the netduma?

 

How are you measuring the pings with and without the Netduma? Also what are the bandwidth speeds that you pay for? :)

Link to comment
Share on other sites

I'm using the BT wholesale test wired to both my Netgear and Netduma. Getting 3.2Mbps up 0.38Mbps down, ping was 40ms but now it's 60ms on average when connected to the netgear only. That was halved from Friday when connected to the Netduma.

Link to comment
Share on other sites

Bt wholesale test is not worth the bread its buttered on , we get 74mb at the shop when i use the bt test it shows 40mb which is totally wrong.

 

Are you using windows if so to ping do the following

 

start / run / type cmd /pop up box appears type     ping 8.8.8.8 -t

 

That will give you a true reading of your ping.

 

Use http://www.speedtest.net/for your speeds the pings can vary always use the dumas diag page or windows cmd to judge pings

 

Link to comment
Share on other sites

  • Netduma Staff

Just done that and the average was 62ms, some 74ms and the odd 104ms. But if I connect the netduma it goes way above that.

Could it be my settings that are causing this?

 

Are you doing the test wires or wireless?

 

Can you connect to the Netduma via wire and open a command prompt and type: 'tracert 8.8.8.8' then post the results back here please.

Link to comment
Share on other sites

Microsoft Windows [Version 6.0.6002]
Copyright © 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Alex>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1     7 ms    14 ms    30 ms  www.routerlogin.com [192.168.0.1]
  2    62 ms    61 ms    46 ms  217.47.106.122
  3    46 ms    46 ms    46 ms  217.47.106.193
  4    62 ms    61 ms    61 ms  213.1.69.158
  5    62 ms    77 ms    61 ms  31.55.165.102
  6    77 ms    61 ms    61 ms  31.55.165.43
  7    62 ms    61 ms    61 ms  31.55.165.107
  8    59 ms    59 ms    59 ms  acc1-10GigE-4-2-3.mr.21cn-ipp.bt.net [109.159.25
0.118]
  9    62 ms    77 ms    77 ms  core1-te0-13-0-14.ealing.ukcore.bt.net [109.159.
250.32]
 10    62 ms    61 ms    61 ms  peer5-te0-0-0-6.telehouse.ukcore.bt.net [109.159
.254.34]
 11    77 ms    77 ms    77 ms  109.159.253.67
 12    92 ms    92 ms    61 ms  216.239.47.175
 13    69 ms    69 ms    69 ms  216.239.46.253
 14    62 ms    61 ms    61 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\Users\Alex>

Link to comment
Share on other sites

Last one was without the netduma, this one is with the netduma :)

 

  1     5 ms    15 ms    15 ms  192.168.88.1
  2    16 ms    14 ms    14 ms  www.routerlogin.com [192.168.0.1]
  3    46 ms    46 ms    46 ms  217.47.106.122
  4    49 ms    49 ms    49 ms  217.47.106.193
  5    62 ms    61 ms    61 ms  213.1.69.158
  6    62 ms    61 ms    61 ms  31.55.165.102
  7    62 ms    62 ms    61 ms  31.55.165.43
  8    62 ms    61 ms    61 ms  31.55.165.107
  9    62 ms    61 ms    61 ms  acc1-10GigE-4-2-3.mr.21cn-ipp.bt.net [109
0.118]
 10    77 ms    77 ms    77 ms  core1-te0-13-0-14.ealing.ukcore.bt.net [1
250.32]
 11    62 ms    61 ms    77 ms  peer5-te0-0-0-6.telehouse.ukcore.bt.net [
.254.34]
 12    77 ms    77 ms    77 ms  109.159.253.67
 13    62 ms    61 ms    61 ms  216.239.47.175
 14    77 ms    77 ms    77 ms  216.239.46.253
 15    62 ms    61 ms    61 ms  google-public-dns-a.google.com [8.8.8.8]

Link to comment
Share on other sites

  • Netduma Staff

The speed deffinately halved when I connected the netduma. I've tested my other line in the house and it's got a ping of 40ms, so how can my line for gaming be over 60ms? :(

 

When you do the ping is it wired or wireless? Can you connect the Netduma and run an internet diagnostics test and post results please :)

Link to comment
Share on other sites

There's the test

 

Ping
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=48 time=59.948 ms
64 bytes from 8.8.8.8: seq=1 ttl=48 time=59.093 ms
64 bytes from 8.8.8.8: seq=2 ttl=48 time=59.409 ms
64 bytes from 8.8.8.8: seq=3 ttl=48 time=59.207 ms
64 bytes from 8.8.8.8: seq=4 ttl=48 time=59.871 ms
64 bytes from 8.8.8.8: seq=5 ttl=48 time=60.734 ms
64 bytes from 8.8.8.8: seq=6 ttl=48 time=59.455 ms
64 bytes from 8.8.8.8: seq=7 ttl=48 time=59.477 ms
64 bytes from 8.8.8.8: seq=8 ttl=48 time=60.061 ms
64 bytes from 8.8.8.8: seq=9 ttl=48 time=59.814 ms
64 bytes from 8.8.8.8: seq=10 ttl=48 time=59.596 ms
64 bytes from 8.8.8.8: seq=11 ttl=48 time=59.399 ms
64 bytes from 8.8.8.8: seq=12 ttl=48 time=59.264 ms
64 bytes from 8.8.8.8: seq=13 ttl=48 time=60.720 ms
64 bytes from 8.8.8.8: seq=14 ttl=48 time=60.092 ms
64 bytes from 8.8.8.8: seq=15 ttl=48 time=59.543 ms
64 bytes from 8.8.8.8: seq=16 ttl=48 time=58.855 ms
64 bytes from 8.8.8.8: seq=17 ttl=48 time=58.885 ms
64 bytes from 8.8.8.8: seq=18 ttl=48 time=59.924 ms
64 bytes from 8.8.8.8: seq=19 ttl=48 time=60.239 ms

--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 58.855/59.679/60.734 ms
Trace

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 192.168.0.1 0.544 ms 0.459 ms 0.747 ms
2 217.47.106.122 41.066 ms 41.769 ms 42.167 ms
3 217.47.106.193 40.926 ms 39.412 ms 39.707 ms
4 213.1.69.158 57.506 ms 56.753 ms 57.542 ms
5 31.55.165.102 49.817 ms 49.437 ms 49.902 ms
6 213.120.162.67 67.283 ms 71.841 ms 71.693 ms
7 31.55.165.107 51.070 ms 50.889 ms 49.485 ms
8 109.159.250.60 67.416 ms 109.159.250.98 68.677 ms 109.159.250.104 69.446 ms
9 109.159.255.155 73.215 ms 109.159.250.148 58.603 ms 109.159.255.155 74.180 ms
10 109.159.254.243 75.011 ms 109.159.254.249 78.447 ms 109.159.254.243 79.018 ms
11 109.159.253.67 57.944 ms 57.830 ms 57.400 ms
12 216.239.47.177 59.516 ms 216.239.47.179 89.019 ms 74.821 ms
13 209.85.255.137 61.431 ms 209.85.249.241 56.808 ms 72.14.237.41 59.702 ms
14 8.8.8.8 57.967 ms 57.183 ms 56.885 ms

Link to comment
Share on other sites

  • Netduma Staff

The netduma is wired to my computer, I'll run the test.

 

Ok. Maybe you could connect the Netduma to your other line and also run the test - is that possible? That was we can see if there is a different between the two. If there is a big difference you might need to contact your ISP as it could be a problem with the line.

Link to comment
Share on other sites

Here's the results from the other line

 

Ping
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=50 time=47.125 ms
64 bytes from 8.8.8.8: seq=1 ttl=50 time=47.591 ms
64 bytes from 8.8.8.8: seq=2 ttl=50 time=45.887 ms
64 bytes from 8.8.8.8: seq=3 ttl=50 time=45.852 ms
64 bytes from 8.8.8.8: seq=4 ttl=50 time=47.232 ms
64 bytes from 8.8.8.8: seq=5 ttl=50 time=46.439 ms
64 bytes from 8.8.8.8: seq=6 ttl=50 time=46.286 ms
64 bytes from 8.8.8.8: seq=7 ttl=50 time=47.381 ms
64 bytes from 8.8.8.8: seq=8 ttl=50 time=46.707 ms
64 bytes from 8.8.8.8: seq=9 ttl=50 time=47.038 ms
64 bytes from 8.8.8.8: seq=10 ttl=50 time=46.329 ms
64 bytes from 8.8.8.8: seq=11 ttl=50 time=46.702 ms
64 bytes from 8.8.8.8: seq=12 ttl=50 time=46.987 ms
64 bytes from 8.8.8.8: seq=13 ttl=50 time=45.633 ms
64 bytes from 8.8.8.8: seq=14 ttl=50 time=47.030 ms
64 bytes from 8.8.8.8: seq=15 ttl=50 time=45.778 ms
64 bytes from 8.8.8.8: seq=16 ttl=50 time=46.552 ms
64 bytes from 8.8.8.8: seq=17 ttl=50 time=47.645 ms
64 bytes from 8.8.8.8: seq=18 ttl=50 time=46.682 ms
64 bytes from 8.8.8.8: seq=19 ttl=50 time=46.789 ms

--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 45.633/46.683/47.645 ms
Trace

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 192.168.0.1 0.530 ms 0.496 ms 0.425 ms
2 217.32.97.250 26.722 ms 27.679 ms 26.065 ms
3 217.32.97.161 26.407 ms 24.535 ms 27.384 ms
4 213.1.69.154 34.799 ms 35.844 ms 35.089 ms
5 31.55.165.33 35.180 ms 35.172 ms 34.255 ms
6 31.55.165.107 34.756 ms 33.176 ms 33.781 ms
7 109.159.250.58 34.253 ms 109.159.250.116 34.361 ms 109.159.250.114 34.158 ms
8 109.159.250.34 44.749 ms 109.159.250.30 45.488 ms 109.159.250.139 41.481 ms
9 62.172.102.1 46.241 ms 109.159.252.57 48.772 ms 50.148 ms
10 109.159.253.67 43.103 ms 43.755 ms 42.139 ms
11 216.239.47.179 42.371 ms 216.239.47.177 46.078 ms 216.239.47.175 41.846 ms
12 209.85.243.123 43.319 ms 41.057 ms 216.239.47.59 45.365 ms
13 8.8.8.8 47.738 ms 42.583 ms 44.356 ms

Link to comment
Share on other sites

  • Netduma Staff

Ok. One final test. Without the Netduma can you run 'ping 8.8.8.8' from your other router and post the results back. From what you've shown so far though it looks like it could be a problem with your line :(

Link to comment
Share on other sites

Here's the ping from the other line without the netduma connected.

 

Microsoft Windows [Version 6.0.6002]
Copyright © 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Alex>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=52ms TTL=50
Reply from 8.8.8.8: bytes=32 time=62ms TTL=50
Reply from 8.8.8.8: bytes=32 time=46ms TTL=50
Reply from 8.8.8.8: bytes=32 time=46ms TTL=50

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 62ms, Average = 51ms

C:\Users\Alex>

Link to comment
Share on other sites

Tracrt

 

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1     7 ms    15 ms    15 ms  www.routerlogin.com [192.168.0.1]
  2    30 ms    30 ms    30 ms  217.32.97.250
  3    30 ms    30 ms    30 ms  217.32.97.161
  4    46 ms    46 ms    46 ms  213.1.69.154
  5    46 ms    46 ms    46 ms  31.55.165.33
  6    46 ms    46 ms    46 ms  31.55.165.107
  7    46 ms    46 ms    46 ms  acc1-10GigE-4-2-2.mr.21cn-ipp.bt.net [109.159.2
0.116]
  8    46 ms    46 ms    46 ms  core2-te0-0-0-16.ealing.ukcore.bt.net [109.159.
50.156]
  9    62 ms    46 ms    62 ms  peer5-te0-0-0-11.telehouse.ukcore.bt.net [109.1
9.254.243]
 10    46 ms    46 ms    46 ms  109.159.253.67
 11    46 ms    46 ms    46 ms  216.239.47.173
 12    62 ms    61 ms    61 ms  66.249.95.39
 13    46 ms    62 ms    61 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Link to comment
Share on other sites

  • Administrators

Hi alba,

 

Try address one issue at the time.  The line issue is some inherent problem with your line.

 

The hosts issue is probably something to do with your Geo-Filter settings, could you post a screenshot of your entire host filtering page and we can help :)

Link to comment
Share on other sites

Hi alba,

 

Try address one issue at the time.  The line issue is some inherent problem with your line.

 

The hosts issue is probably something to do with your Geo-Filter settings, could you post a screenshot of your entire host filtering page and we can help :)

Sorry about that Iain. Been having problems with BT three weeks after the line was put in and thought the duma would solve some problems.

Have send an email after getting the excellent feedback from this forum.

 

Here's the screenshot of my geofilter. It's those two Always alow hosts.

 

Netduma_6_zpsrk0xtqza.jpg

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...