Netduma Fraser

It's a less secure firewall but it's still enabled in that state, I use the option myself.

As above, does the host have a dashed circle around it to indicate it was caught by ping assist? We're aware of the ping not always appearing and are looking into it.

Effectuez une réinitialisation d'usine via l'interface et voyez si c'est toujours un problème après cela. - Do a factory reset via the interface and see if it is still an issue after that.

Could you follow these steps please? Delete the device from the Geo-Filter Look at the IP on the console network settings and match this with the device in Device Manager - make sure you know what the correct device is Hard turn off the console Flush the Geo-Filter cloud Re-add the device to the Geo-Filter Wait 2 minutes Turn on the console and the game See if it works better then please.

We will be doing more testing for Traffic Prio games/applications and have added a lot more so I can't see this being a problem.

The above should help but also double check that the Geo-Filter is not causing a misreading. Switch to Spectating mode then boot the game, if it appears as open then it's always open and you can enable and ignore the moderate reading.

¿Quieres la posibilidad de editar reglas adicionales? Esa es una buena sugerencia, la sugeriré al equipo. - You want the ability to edit added rules? That is a good suggestion, I will suggest it to the team.

As it's a Google form it won't be checking the validity of the serial number so that's probably why, all good though!

Hey, welcome to the forum! If you invite them one by one to the party then they will appear on the map for you to then add to your allow list. If there are too many people to do this then simply switch to Spectating Mode until everyone has connected and then switch back to Filtering Mode.

I'd highly suggest signing up for the XR beta so you can join earlier - hopefully your issues will be resolved and if not you can provide feedback http://www.netgearinnovation.com/dumaos-beta/index.html

Not open the ports but in Traffic Prioritization make an advanced rule instead of using the console service to input the ports that you would like to prioritize.

Okay leave it with us, this is something we'll have to test. Thank you for the information.

Hey, welcome to the forum! This is an issue we have identified and so we are working on fixing this so it should be good for 3.0. I would suggest you sign up to the XR beta so you can get into it sooner and then let us know if it is still an issue: http://www.netgearinnovation.com/dumaos-beta/index.html

With ping assist it will ping it initially and then if it is under the limit it will allow it, even if the ping then creeps above your limit. So set it to 30 instead and that may help it stay lower. Also make sure fast search is disabled as that can get you higher pings over your limit.

Es probable que sea más o menos lo mismo para Destiny también. Sí, mantenga los puertos de origen en el valor predeterminado 1-65535 y solo cambie los puertos de destino a los que desee. - It is likely to be roughly the same for Destiny also. Yes keep the source ports at the default 1-65535 and only change the destination ports to the ones you want.

Bert has given you great advice there, couldn't put it better myself. Let us know how you get on with his suggestions.

R1 sign up hasn't started yet so I'm not sure how you filled out the serial number etc for the NG routers. You would have to use a different email for the Nighthawk router signup.

That's odd, did you adjust your radius when you were on the game at all or do you set it all before booting up the console?

Yes that's right. Until Alex can resolve some of the issues identified with a cloud update I use Spectating Mode (location is placed in London with 1000km radius) and select the London server on the Apex menu. I rarely have an issue with this apart from one slow mo server yesterday.

What game are you playing? I think the best bet here would be to prioritize the ports manually. I would also recommend double checking that the IP/device you think it is hasn't changed - especially since making those PC changes.

Hey, welcome to the forum! In System Information in the Rapp panel options change the number of retries to 5 and then reboot the router. What firmware version are you on also? I think you'll be much happier with 3.0 as it brings more features that I think you will like and will eliminate these issues and make the router more stable in general. Sign up here so you can get onto it sooner http://www.netgearinnovation.com/dumaos-beta/index.html

Si tiene los puertos incorrectos que pueden obstaculizarlo, los puertos de origen no siempre son los mismos. Para Traffic Prio, use 1-65535 como fuente y luego agregue los puertos que desee. ¿Cuál es el ping promedio que obtiene como lo muestra el Geo-Filter? - If you have got the ports incorrect that can hinder you, the source ports are not always the same. For Traffic Prio use 1-65535 for source then make your additions for the ports you want. What is the average ping you're getting as shown by the Geo-Filter?

I mean't the UPnP table on the router. The moderate in game may be the Geo-Filter causing a misreading if you have an open NAT in the console settings so disable, boot up the game and see if it switches to open. If it does then you can enable it again and forget about it.

If you get better routing to the VPN server and then to the game server rather than direct to the game server then it could improve your stability and perhaps ping.

Static route isn't what you want, you've also changed a lot of settings such as MTU which can hinder you if you haven't done it properly. What IP address did you put in the DMZ on your fritzbox? If this changed then that's what needs to be fixed first otherwise your port forwarding won't work.