How do I get the geo filter working being connected to another router?

[johnnytran]

I've never been able to get the R2 geo filter working while connected to another router. I have a fibre modem, called an NTD (network termination device), it's not a normal modem you can access to configure - it just provides the fibre signal. Scenarios I've tried:

1. - Router is 192.168.1.1 , R2 is 192.168.1.2

NTD  to Router's WAN > Router's LAN to R2's WAN.

Everything but my console connected to the Router. Console is connected to the R2. I can't access the R2 at all from my PC to even see if the geo filter is working but I know it's not because the game searches for up to 200ms matches. I've put 192.168.1.2 in the DMZ in my main router. I believe I've tried this with DHCP disabled and enabled on the R2. In this scenario I don't think my console could even connect online. If it should be able to, I can retry later when the internet isn't being used to confirm.

2.

NTD  to Router's WAN > Router's LAN to R2's LAN.

Same device connections as scenario 1 but this time I can access the R2 from my PC and see nothing appearing on the geo filter so it doesn't work.

3.

NTD to Router's WAN > Routers LAN1 and LAN2 to R2's LAN1 and WAN2

Same device connections as previous scenarios with the console the only device on the R2. Geo filter didn't work.

 

Which scenario should be making the geo filter work and which one should definitely not so I can stop testing it? What are the correct settings to leave on/switch off in the R2 or Router? I recall reading once to put whatever IP is showing up in the R2's WAN on the main page into the DMZ on main router but last night when I was looking, it didn't have one. It did have an IP assigned to the "public IP" though which was strange, it was one from my ISP but it wasn't my actual IP when I checked whatismyip.com. I tried putting it into my main router's dmz but it didn't change anything.

I've also tried assigning a static IP for the R2 in the main router and using that in the DMZ but I don't believe the geo filter worked. What am I doing wrong?

[Netduma Fraser]

Scenario 1 is the one you want to ensure the R2 gets proper internet, however, no scenario will allow you to access the R2 interface from the WAN, you will need to be directly connected to it. Once you've got it in scenario 1 you should see a WAN IP on the System Information page or you should see the R2 IP the other router has given it on that router - both IPs will be the same, then putting that in the router DMZ will work. Once it's all connected up properly, connect your PC to the R2, do this:

1. Quit the application/game/client completely
2. Remove device from the Geo-Filter
3. Resync from the Geo-Filter Map menu
4. Re-add the device to the Geo-Filter with the manual option
5. Set up the Geo-Filter how you like
6. Wait 2 minutes
7. Boot up application/game/client

Then see if it works better.

[johnnytran]

On 3/11/2023 at 11:06 PM, Netduma Fraser said:

Scenario 1 is the one you want to ensure the R2 gets proper internet, however, no scenario will allow you to access the R2 interface from the WAN, you will need to be directly connected to it. Once you've got it in scenario 1 you should see a WAN IP on the System Information page or you should see the R2 IP the other router has given it on that router - both IPs will be the same, then putting that in the router DMZ will work. Once it's all connected up properly, connect your PC to the R2, do this:

1. Quit the application/game/client completely
2. Remove device from the Geo-Filter
3. Resync from the Geo-Filter Map menu
4. Re-add the device to the Geo-Filter with the manual option
5. Set up the Geo-Filter how you like
6. Wait 2 minutes
7. Boot up application/game/client

Then see if it works better.

Thanks Fraser. Followed all your steps except the router I'm currently trying to get this working with doesn't have the DMZ option. I did forward all ports 1-65535 source & destination to the IP address showing up in the R2's main page (the primary router has assigned the R2 192.168.1.221 but I access the R2 from it's own static IP which is 192.168.1.3. All ports forwarded for the 192.168.1.221 IP, tried all ports forwarded for 192.168.1.3 as well)

The geo filter still doesn't work. It does show a ping assist server/player symbol in the US when I launch cod but other than that nothing pops up. Matchmaking still goes up to searching 200ms and eventually connects me to somewhere in Asia on 200-400 ping but if I use the R2 by itself it locks the searching on <15ms and always gives me a local aussie server.

Setup is

NTD to Router's WAN, Routers LAN to R2's WAN, Router's LAN to R2's LAN (to access interface), R2's LAN to Playstation

DHCP disabled on R2. Playstation is getting its static IP from primary router but I also tested with DHCP on, no difference.

[Netduma Fraser]

The port forwarding rule to the .221 IP is good, I think it's best to unplug the router LAN to the R2 LAN, I don't think that will be helping matters at all. The R2 needs to give the PS an IP address. All you need to do is connect the R2 to the router - R2 WAN to router LAN, forward those ports to the R2, leave every setting as the default on the R2 so the R2 controls the PS completely, then with another device setup the Geo-Filter and it will work.