TG3NOC1D3

I see Fraser sent your the new firmware above, hope that helps you!

I'm not in front of my router at the moment as I am at work but either myself or @Netduma Frasercan show you where on this thread. When I got my router I was prompted to update to .21 but those are rolling releases at the moment so not everyone will get them at the same time. For being on PS5, draw your polygon over whatever server areas you want to play on and make sure you save them. Big thing is, do not have your game open on ps5 when making adjustments as the game will take whatever input the router is sending already. Go to your home screen, close the game completely, make your changes, disable geo-latency and ping assist. Leave strict mode on, then start your game. Another thing, when you upgraded your router, if you already had your router setup, try doing a factory reset, then power cycle it all the way off and back on so everything clears if the above instructions do not help.

I asked for the .23 firmware but in my opinion the .21 geo-filter works better. I encountered numerous longer waiting times due to the geo-filter trying to connect to a Oklahoma server that does not exist on the ping heatmap. There was even a no connect triangle so I'm not sure why it was trying to connect in the first place. Second, there seems to be a large of amount of load buffering on .23 currently, I noticed the stabilizer was struggling more to get the server stabilized and seemed to lock up after a bit.

1. It would be nice but definitely would need a secure way to do it lol. 3.Nice, I will have to try it, It didn't look like it showed up the other night but I will see what happens when I created a psn party tonight. 4. Yeah, ISP's are weird about that so it may not be doable but I know Asus has that optimal route deal on their router, I would have to get the exact name and see if it truly works but it would be interesting to see on this router with the geo-filter in a tag team tandem. 5. Just thought I would throw it out there, it would probably be easier (and safer) to just allow certain apps to be added to the router depending on the load of course.

My UDM Pro allowed dockers for running my own apps lol. So number 5 is not a dream land ask, it may just be too much for the current hardware. 4 is not a small task but it could be done, just depends on the ISP and if breaking their "preferred" routing would be an issue with them lol.

