Jump to content

Not working???


gkontos10

Recommended Posts

It's your location and connection that are the issue. The Netduma can't find games that are not there.

 

If you connection at peak times pings Google at 100ms then that is as good as a game ping as you could expect to have. Ping a server in Netherlands or UK on pingtest.net as those are COD server locations and would be indicative of your likely in game ping.

Link to comment
Share on other sites

Ok i can understand that on rush hours between 20:00-22:00

 

But what its going on the rest of the day that I have ping 35-45?? Even then I can't games below 80ms.

 

Were do you suggest to put my home dot

And what distance and ping to search for?

Link to comment
Share on other sites

Your ping of 35-50ms at non peak hours is to a local server likely in Cyprus. That's not where the COD server will be.

 

Ping in its simplest form is a factor of distance. Further away server is, the larger the ping. The COD servers will be in Europe so you need to ping a pingtest server in UK / Netherlands etc at non peak times to see what you can expect with COD.

 

After you have that info post it up and we can advise re a ping assist value. Ping assist needs to set at a realistic value to be of use. Not a notional value of what you would prefer.

 

Hope that helps.

Link to comment
Share on other sites

Guest Netduma_Iain

Hi Konto,

 

So there are a few concepts here. Lets call the first one base ping. That is what the Internet diagnosis test shows on the router. It pretty accurately shows you the best ping you can ever achieve. So in reality it will always be a little higher. So your base ping seems to be 50ms in the day & 110ms in the evening.

 

So that means the best you can achieve is 50ms in the day, but in reality it will probably be higher as there won't be any players near you. In the evening again it will be at least 100ms but probably higher for the same reasoning.

 

BUT its not the end of the world, because multiple things make your ping. If ping was an equation it would look something like this:

 

ping = base ping + distance to travel + local queuing + remote queuing

 

The R1 can help with the last 3 terms in the equation. So you won't be able to get low pings like people who live in NY or UK. But you will be able to get lower pings that you are used to. So based on your connection I imagine without our tools you could easily end up with 300ms+ games. 

 

So lets keep everything simple for now, this is what I suggest:

  • Set the ping assist to 110ms
  • Set the distance to 111km THEN press the snap button twice to auto-expand your distance to the optimum 
  • Tick strict mode
  • Go to congestion control & set it to 70% for download & upload

Then try that, also please if possible use a wire to connect your console to the router.

 

Hope that helps

Link to comment
Share on other sites

so thats my internet diagnosis through R1

average 45ms

what set up to use ???

 

 

 

Ping Diagnostics

 

Ping Jitter Spikes Packet Loss Ok Good Good No Loss
Ping
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=57 time=44.170 ms
64 bytes from 8.8.8.8: seq=1 ttl=57 time=44.270 ms
64 bytes from 8.8.8.8: seq=2 ttl=57 time=45.765 ms
64 bytes from 8.8.8.8: seq=3 ttl=57 time=43.849 ms
64 bytes from 8.8.8.8: seq=4 ttl=57 time=44.335 ms
64 bytes from 8.8.8.8: seq=5 ttl=57 time=45.459 ms
64 bytes from 8.8.8.8: seq=6 ttl=57 time=44.343 ms
64 bytes from 8.8.8.8: seq=7 ttl=57 time=45.630 ms
64 bytes from 8.8.8.8: seq=8 ttl=57 time=43.828 ms
64 bytes from 8.8.8.8: seq=9 ttl=57 time=44.757 ms
64 bytes from 8.8.8.8: seq=10 ttl=57 time=45.464 ms
64 bytes from 8.8.8.8: seq=11 ttl=57 time=44.254 ms
64 bytes from 8.8.8.8: seq=12 ttl=57 time=45.791 ms
64 bytes from 8.8.8.8: seq=13 ttl=57 time=43.968 ms
64 bytes from 8.8.8.8: seq=14 ttl=57 time=45.420 ms
64 bytes from 8.8.8.8: seq=15 ttl=57 time=45.193 ms
64 bytes from 8.8.8.8: seq=16 ttl=57 time=45.029 ms
64 bytes from 8.8.8.8: seq=17 ttl=57 time=44.804 ms
64 bytes from 8.8.8.8: seq=18 ttl=57 time=56.721 ms
64 bytes from 8.8.8.8: seq=19 ttl=57 time=45.185 ms

--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 43.828/45.411/56.721 ms
Trace
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 * * *
2 213.140.211.17 9.207 ms 10.164 ms 8.516 ms
3 213.140.198.14 9.349 ms 19.984 ms 8.419 ms
4 213.140.198.9 10.106 ms 21.517 ms 10.407 ms
5 213.140.214.14 44.956 ms 45.032 ms 45.063 ms
6 91.184.192.134 45.191 ms 43.617 ms 45.897 ms
7 209.85.245.0 44.977 ms 209.85.244.252 44.546 ms 47.873 ms
8 8.8.8.8 43.577 ms 45.502 ms 44.112 ms
 

 

Link to comment
Share on other sites

Guest Netduma_Iain

Hi Kontos,

 

I recommend you work your way through the wiki.netduma.com and understand the concepts, this will allow you to get the most out of the router. But if you want a simple quick setup guide I recommend the following:

  • You want to minimise distance, but you can't set it to 111km because you probably won't get a game. So please set the distance to 111km then press the snap button twice to get the optimum search range for you
  • Strict mode ticked
  • Ping assist set to 80ms
  • Anti-flood set to 70% each way
Link to comment
Share on other sites

Archived

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

×
×
  • Create New...