Sproutcore

Made the changes and still getting 'Beavered' when going to the tower and starting PvP.

Hi, any progress on getting the GEO Filter changes so that EU gamers can use the NetDuma R1 router again for Destiny 2? As it stands, the router is not compatible with Destiny 2 outside the US (I haven't used the router now since September). I opted in for the NetDuma 3.0 update for the NetDuma R1 but no feedback from you guys yet. Looking forward to hearing back from you soon. Have a Merry and Healthy Christmas

Hi Frazer, I've submitted 44 servers so far (all using the same icon on the map and still finding new servers). It seems that there are new server being listed every day. Is anyone else in the EU posting Destiny 2 sever IDs located in USA or am I the only one? Thanks for your support PS: It's tough playing with the spectating mode enabled. I really am looking forward to getting my R1 Geo Location back to normal. PSS: it would make it much easier if I could export the server list using some kind of button (IDs formatted using commas). Even better would be to right click and submit to you directly.

just reaching out to the community to see if anyone is aware of any connection issues over the past few days (R1 with Destiny 2 on PS4 Pro)? I'm having a bit of a problem with the Geo-Filter (current settings have been working for over 12 months now without a glitch so far): I have deleted the device and assigned it back again after flushing the cloud (no change) Strickt mode is set to off and filtermode is on (with filter mode set to spectating the problem goes away) My normal distance settings are 1500km around S. Germany, which no longer work Beaver errors with Geo-Filter set under 7000km: I can spawn to a PvE location with no problems, e.g. Earth EDZ I cannot spawn in the tower or start PvP matches (always get beavered) Delayed beaver errors with Geo-Filter set to 8000km: I can spawn in the tower or start PvP matches after getting a warning message that I am getting network problems. A minute or 2 later I get beavered. If I set the distance to over 8500km everything returns back to normal. In all the attempts there is always a dedicated server in Texas that pops up just before getting beavered. If I include this server to be within the distance everything is ok. I have tried to add the server but it gets a new ID every time. Images with server just outside and just inside of set distance (not working and working) Any help would be really greatful. I find Destiny very clunky without my trusted router 🙂 Sprout

It's good to see that Destiny 2 is on your radar. Destiny 2 will have dedicated servers for all crucible games that will do all the physics calculations (bullet strike, etc). Local machines will host the graphical content for the matches. I see potential for more beaver like error codes if this is not taken into account when using the Geo-filter: https://www.reddit.com/r/DestinyTheGame/comments/6ddfxg/bungies_changes_to_their_networking_model_is/

Turned Geo Filter on and got Beavered on the 2nd match (first match was full of red bars too - really laggy). I would appreciate your support Chive. How do I send you my contact details?

With the settings you suggested I still got weaselled in the middle of a game (at least no Anteater first). Update. turned router off for Destiny. Totally, unplayable!!!

I'm able to access Destiny content using the workaround above but I'm now getting Anteater followed by Weasel every 8th or so game. So annoying! Happened twice last night on the 8th round of trails (only the 8th rounds too). There is still something unstable running in the background (or new Destiny server trying to run checks and getting blocked). Are there any other players getting the same problem in Trails? I'll try the new cloud servers and get back.

Can someone please add the Ireland padlock above to the list of blocked dedicated hosts. It pops up every other game now. PS I Love Ireland :-)

ID located in Ireland (padlock): 7536a36ed3144348

I had the same problems: http://forum.netduma.com/topic/21041-destiny-not-playable/

Anyone who says this router does not work should try using a Netduma for about 3 months then play 1 week without it. Vanilla Destiny matchmaking is a total nightmare (). I may've found a way of getting the router to work: Disable Geo-Filtering Start PS4 Start Destiny and wait in orbit Enable Geo-Filtering Select a crucible match and you're in :-) The new server(s) that Bungie added seems to be connecting just before the character selection part of the game.

Last night the game was working. Today not. Bashing my brains out here. Marrionberry every time now when enabling Host Filtering. Can't start Destiny at all! Netduma is fully exposed to the main router (DMZ) Reset Netduma router again (connected to main router using port 1) Replaced LAN cable Set wifi pasword (for laptop to access Netduma web-server) Set up devices (PS4) Setup static IP Set LAN DNS to OpenDNS public servers (connected to PS4 on port 2) Entered standard PS4 port forwarding to static IP Applied the cookies (nice tip) Disabled Auto Cloud Selected 30, 28, and 28 Results on Netduma LAN (preferred choice): Enable Host Filtering = Marrionberry Disable Host Filtering = Destiny starts with no problems Results on Netduma wifi (don't like to use) Enable Host Filtering = Destiny starts with no problems Disable Host Filtering = Destiny starts with no problems Results on main router LAN Destiny starts with no problems Results on main router wifi Destiny starts with no problems Everything was fine until Destiny updated their servers this week but why only LAN (does make me feel like there is something wrong with the LAN setup)

Hi guys, great advice so far. It seems to have worked :-) Since Iron Banner came out on Tuesday I've been getting 'Marionberry' constantly (router worked reasonably well up until then). I reset the router and applied your changes above. Can't help but love the NetDuma router and now the support is right up there. Thanks again. I'll keep you updated if I run into anything else (such as Trails ;-).

Had this router for quite a while now and I can say that when the router works the games are nice and clean. Unfortunately, the router is very unstable. If you play Destiny (with Destiny profile, Strict mode off, Home set to central Europe, 1200KM distance, and cloud settings enabled) then in my experience I get about 3-6 games without errors followed by 1-2 games where I get kicked from the game (or returned to lobby just before the game starts). If you play Trails then forget it. There is no way (or rare) that the router will hold out for 7 continuous matches. I know, I've been beavered enough with my team mates screaming at me to turn off the router. I've read loads of forums where Netduma state that these errors are due to incorrect settings but I don't think so. You just can't mess with the Bungie connection - Beavered!. Even then, if the router is set up to allow laggy games (what's the point of the router) how do you get past the padlocks inside the distance set? Answer = Beavered! Improvements needed: Once a game has started, commit to the game. Don't send me to orbit half way because the game has started to lag Is there no way to automatically report padlocked hosts outside the distance set? Why are you asking for users to send you the padlock IDs? Give me an option to report and ignore padlocked hosts. What is the point of Strict mode (at least with the Destiny profile set) if you are telling people to disable it all the time? When I start my browser and go to the router why does it not save my previous session? It's annoying to un-check the legend and zoom into my home location every time. For some reason the browser lags when opened for some time (and often crashes). Even had out of memory once. Mobile app? All in all I do like the router but it's not stable enough for competition type gaming (firmware update seriously needed). It is really good for normal crucible (even Iron Banner struggles) if you don't mind crashing out of the game regularly then it's great.