fatal0Efx

Has this occurred yet? I assume no because DNS resolution is still broken.

Sure. I just hope I'm around and doing something when it breaks. When do you intend to reboot, however? Luckily I wasn't affected last time but my partner and I both work from home so I cannot have this affecting that and I usually am gaming until around midnight EST. Before you perform the actions, however, can you issue nslookup commands from the router itself to an external provider to verify that is actually working when this is occurring.

Spoke too soon. Out of nowhere (while just just browsing the internet), websites stopped loading and DNS resolution through R2 is down again. Back on static DNS servers and working fine. This is so frustrating. What could be going on here? I might have no recourse but to replace this thing with something else.

Seems to be working now. Why on earth would you restarting DNS and the router do anything different than me restarting the router? lol.

Yes I have DNS servers statically configured in Windows, otherwise I wouldn't be able to respond to this post. Setting to automatic pulls the R2's IP for DNS and nothing works. Remote access is enabled.. Do you need anything from me to know you're connecting to my specific router, not someone elses?

No DNS works, including upstream or custom. I'm on the latest I believe... R2 3.0.394. At this point I've done everything I can think of short of factory reset which I REALLY don't want to do. Is there someway to like SSH into this thing to do higher level diagnostics?

We need a terminal or rapp to allow us to perform various networking diagnostics from the R2 itself to validate it can do things it needs to do. Such as performing NSlookups against the DNS servers it's configured for. Also when pointing to ISP for DNS it doesn't seem to show what DNS servers it pulled anywhere? Am I overlooking something?

Was using OpenDNS. Anyway it doesn't matter what DNS I tell the R2 to use, it simply won't accept DNS requests from clients. This is bananas.

I seem to have lost internet access, and I believe it was my ISP, but anyway I was doing some persistent pings to an IP and eventually it came back up. But none of my PCs can resolve DNS. They are configured for DHCP so the DNS passed down to the clients is the router's IP. For whatever reason the R2 won't allow DNS lookups now. If I statically assign the same DNS servers I have the router configured to use, my PCs can get back on the internet. It just seems the R2 is just borked when it comes to DNS. I've rebooted it twice now via the menu and a hard boot by pulling power for 30 seconds. NSlookup states: *** dumaos.lan can't find google.com: Query refused. It'll accept a query for dumaos.lan and resolve though, though oddly my PC will resolve that to the gateway even if I'm pointing to Google DNS so perhaps that's not coming from DNS. Anyway it seems the router itself seems to be able to resolve external DNS... it's able to do connection benchmarks and I assume DNS is being used to resolve hosts for that purpose? I hope yall didn't statically assign IPs for that.

I'm sorry but this is not true at all for a number of reasons, the main one I can think of is a concept called Lag Compensation. Lag compensation was introduced to help counteract the inherent benefits of P2P/Listen Server hosts. Unfortunately some games had very bad implementations of this that actually benefited people with higher latencies more than the actual host. Essentially the host was often "penalized" with artificial lag to level the playing field. That is a crude explanation but basically what happened. This was widely an issue in several CoD games in the past (maybe even still today, I don't play so I don't know), as well as Destiny 1. Many users, including myself (as much as I hate to admit), used to throttle our upload/download speeds and try to introduce artificial lag on my home network, to avoid gaining host in these games, because we'd have a much better experience than if we were host. With that said, this conversation is essentially moot. What you are asking NetDuma to do is actively boot people out of an active game session. That would be nearly no different than DDOSing someone so they would lag out of the game and you win, which is rampant on P2P games these days, see Destiny 1 and 2 competitive matches. Ultimately NetDuma only attempts to prevent bad connections from getting together. It will NEVER negatively affect a gaming session in progress. Doing so would be against the TOS of just about every game there is.

Still interested in the following: 1) a free-form geofilter vs. radius centric. 2) updated ping assist to exclude high pings within the geo-filter