UPnP table not forwarding ports, slow matchmaking

[Azsry]

Hey there,

 

I don't know how long I've had this issue, but I've been experiencing extremely long queue times in pretty much every game I play, and if I'm queuing with others, they will find a game as soon as I leave the lobby. I have UPnP enabled on both my router and modem/router devices (the modem/router cannot be put into modem mode as its control panel is extremely restrictive) and have disabled all port forwarding rules, but when I start searching for games no extra entries appear in the UPnP table. I assume this is partly the reason why it takes so long for me to find games, but I'm not 100% sure. I also used to have UPnP forwarding enabled in the Misc. settings, but my NAT would always be moderate unless I manually forwarded all the ports. Since turning it off, my NAT would display as Open in Call of Duty, but I still have difficulty searching in other games like CS:GO. Any things I could have overlooked?

 

I'm currently on R1 debug version 1.03.6g running on rb-951g-2hnd. My R1 is connected to an ISP provided modem/router from Sagemcom.

 

Thanks in advance.

[BIG__DOG]

disable upnp then click apply, then, reenable it and click apply, this will flush the upnp and you should be ok.

[BIG__DOG]

i do not use upnp port forwarding in misc. just try using the upnp as normal but make sure it is flushed.

[Azsry]

disable upnp then click apply, then, reenable it and click apply, this will flush the upnp and you should be ok.

 

i do not use upnp port forwarding in misc. just try using the upnp as normal but make sure it is flushed.

Okay, so I found out that the UPnP table does get updated when I play CoD, which is why I get an open NAT with UPnP forwarding disabled, but no ports are being opened when I play CS:GO. I guess that just means I'll have to manually open CS:GO's ports and let UPnP handle everything for CoD.

[Netduma Fraser]

You should disable UPnP on the modem/router. Have you got the R1 in the DMZ of your modem/router? If you're not able to do this then port forward 1024-65,000 to the R1. 

 

Leave UPnP forwarding off it's not needed. 

 

I would imagine the reason you're having long queues is because your Geo-filter settings are too restrictive. You should have ~1000km/650mile radius. 

 

Do you have an issue when playing CS:GO having noticed UPnP not explicitly opening ports for it? You should only use the Geo for casual playlist in CS:GO otherwise don't use it at all.

[Azsry]

You should disable UPnP on the modem/router. Have you got the R1 in the DMZ of your modem/router? If you're not able to do this then port forward 1024-65,000 to the R1. 

 

Leave UPnP forwarding off it's not needed. 

 

I would imagine the reason you're having long queues is because your Geo-filter settings are too restrictive. You should have ~1000km/650mile radius. 

 

Do you have an issue when playing CS:GO having noticed UPnP not explicitly opening ports for it? You should only use the Geo for casual playlist in CS:GO otherwise don't use it at all.

Ah I have UPnP enabled on my modem/router as well. I'll disable that and see if anything changes. I assume this is due to leaving all UPnP work to the R1 and not getting the other device involved to potentially mess things up? I've already put the R1 in DMZ, but the blue box still shows on the Device Manager page. Is this a persistent message as long as there's another router detected on the network, or should it disappear?

 

I don't even have an entry for my computer monitoring any CS:GO ports enabled in the Geo-filter, but the settings are kind of restrictive (2000km, 100ms Ping Assist). I'm not sure if these affect anything without a service enabled.

 

I'm not sure if CS:GO even supports UPnP port mapping by default. As soon as I open BO3 I get DemonwarePortMapping entries in the UPnP table, but nothing pops up with CS:GO (or LoL in my brother's case). I just had a suspicion that this could be a cause for longer-than-usual queue times since required ports aren't being opened, but once again it was just a suspicion. Also, is there any difference between having a Geo-filter service disabled and not having it listed there at all? It seems that once I have added a service, there's no way to remove it from the list so it goes back to nodevice.

[Netduma Fraser]

Ah I have UPnP enabled on my modem/router as well. I'll disable that and see if anything changes. I assume this is due to leaving all UPnP work to the R1 and not getting the other device involved to potentially mess things up? I've already put the R1 in DMZ, but the blue box still shows on the Device Manager page. Is this a persistent message as long as there's another router detected on the network, or should it disappear?

 

I don't even have an entry for my computer monitoring any CS:GO ports enabled in the Geo-filter, but the settings are kind of restrictive (2000km, 100ms Ping Assist). I'm not sure if these affect anything without a service enabled.

 

I'm not sure if CS:GO even supports UPnP port mapping by default. As soon as I open BO3 I get DemonwarePortMapping entries in the UPnP table, but nothing pops up with CS:GO (or LoL in my brother's case). I just had a suspicion that this could be a cause for longer-than-usual queue times since required ports aren't being opened, but once again it was just a suspicion. Also, is there any difference between having a Geo-filter service disabled and not having it listed there at all? It seems that once I have added a service, there's no way to remove it from the list so it goes back to nodevice.

 

Yes it could cause conflicts having UPnP on both enabled. Best to have the R1 do everything at once. That message will stay as long as you are connected behind a router - It's nothing to be concerned about. 

 

If no device is enabled on the Geo-filter then it will not take effect.

 

To double check your suspicion manually port forward the ports for CS for your PC and see if queue times are shorted.

 

No no difference, if it's disabled it's disabled, if it's not there then it's disabled. That's correct, only if the device is remove from device manager will it be disappear from the Geo-filter - I suspect this will change with the new upgrade.