1. Remote Access! It would be awesome to check in on my network while away, especially when my lady is not super tech savvy and relies on me to keep the internet humming along lol. 2. Integrate the ping heatmap into the geo-filter, then allow us to auto whitelist and blacklist servers that are outside our comfort of playable latency, this would be so much more intuitive than drawing polygons as not every game has the same locale for good servers. What might be low latency for one game in an area, could be game breaking in another. 3. Also allowing us to see peer servers when creating a local game that may not use a dedicated server for a private match (This could already be a thing, haven't tested it yet lol). This would be a great way to implement a peer-to-peer reverse ping so we can see their latency to us and see if it is a local issue or a them issue. 4. This one is a little ambitious but stay with me. What if we had a feature that allowed us to create a custom static route to bypass crappy public internet routing? "Oh, hop 4 on my path is terrible, let me adjust this and make hop 5 of 7 hop 4." This may not be doable as I believe ISP's will control this but man, if we could the like a SD-WAN style route from our homes to our DNS provider to the game server, that would be insane! 5. Dockers to run our own apps, like pihole for instance. Not sure this would be doable even on the R3 but it would be pretty cool. That's it for the ideas, just a few things that I have been meaning to put to paper. I had a few others but they fell off, if I remember them later I'll post them up. Happy New Year!!

Can I get this one, I wanna do a comparison and see how my unit does. I also started thinking about something, but I will PM you my thoughts on that.

I mean this as nice as possible but this is because too many people want to use a specialty router but can't be asked to learn simple networking. If you're going to run your own network and use a device like this, you need to get comfortable troubleshooting and understanding some basics.

Just a heads up, unless you are running the cable through the home where power may cross your cabling, shielding is super unnecessary.

When I did the internal speed test I got 938/936 on my gig line, I'm using the 4.0.20 as well. Try plugging directly into your modem or isp provided device and test from there to verify this isn't an ISP issue to rule that out.

Looks like you have your pc listed twice, try closing out cod and closing the launcher as well. Then, delete both entries, go to device manager, change pc to playstation and then go add your pc back into geo-filter. If you want, give the router a reboot as well. Now you can fire up your launcher and open mw3. Let me know if this helps out.

Awesome! I'll be doing some more testing throughout the day while I telework. I did notice that while streaming apple tv through my TV (Ted Lasso!) The video and streaming priority did not see apple tv or hbo max as a streaming service, just an "other". Also, even my playstation device was a little wonky where it would see it as a priority one minute and then not see it active the next. I'm thinking in game modes where you go idle like search and destroy, or even watching a kill cam, the feed is causing some sort of disconnect. I'll test again as I was tired and may have botched my settings last night.

Power off the netduma and your modem/router. Wait 15-20 seconds and then power on the isp modem/router. Once it is fully online and has internet light showing, power up the r3.

So I got off of work tonight and deployed my R3 into my network amd lemme just say.... HOLY COW MAN!! Ping stabilizer is a BEAST for getting amazing hit detection on MW3. No longer do I find myself having to play hard-core just to get better kills, now I just grab a server and go! I will say this, I was extremely skeptical of all the tech bolstering about what this thing could do but man.... I was wrong! This thing plus a fiber optic connection to the Utah data center!! The only issues I really see are when you go idle in search and destroy, the filter seems to pick up that temporary boost in ping since your on dead cam and stabilizer sticks on it but I definitely wasn't playing like I was at 150ms. I did find that to keep servers outside of my radius from slipping through I turned off geo-latency as I remember this was geared more for halo and fortnite I believe? Second, you will have much better luck if you prioritize by device instead of a application like gaming, Video or work from home. They do not work very well and neither does seeing your port forward active either. Very minor issues for such a giant leap forward in software. Congrats Duma team, you created a monster. Cheers 🥃

Dude straight up said "These are the droids I'm looking for!" and bounced lol

I'm honestly a little surprised that this device isn't load balancing between the CPU cores when you can do this with any router running opensense or openwrt at this poiint.

They are asking for specifics, like what did you change, what is turned on/off, geo-filter etc. They can't help you troubleshoot if you don't give them details bro, I just got my R3 in while I was on lunch. Will be installing it tonight and see what everyone is talking about and try to do a walkthrough video if I have better success. In the mean time, be specific, they are here to help you

What firmware are you using on the r2?

I didn't get snobby until after you became condescending. I originally tried to make s point that YOU were being snobby about boot up time when it is literally not that long. Your expectation of "I want an instant boot up!" Isn't realistic and makes you look like a giant butthole and a whiny brat. I also never told you to use those dns servers permanently, just for testing with pingplotter, which I can gladly go back and quote. I was never belittling you in my original responses, simply stating that you need to work thr process and explaining how some games super low ping /= great. Here is some free advice though without belittling. Telling the developers in a condescending way that the completely normal boot up time isn't acceptable and insinuating they released a inferior product, I wouldn't want to help you right away either. Especially over Christmas for that matter, so humble yourself. Merry Christmas eve, I'm done having this back and forth. Ps: you should look into localizing a controller for your Automation if they need the internet so badly to keep from flipping out.

I told this dude all of this and he told me tock kick rocks, guess when someone else backs it up, he listens lol.

1. I can comment or post on whatever I like, especially when you were asked the same Troubleshooting question by the developer. 2. Majority of people are happy with the product they have received. The issues you are having which, to quote you, only one person, titofuenla, has been able to duplicate. If you studied in this field, which you said you did, 2 people doesn't equate a massive scale problem. It's a isolated problem in which they are still reading your issues and working toward a resolution. Just because they didn't answer you immediately, doesn't mean it isn't being sorted. 3. Majority of issues I have seen are from people not understanding how the technology works and immediately jumping on the band wagon of "you lied to us, this makes my connection worse and latency higher!" That right there, is unnecessary clutter and side-tracking from the real issues like the issue you and 1 other person have found which imo, could still be a user error. 4. Believe it or not, unless you are pulling massive downloads or uploads, people watching Netflix aren't going to tank your latency. If you are using the smart qos you should still get FIFO. Which would keep your packets from queuing, which it shouldn't without major bandwidth usage and filling the pipe from your isp. Hope this helps 🎄

Diploma? What was your field of study in college?

This is where lag comp plays in, you actually do NOT want the lowest ping. 30-80 in COD is the sweet spot where the server can make those adjustments and still get back to you with minimal jitter. It's why you optimize your connection for bloat, then play with different servers and see how they play.

Also, you will not always get the same server for waveform tests.... if you really want to see how your internet is behaving, download pingplotter, run a ping to like 8.8.8.8 or 1.1.1.1, then, start a speed test with your preferred site. That will tell you what your actual increas under load is. Hope this helps. DISCLAIMER: I do not work for Netduma and am in no way affiliated with their company. Just a dude who works in networking and knows a thing or two about it.

1 minute and 21 seconds without the internet?? OMG WHAT WILL YOU DO! But seriously..... my friend.... that is not a bad boot time. My UDM Pro has a 3-4 minute boot time.... the more features you pack in, the longer a boot sequence takes. Also, why in the world are you timing it and if you are rebooting constantly, that sounds like a you issue. After watching their video on how they are doing steady ping, you really should leave it on. Did you know that you don't truly experience lag until you start climbing over 85ms or so? Sure, you want lower ping, but I played COD on a 65ms ping time and still crushed it when I had a cable connection. The fact that some of you think you need sub 20ms to have a good game is laughable in a seriously disturbing way. I guarantee your latency not increasing on the R2 is because you probably had your device in smart boost mode, which will put it in a fifo state, at least that is how it acted when I ran a wireshark on my network. STEADY PING DOES NOT CONROL YOUR BUFFERBLOAT, it is only used in geo-filter. Also, did you have the bypass congestion control during speed tests enable on your R3 when you ran the test? Try turning that off and using low latency only and then try again, you might be surprised with the results.