Netduma Fraser

The R3 WAN IP yes - the one shown on the R3 WAN Settings page / the one shown for the device on the Tim hub devices page

You didn't need to disable DHCP on the Tim but now that you have done so set the R3 IP as static/reserved on the Tim and other than that it's correct!

Reboot your modem, wait 2 minutes, reboot the R3, wait 4 minutes then check, you should have internet then

If your setup is Tim Hub > R3 the R3 does not need PPPoE/VLAN because the Tim Hub is handling it. In this case you would put the R3 in the Tim Hub DMZ. If your setup is ONT/Wall > R3 then the R3 needs PPPoE. In this case the Tim hub is irrelevant as you aren't using it.

You don't need to disable anything specifically but I would suggest you put the R3 in its DMZ/exposed host function

It has no benefits for gaming, it's simply a way to connect which you do not need, if you needed it you would have a connection with it set. Focus on Congestion Control to eliminate bufferbloat.

If you're entering VLAN and you don't get internet then you don't need VLAN for a connection. I'm not sure what you mean about a public IP being bad for gaming but that's not correct.

Okay so you don't need VLAN then. You'll need to adjust Congestion Control (Ping Optimizer > Advanced) to find the best percentages to reduce your bufferbloat

Add that UK server to your allow list, you may need to do it a couple of times and it should be more consistent then until a cloud update can be done - there was an issue preventing them pushing the cloud which they're trying to resolve currently so it is a bit delayed

Put the details in, reboot your modem, wait 2 minutes then reboot the R3 from the interface, wait 4 minutes then access and see if you have a connection?

It's possible but not with those specific instructions, you'd have to create a hotspot off the PC or use a hub so the traffic flows through the PC so Wireshark could pick it up but I get that isn't very practical. The easiest workaround is to just prioritize devices instead of the gaming option. You'll get the same benefits without it incorrectly prioritizing the BTC Miner

Don't cover Germany and enable crossplay and you're likely to connect to Italy more often - it is one of those servers though that don't always appear to be active

The one in Dublin isn't a game server, it's required for authentication so you'll almost always see a connection to this server. You'll therefore see another server on the map which will be your game server. Disable Geo-Latency in Geo-Filter settings though and restart the game device and see if you get games more visibly within your radius.

As above disable that option, restart the game/gaming device then try again and servers should stay within your radius

We'd have to test it specifically to make a cloud update for it but I couldn't say when/if that may happen, if you're willing to help out by following the instructions here: https://forum.netduma.com/topic/51505-adding-new-games-and-applications-to-dumaos/ that would increase the chances of us being able to rectify it

If you disable the Geo-Filter before you launch the game do you get the same issue?

Not confirmed for the R2, we're looking into it but we've not totally finished development for it as is so it may be too much for the R2 hardware

We've had a couple of cases of people mentioning that previously so I expect there was a small batch of cables that were faulty. Do keep us updated!

Glad to hear that sorted it, thanks for the update! I'll also pass that onto the team to investigate as it seems to be the opposite of what should happen.

It's not necessarily in Paris but it's definitely located in France. I don't know if that one has gone out just yet but it has been incorporated into an update going out.

I don't know if that's what EE requires specifically but if you have internet with it set like that then it will be correct. For that issue you're seeing disable Geo-Latency in the Geo-Filter settings menu, also ensure you have Ping Assist set to 0-0. Then restart the game and try again.

We are aware of that issue and it'll be fixed in the next version. Early Access won't fix it but I've given you access anyway. For now you might find it better to have the ISP modem/router handle PPPoE if possible and put the router in the modem DMZ instead.

Could you clarify what you mean exactly?

The settings aren't something we change as its purely NTGR software, I'm not aware of them removing it, I don't know why they would. It'd be on the first settings page > Internet Setup, it might show as DHCP Identifiers instead. If not there it could be in WAN Settings or Advanced Internet Settings

The ACC feature from that article will be coming to the next version of the R3 firmware