F5F Stay Refreshed Power Users Networks Configure double router port forwarding to access your CSGO server securely.

Configure double router port forwarding to access your CSGO server securely.

Configure double router port forwarding to access your CSGO server securely.

T
thlortiz27
Junior Member
49
01-21-2023, 10:28 AM
#1
I'm working on setting up a CSGO server for you and your friends. Your PC is linked to a router, which connects to another router that ultimately accesses the internet. You're having trouble opening a specific port so others can join the server outside your local network. On the internet-facing router, you've configured the necessary ports using the second router's IP (192.168.2.103) and mapped 27015 to it. On your PC's local router, you've set up a similar rule pointing to 192.168.2.100:27015. The server itself starts without issues but doesn't appear in the CSGO client browser and isn't reachable via public IP. You checked port status using an online tool and found it closed, yet it works through your LAN. You also verified the source wiki and confirmed TCP/UDP settings are correct. Consider double-checking the forwarding rules, ensuring no conflicting rules exist, and verifying the server's configuration on the target machine.
T
thlortiz27
01-21-2023, 10:28 AM #1

I'm working on setting up a CSGO server for you and your friends. Your PC is linked to a router, which connects to another router that ultimately accesses the internet. You're having trouble opening a specific port so others can join the server outside your local network. On the internet-facing router, you've configured the necessary ports using the second router's IP (192.168.2.103) and mapped 27015 to it. On your PC's local router, you've set up a similar rule pointing to 192.168.2.100:27015. The server itself starts without issues but doesn't appear in the CSGO client browser and isn't reachable via public IP. You checked port status using an online tool and found it closed, yet it works through your LAN. You also verified the source wiki and confirmed TCP/UDP settings are correct. Consider double-checking the forwarding rules, ensuring no conflicting rules exist, and verifying the server's configuration on the target machine.

C
ChubbyCantRun
Junior Member
6
01-21-2023, 02:39 PM
#2
The numbers seem inconsistent. Router One is sending traffic to Router Two's IP, which is 192.168.1.xxx, while Router Two is directing it to the PC's IP at 192.168.2.xxx. This suggests a mismatch in subnet settings. If Router Two is meant to use the .1.xxx subnet, all connected devices should share that range, yet they're being routed to .2.xxx. My setup works differently: Router One connects to the internet and forwards to 192.168.0.1, while Router Two uses a DHCP server at 192.168.1.1 and sends traffic to its LAN IP, which is 192.168.1.xxx.
C
ChubbyCantRun
01-21-2023, 02:39 PM #2

The numbers seem inconsistent. Router One is sending traffic to Router Two's IP, which is 192.168.1.xxx, while Router Two is directing it to the PC's IP at 192.168.2.xxx. This suggests a mismatch in subnet settings. If Router Two is meant to use the .1.xxx subnet, all connected devices should share that range, yet they're being routed to .2.xxx. My setup works differently: Router One connects to the internet and forwards to 192.168.0.1, while Router Two uses a DHCP server at 192.168.1.1 and sends traffic to its LAN IP, which is 192.168.1.xxx.