Netduma Fraser

Have a look at the URL when it gets blocked (it should show up), then add that to your whitelist and it should prevent it happening, if you also provide that URL to us we can get it added to the main whitelist

Added: https://forum.netduma.com/forum/151-netduma-r3-early-access/ Currently the publicly available firmware is the same as the latest firmware in Early Access

Thanks for the report, could you forward the email back to us so we can see exactly what is happening? That'd be really helpful!

NAT Type 1 = Open NAT connected direct to a modem NAT Type 2 = Open NAT connected to a router So it is impossible to get NAT Type 1 through the router, it's also unnecessary as you'll already be open

Thank you for the report, I have let the team know so they can get this updated

I have checked in again and the game was tested but we weren't able to filter the game unfortunately so it wasn't added. We'll re-test the game again to see if we can do anything to improve it, otherwise we'll put it in as a non recommended game so that it'll still work with Steady Ping on the R3.

Try and access the sites with QoS enabled then grab the logs and post them here please

Okay so what are their next steps to identify the issue?

Have you upgraded to the latest firmware? https://forum.netduma.com/topic/55635-new-r3-firmware-40219/ As it could be an early firmware bug

You would need to contact your provider about getting the config file, it's not something we can help with specifically

You can use either really!

Exactly as above, the hardware is limited to 1Gbps!

Brilliant thank you!

Just to ensure we can gain access when needed if you could: Ensure the R3 is in the DMZ on your ISP modem/router or the ISP modem/router is in modem/bridge mode Disable IPv6 in WAN/LAN on the R3 Enable remote support on the R3 Post back here when you've done that The team can then remote in at any time, no need for you to be present.

No need to but you can if you wish

It's not a bug necessarily, it will be blocking the servers used to detect your NAT status - it won't be causing your NAT to become strict. If you notice the blocked server on the map please do provide the ID and we can add it to the allow list. Otherwise now you know that happens you can re-enable the filter and ignore the NAT reading.

That's great thank you, I'll pass the topic onto the team so they can keep an eye on it - just post here again as soon as you notice it happening.

Ahh that's good to hear, yes that could potentially affect it if its not getting the right amount of power

Thanks for posting your solution!

We would need if off for WAN as well. It's unlikely we'll be able to match up but if you have everything ready then it'll make it easier should it happen again. Just to ensure we can gain access when needed if you could: Ensure the R3 is in the DMZ on your ISP modem/router or the ISP modem/router is in modem/bridge mode Disable IPv6 in WAN/LAN on the R3 Enable remote support on the R3 Post back here when you've done that The team can then remote in at any time, no need for you to be present.

We're based in the UK so we wouldn't be in then but if you could: Ensure the R3 is in the DMZ on your ISP modem/router or the ISP modem/router is in modem/bridge mode Disable IPv6 in WAN/LAN on the R3 Enable remote support on the R3 Post back here when you've done that The team can then remote in at any time, no need for you to be present.

You download the file from the first post in this topic, then on the router interface go to Troubleshooting > Upload Firmware and select the file you downloaded to upgrade. It's likely a bug on that version so upgrading will fix it

Great to hear that, thanks for the update!

Great thank you!

Disable IPv6 in LAN/WAN then ensure remote support is enabled. As long as it is enabled they can connect at any time, they don't need you to be there. They may need frontend access, in which case they will communicate with you and want to conduct a session over AnyDesk, so if you download that ahead of tomorrow that would be much appreciated just in case it is needed. For the Geo-Filter: Disable GeoLatency Disable PingAssist (set it to 0,0) Enable Strict Mode Disable Fast Search Use Simple instead of Custom radius Then restart game or wait 10 minutes (in the lobby in the game). If that doesn't work, reboot PC/Console and it should work then.