How to port forward a Counter-Strike 2 server

Counter-Strike 2 uses one port number on both protocols, the same arrangement as every other Source-engine server. UDP is gameplay and queries; TCP on the same number is part of the Steam handshake.

Your setup

Pick the firmware family, not the exact model — the menus are identical across a range.

Default is 27015. If you changed it, it is the value of -port.

The private address of the machine running the server — ipconfig on Windows, ip addr on Linux. It starts with 192.168, 10. or 172.

Open these

This firmware accepts ranges, so each line below is a single rule.

  • 27015 TCP
  • 27015 UDP
  • 27015UDPGame trafficAll CS2 gameplay and queries.
  • 27015TCPSteam handshakeSame number, TCP. Forward both protocols or the server intermittently fails to register.

Only if you want them

The server works without these. Every port you open is a port someone can knock on, so skip anything you do not need.

  • 27020 UDP
  • 27020UDPSourceTVDemo relay. Optional.

Do not open these

This game has no remote-administration port to get wrong. Forward only what is listed on the left and nothing else.

Step by step: your router

  1. 1

    Give the server a fixed local IP

    A forward points at one address. If the server picks up a different one after a reboot, the rule silently starts pointing at nothing — this is why forwards "stop working" on their own.

    On this router:look for DHCP Reservation, Address Reservation, Static Lease or Manually Assigned IP

  2. 2

    Open the router admin page

    Try these addresses in a browser on the same network:

    • 192.168.0.1
    • 192.168.1.1
    • 192.168.2.1
    • 10.0.0.1

    Almost always printed on a sticker on the router itself.

  3. 3

    Find the port forwarding page

    Port Forwarding, Virtual Server, NAT, Applications & Gaming, or Port Mapping

    Vendors use at least six names for the same feature. Whatever it is called, the page you want is the one asking for a port, a protocol and a device on your network. If the external and internal port fields both exist, set them to the same number.

  4. 4

    Create one rule per line

    a description field, if there is oneExternal / WAN / Public / Service portInternal / LAN / Private portProtocolInternal IP / Device / Server IP
    Counter-Strike 22701527015TCPyour server’s local IP
    Counter-Strike 22701527015UDPyour server’s local IP

    External and internal port are the same number here. Changing the external port is possible, but then everyone connects on the new one, so keep them matched unless you have a reason.

  5. 5

    Let the server through its own firewall

    The router now sends traffic to the machine, and the machine can still refuse it. Windows Defender Firewall in particular blocks a freshly installed dedicated server by default, which looks exactly like a failed forward.

Take it with you

Counter-Strike 2 — port forwarding rules
----------------------------------------
27015  TCP  ->  <server local IP>
27015  UDP  ->  <server local IP>

Check whether it worked

Test from outside your own network. Connecting from a machine in the house proves nothing — that traffic never leaves the LAN and never touches the rule you just wrote.

What usually goes wrong

RCON on a Source server rides the TCP side of the game port rather than a port of its own, which means you cannot simply choose not to forward it. Set a strong RCON password and treat it as the credential it is — an attacker with your RCON password can change every server setting and load content of their choosing.

Not forwarding at all

Competitive play is unforgiving about latency variance, and a server sharing a household connection with everything else in the house will show it. This is one of the few genres where the hosting decision is really a gameplay decision.

Support & Help