To help people understand, i made my geofilter super tiny so most everyone is outside, and yet it lets people and servers connect to me that are well above my set 60ms.
Still not working. I installed the previous FW which removed Ping Assist. Reinstalled 2.3.2.40 and did a factory reset. Everything else that I had malfunction with now seems to be working properly, yet ping assist just let someone in france with a ping of 90 connect to me while my assist is set to 60. Pretty sure my circle over a 3rd of the US does not reach France.
Yet another connection well above my poing assist setting. This time a a ping of 110 from Mexico. What is the point of this feature? Seems useless.
NetDuma might consider just making a Geofilter setting by country instead of this bull**bleep** with a disformed circle and so called "ping assist". Because so far geofilter has not helped me in any game I've played. I've had this router for almost a year and thus far it's the biggest waste of money I've bought.
What game are you playing and do you have better games by just using the radius? Do you have fast search enabled for ping assist as that could lead to the problem you're having here.
I've tried it with fast search on and off. I do not have better time with radius because people in my radius all seem to have comcast with nasty high pings and here I am with a private Fiber optic ISP. I found out the only way to even turn off ping assist is to delete the devices added to my geofilter, set it to 0, and then add them back. I'm using my PC to play games but have it added in devices as a console (xbox) because otherwise geofilter doesn't work at all. I play several fighting games that all use Unreal Engine but setting it to Unreal Engine does nothing too because it's not PUBG or Fortnite. All I want is the feature to function properly.
I've never been disatisfied by a router in all my life until this one. I paid up for the features and they hardly work. I was just set up with someone with a ping of 120 far outside my circle. Literally DOUBLE the ping assist value. No matter what the ping is, it's covered by a tiny circle of dots, rather than a triangle showing the ping is too high/outside radius.
After watching my geofilter while playing SFV for HOURS, it finally shows someone outside the radius with a triangle signifying a bad he is a bad ping. I think the problem is this firmware doesn't ping them more than once before showing results. Thus if the ping is below threshold the first time, it just assumes it is fine even if it fluctuates. What it needs to do is see the ping has gone over threshold and just block it after the fact. The router has no issue pinging multiple people, I cannot imagine it cannot see the ping has gone above threshold and thus deny the peer.
After watching my geofilter while playing SFV for HOURS, it finally shows someone outside the radius with a triangle signifying a bad he is a bad ping. I think the problem is this firmware doesn't ping them more than once before showing results. Thus if the ping is below threshold the first time, it just assumes it is fine even if it fluctuates. What it needs to do is see the ping has gone over threshold and just block it after the fact. The router has no issue pinging multiple people, I cannot imagine it cannot see the ping has gone above threshold and thus deny the peer.
While that sounds like a good idea, DumaOS doesn't block existing connections because we don't want the device to be used for cheating. That said, this would probably be a legitimate use of such a functionality.
Then my suggestion to you and the Net Duma team is to make Ping Assist poll 2-3 times before accepting a connection as okay by the assist. When you do a trace route in CMD it shows 3 pings for each hop. Do something similar before assuming the ping is good. Fluctuation happens but it's straight up letting high pings in often. I get people who will ping the first time as say 48, and then jump to 70ms and fluctuate heavily and stay way above my ping assist threshold. The entire reason I want to use this feature is because many peer to peer games poll once and then think the connection is "5 bars". I bought my XR450 to help games with poor matchmaking but thus far it has not done me much good. On a hardware level it's fantastic but the DumaOS has been a little bit of a let down over something like DD-WRT. GeoFIlter is the only real feature here that I bought it for.
I guess thats cool. My idea is more like, prior to connection if the ping fluctuates way too much out of range to just deny the peer. I understand why you'd say about cheating. Once you connect to them don't just cut the connection but rather within a set polling time if it goes above the threshold block the peer.
Example, Street Fighter V has a 15 second time frame to accept a match. If you make the assist poll 2-3 times within say 5-10 seconds, it can see the ping is bad and above the limitation set and put the bad triangle on it on GeoFIlter. Most peer to peer games have a long polling time like this for the player to accept the match, with the exception some shooters don't use a server and might poll similarly without the option to accept it.
Perhaps also consider making GeoFilter work for PC not based on game engine, but maybe by game clients. Steam, BlizzApp, Origin, etc. So far most games I play require me to add my PC as a console.
I set my assist lower and it seems to do much better job. Set to 50 it has kept out more people who fluctuate from 60-100, but still let's people who are fluctuating from 50-65ish area in. I'm finding this more comfortable.
Most likely the reason that is happening is because when it initially detects the ping, if it is within your range it will be allowed even if it then goes up after that. That explains why the ping range is sometimes 15ms above.
That's why I suggested it ping the peer more than once. My router shows the ping as it fluctuates. I believe it would be easy for it to let it detect that a few times before making a decision. And if it fluctuates an higher than the set threshold after say 10 seconds it no longer will have the option to refuse. That way you can't expect it to kick people out of your game once it's underway.
As I said, many games have a short timer to accept matches when it's a peer to peer game like say, street fighter or Tekken. That should be plenty of time for the router to make the call on an unstable ping above the threshold.
Found another problem when ping assist is enabled. Now it's blocking servers I already have in my allow list. All the Street Fighter V servers are in Oregon and have a high ping, like 100+. But I allow them so matchmaking can run in the game. Even with them on the allow list, a lot of times they show as a triangle, only to show I've named the server and allowed it when I ping it. Not an issue had with just using radius, however radius letting in anyone within it is worse in my experience.
That shouldn't be the case at all, are you 100% they are the same server? Servers are located in clusters in the same location and can appear to have a very similar ID but are slightly different.
I thought it was clustered up and sometimes I see it is but there's a case where its just a triangle and when I click it the server is already allowed. It started doing it after I flushed the cloud. Doesn't se to be blocking it.
Also I'd like to say Ping Assist seems to work better as time goes on? I had to set it much lower to make it work better, like 40 threshold. But it just caught someone literally with a ping of 41 and denied it. Which is funny to me.
