NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
NIGHTHAWK R7000 gaming lag
hey guys
just needing some help.
im in australia with nbn, speeds of 23Mbps, upload of 3-4 mbps
i quite often play fifa on xbox one on a wired connection. we often have guests and family over and if anybody is using the bandwidth to watch movies or youtube, it makes my gaming basically unplayable which gets me frustrated quite often.
Now iv tried QoS upload and download, or one and the other and all i get from that is general problems or slow speeds.
now i feel like some settings could be the problem.
This is my first netgear product and iv always been pretty good at sorting these sort of problems, but previously when we had adsl, iv just put it down to our speeds, but with nbn i didnt expect to have these problems.
HELP
thanks guys
Hi Striker8881,
1. What is the firmware version of the router? make sure it is on the latest.
2. Try to perform a factory reset on the device and manually reconfigure.
16 Replies
It might be useful if you measure latency.
For instance if you run a repeated ping test on a PC (ping xxx.xxx.xxx.xxx -n xxx), and then repeat that test while watching a youtube on a different device - looking for changes in the latency (both average and variations).
i downloaded a repeated ping test on my iphone and the results were a steady 9ms
then i repeated the test while i was playing and lag was happening and times varied from 9-30ms. But most of the pings just said "time" which i figured was the lag happening.
Can you ping your modem? If so, that would let you see the router's contribution to the lag. Maybe start with a tracert so you know if the ping path goes beyond the modem itself (it might go to an ISP router and then back to the modem).
This might require a setting change on the modem, it possibly is configured to not respond to ping.
- But as far as I know and iv tried previously, when the TG-1 is in bridge mode I can't access the GUI? And I use the ping tool on 10.1.1.1 and it doesn't read anything?
And I use a mac as our home computer 😂😬
Striker8881 wrote:
But as far as I know and iv tried previously, when the TG-1 is in bridge mode I can't access the GUI?That could be - I didn't see anything about bridge mode in the manual.
The puzzle here is figuring out if the router is the cause of the latency problem or if the issue is upstream (for instance the ISP link.) You could try putting the TG-1 in router mode (keeping everything connected as it is), and then measure the latency I guess.
sorry i didnt reply till now
Yer bridge mode was added late last year.
i tried reseting the modem to get test it but i was having troubles getting a connection so i just put it back in bridge mode.
i tried speaking to IInet twice and i got hung up on once and then spoke to someone that had no idea about anything and told me to "disconnect my xbox if its causing connection issues"
So frustrating
i tried doing a trace route? ( for the first time) to easo.ea.com (which is the ea servers for fifa which i play?)
now im not 100% sure what that means or what its supposed to be so hopefully someone here can tell me.
traceroute to easo.ea.com (159.153.234.54) , 5 relative hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 7.618 ms 116.618 ms 119.761 ms
2 150.101.32.66 (150.101.32.66) 37.428 ms 168.453 ms 173.249 ms
3 150.101.33.66 (150.101.33.66) 87.555 ms 185.954 ms 191.532 ms
4 150.101.34.171 (150.101.34.171) 182.879 ms 432.820 ms 440.143 ms
5 150.101.33.176 (150.101.33.176) 799.099 ms 867.740 ms 869.311 ms
6 150.101.40.217 (150.101.40.217) 108.281 ms 190.949 ms 198.699 ms
7 prolexic1-lacp-10g.hkix.net (123.255.91.26) 108.105 ms 390.032 ms 391.530 ms
8 72.52.2.176 (72.52.2.176) 159.211 ms 571.512 ms 577.144 ms
9 72.52.2.183 (72.52.2.183) 104.398 ms 229.580 ms 237.268 ms
10 * * *
11 209.200.184.165 (209.200.184.165) 272.601 ms 1293.185 ms 1315.033 ms !X * * !X *
This is the traceroute to the ea servers again. that first hop changes everytime i do it. its often 0.7ms.
1 192.168.1.1 (192.168.1.1) 1.853 ms 0.567 ms 0.535 ms
2 lo0.bng2.per4.on.ii.net (150.101.32.66) 9.000 ms 8.864 ms 9.187 ms
3 cr1.per4.on.ii.net (150.101.33.66) 8.219 ms
cr1.per1.on.ii.net (150.101.33.42) 9.136 ms
cr1.per4.on.ii.net (150.101.33.66) 8.345 ms
4 ae17.cr1.adl6.on.ii.net (150.101.33.20) 167.699 ms 167.939 ms
ae17.cr1.adl2.on.ii.net (150.101.33.18) 166.493 ms
5 ae4.br1.syd7.on.ii.net (150.101.33.34) 191.900 ms 190.167 ms
ae16.br1.syd4.on.ii.net (150.101.33.188) 55.876 ms
6 ae0.br1.syd4.on.ii.net (150.101.33.14) 55.593 ms 56.285 ms 62.724 ms
7 prolexic1-lacp-10g.hkix.net (123.255.91.26) 169.872 ms
te0-0-0-0.br1.hkg2.on.ii.net (150.101.33.199) 168.731 ms
prolexic1-lacp-10g.hkix.net (123.255.91.26) 170.057 ms
8 unknown.prolexic.com (72.52.2.184) 184.141 ms 183.813 ms 183.902 ms
9 unknown.prolexic.com (72.52.2.183) 170.158 ms
unknown.prolexic.com (72.52.2.176) 184.155 ms
unknown.prolexic.com (72.52.2.183) 169.830 ms
10 unknown.prolexic.com (72.52.2.183) 170.512 ms * *
11 * * *
12 209.200.184.165 (209.200.184.165) 459.358 ms 404.791 ms 409.555 ms !X
13 * 209.200.184.165 (209.200.184.165) 524.000 ms !X 409.440 ms !X
