NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Deeper250's avatar
Deeper250
Aspirant
Aug 11, 2024

Re: Geofilter not working. XR1000 Router

Same issue with mine. I've tried everything on every forum/thread. Also, since I can't access the geofilter to change it, it defaulted to California and I'm in Dallas, so Call of Duty will only let me play west, higher ping lobbies. Netduma-Fraser 

4 Replies

    • Deeper250's avatar
      Deeper250
      Aspirant

      Same issues as a number of posts regarding XR1000 Geofilter and Ping Heatmaps not functioning. Rapp has not loaded error. I've tried a few different firmware versions - 1.0.0.68, 1.0.0.72 and 1.0.0.74. Factory reset each time. Same issues. Tried multiple different browsers - Chrome, Edge, Firefox, - same issues. It seems like the Geofilter in particular is so corrupted, that it is still defaulting me to California in Call of Duty, even though the game shows I'm located in Dallas. I should normally get starting ping when searching for lobbies of around 18 ping, and it is throwing me into lobbies of +49 bc the DumaOS Geofilter defaulted me to California, gave me an error when trying to change it, and then collapsed altogether and I'm no longer able to access it due to the Rapp has not loaded error. I've also tried changing the Rapp retry from 3-5 and waited 2 minutes after reboot, still nothing. I've scoured every forum for every know issue with this router related to the Geofilter issue and tried every fix. Even updating firmware via TFTP didn't fix. I'm currently a Top 250 Call of Duty Warzone Ranked player this season, and this router is quite literally not allowing me to play the game. And before you ask, no it's not a Call of Duty/server issue. I tried connecting from a different PC in different location in Dallas, and I have normal ping and can connect to Texas lobbies and others.

      • Netduma-Fraser's avatar
        Netduma-Fraser
        NetDuma Partner
        Change the location manually not by the address and then that aspect will work - essentially it's not setup to get you low ping servers currently.

        Reboot from the interface via routerlogin.net/adv_index.htm close the tab, wait 4 minutes then check please.