JR_

Same issue since launch firmware up to the current one. I have to reboot it daily to connect, and geofilter does not work if I don't.

The bug where the router becomes nonresponsive to web connections is still apparently present, ngl, getting pretty tired of rebooting it every time I want to access settings

The bug where the router becomes nonresponsive to web connections is still apparently present, ngl, getting pretty tired of rebooting it every time I want to access settings

The bug where the router becomes nonresponsive to web connections is still apparently present, ngl, getting pretty tired of rebooting it every time I want to access settings

Gave this a try - initially it immediately connected me to a DC server, but after that first game, it remains sitting at searching for a match <25ms ping, with either radius or custom geofilter applied and the settings from above changed (geolatency off, ping assist off, fast search off) - I also tried Steady Ping off, though that didn't seem to help either.
This is different from before updating in two ways, the first being obviously that it connected to DC once, the second being that it's now failing with searching at <25ms, before it was starting at <100ms and counting up - vs perpetually stuck at <25 and never raising, nor according to the geofilter map, checking any servers.
I tried restarting the game and despite actively pinging the DC servers, it refuses to connect again - I also tried manually allowing them, same issue, despite being allowed the duma UI says they're blocked and MW3 won't connect.


If I expand the range to include NY it will connect again, still seemingly preferring the NY servers, despite them being farther away geographically and with a worse ping than the DC servers.
 
edit: Tried restarting the game again and trying again, it still would not connect to DC servers, failing to connect to NY repeatedly. When I clicked over to Custom filter with a preselected region around the DC servers it immediately connected to a DC server. I left and tried to connect again, and once again it was stuck searching, blocking NY servers and refusing to even ping a DC server.

The white dots are from the moment it connected to the DC server, but after leaving and trying to search again, it won't find them.
Out of curiosity I checked Zombies and it exhibits the same behavior as multiplayer - refuses to even ping DC servers, attempts and fails to connect to out of range NY servers:

I can't replicate the switching between Simple/Custom filter shape to connect to a DC server. Possible it might work after fully restarting the game, but not much of a solution if it only works once and inconsistently at that each startup. Backing out of search and changing modes then returning does not work either.

No luck, it no longer connects to servers outside the highlighted area, but it's also not connecting to the DC servers for whatever reason
One oddity, unsure if it's meaningful to you, but set up that way, the first search is <~100ms ping ingame, rather than <20 like it usually is (moot since it didn't connect, just pointing it out)
edit: after expanding the region back to include NY, it did connecting to matchmaking servers and began searching at <33ms - I'm now wondering if the problem is that there's no matchmaking server in the DC area, and so if it's filtered to just there it won't connect at all?