MaltedMilkhouse

That did the trick, thanks very much for the prompt reply and solution!

I'm just having an issue tonight which seems odd, I went and loaded my profile for Destiny 2, went to the host filtering page and where my PC is always listed in the 1st of 4 services, there's nothing. If I click "select service" it brings up a box with "select device" but there is no devices to choose from. I am then unable to press "next" or even close the pop up dialog, I have to refresh the page, and there is no service listed. This isn't restricted to a certain profile, even on general gaming or non gaming my PC is unlisted in host filtering, I've reset the router several times, rebooted the PC, turned off the router for 5 mins, nothing seems to work. Like Internet is fine but I obviously can't use the geo filter as there is no service to select. Any advice?

No worries, I've got to say things have improved significantly from when I first used this in late D1 and early D2 on console, where I was constantly getting kicked from games etc. I had to stop using it. So far on PC I've only been error coded/kicked 3 times in over 100 hours, and been able to make full use of the geo filter, which on PC is essential due to the smaller playerbase.

I was using bleeding edge and auto cloud as I am unable to enter a number for the third option, and haven't been advised why that is or what is optimal.

Also ID:d467451004735a5f has already booted me twice, located in the middle of the south atlantic ocean 😑

Is this still what should be used? I've switched to PC so just seeing if the duma will be of any benefit. For some reason I can't select 28 or any numbers in the thrid box. Like it let's me scroll for numbers but as soon as I select a number it defaults the entry to 1.

Only just got the game, what profile is recommended? I used COD Ultimate in the beta and had really good connections.

Thanks for the updates guys, I've been playing with geo disabled because it was getting quite bad, will try with the auto cloud and edge cloud ticked when I get the chance.

Japan I think ID: 93368c57d332575c

I didn't treat as such, but thanks for mentioning that

Another one 5 minutes later in the tower, once again in Ireland ID: 4c36f8c3d3eb4348

Oh I read it, yes the game has been out almost 6 weeks and the staff(not sure if there are paid employees or just volunteers, if it's the latter then it's understandable)haven't been able to include many of the servers resulting in people being kicked many times, and that's Bungie's fault as you say for making a game poorly, and nothing to do with the adequacy or efficiency of Netduma, correct? The configuration of my main router is fine, I just set it up to test the Netduma yet again with my Archer D7 in bridge, it's essentially doing nothing so there's no use sending screenshots. I've also previously set it up via bridge or alternatively via the dmz method outlined in your guide on the D7, on an Asus dsl-ac68u and on an old Billion 7800nxl. All of them have been set up correctly with the right configuration needed to work with the Duma, all of them have also been setup correctly when not using the Duma and have zero issues with Destiny 2. Logged in then and got kicked error code beaver by a padlock in Ireland of all places, ID: cf364712d36e4348 348

I mean I've never been kicked with any animal error when I'm not using a Netduma, I know others have but I have zero issues when not using it. With the duma it's padlocks which are NA based orginally cabbage then beaver, I got around that by having the geo off and got no errors but then what's the point? I can use QoS on any of my existing routers to get A+ buffer bloat, and they have the functionality to use 5ghz wifi for other devices in the household(console is on lan), with more detailed info, and more settings that can be tweaked. People can blame Bungie all they like though.

Oh I gave it a go, I generally don't spend $300 on a product to not use it, I've been giving it a go since the last month or two of D1, it just doesn't work for me as advertised in regards to D1 or D2. The only thing it worked flawlessly for was the WW2 beta. However I tried it again last night with the "new settings" and the beaver errors were back, in fact one of the padlocks was the same id I'd reported on here several weeks ago in Connecticut. I've seen some admin recommend auto cloud and bleeding edge off, others recommend it on, Chive's guide says no to upnp, other admins say yes to upnp, so it's hard to pin down what is the actual recommended settings. It would be nice to get some clarification on that. The other night I had auto cloud and bleeding edge off with upnp on and whitelist 40, gameserver 37 and map 28. I am unsure in regards to profile, are people using "Destiny" or just "General Gaming"?

I'm in Australia and ended up disconnecting the duma about 3 weeks ago due to constant beaver errors from various padlocked NA hosts, just wasn't worth the trouble, even in PvE with 2 local players. Dissapointing to see it's still the case, dominate lag? yeah nah.