Back to Blog
Guide
8 min readOct 30, 2026

Arma 3 Port Forwarding: Server Ports 2302–2306 UDP and Fixes

Arma 3 servers need UDP 2302–2306 forwarded. Port roles, a port calculator with firewall command, multi-server offsets, browser and BattlEye fixes, and hosting behind CGNAT.

Quick Answer

Forward UDP ports 2302–2306 to the Arma 3 server PC: 2302 is the game port (gameplay and voice), 2303 the Steam query port, 2304 the Steam master port, 2305 is reserved for VON and 2306 carries BattlEye. No TCP rules are needed. If you change -port, the other four ports move with it (+1 to +4). The Arma 3 server does not support IPv6 or DS-Lite, so behind CGNAT you need a public IPv4 from your ISP, a rented server, or a VPN that can forward the exact ports, such as PureVPN.

Arma 3 port forwarding needs five consecutive UDP ports: 2302–2306. Port 2302 carries gameplay and voice, 2303 answers the Steam server browser, 2304 talks to the Steam master server, 2305 is reserved for VON and 2306 carries BattlEye traffic. Forward all five to the server PC’s local IP; no TCP rules are needed.

If you start the server with a different -port, the other four move with it (+1 to +4). Bohemia also warns that the Arma 3 server does not support IPv6 or DS-Lite: you need a real public IPv4 address, which rules out many fibre, cable and 5G lines that use carrier NAT. The CGNAT section covers what to do then.

Official ports

Arma 3 Server Ports (All UDP)

PortOffsetUsed forNotes
2302game portGame port (gameplay and VON)Players connect here; set with -port
2303+1Steam query portServer browser ping, player count
2304+2Steam master portRegisters the server with Steam
2305+3VON portReserved, not used at the moment
2306+4BattlEye trafficAnti-cheat; needed on BattlEye servers

The server also needs to reach BattlEye outbound. Home routers allow this by default, but a strict firewall or hosting provider may not:

Outbound portProtocolDestinationPurpose
2344TCP & UDParma31.battleye.comBattlEye master
2345TCParma31.battleye.comBattlEye master

Arma 3 Port Calculator and Firewall Rule

Enter the game port you pass with -port. The router rules, Windows firewall command and launch line update to match.

Router rule

External 2302–2306 → Internal 2302–2306 | UDP | [server PC’s local IP]

Game 2302 · Query 2303 · Master 2304 · VON 2305 · BattlEye 2306

Windows Defender Firewall (PowerShell)
# Run in PowerShell as Administrator on the Arma 3 server PC
New-NetFirewallRule -DisplayName "Arma 3 Server UDP 2302-2306" -Direction Inbound -Protocol UDP -LocalPort 2302-2306 -Action Allow
Server launch parameters
arma3server_x64.exe -port=2302 -config=server.cfg -profiles=A3Profiles -world=empty

How to Port Forward an Arma 3 Server: 5 Steps

  1. 1

    Reserve the server’s local IP

    Run ipconfig on the server PC, note the IPv4 address (for example 192.168.1.50) and reserve it in your router’s DHCP settings so it never changes.

  2. 2

    Forward UDP 2302–2306 on the router

    Create one rule for the range 2302–2306, protocol UDP, pointing at that IP. If your router only takes single ports, add five rules. Router guides: TP-Link, ASUS, Netgear, FRITZ!Box.

  3. 3

    Allow the ports in Windows Firewall

    Windows drops unsolicited UDP by default. Run the PowerShell line from the calculator, or allow arma3server_x64.exe for private and public networks.

  4. 4

    Start the server with the matching -port

    Install the dedicated server through SteamCMD (app 233780) and launch it with -port=2302, your server.cfg and a profile folder. Only change -port if you run more than one server.

  5. 5

    Test from outside

    Ask a friend to search the server browser, or use Direct Connect with your public IP and port 2302. Testing from the same PC or LAN can fail even when forwarding works; connect locally with 127.0.0.1 or the LAN IP instead.

Router walkthroughs: TP-Link, ASUS, Netgear, FRITZ!Box. Check the public side with our NAT checker.

Hosting from the game instead of a dedicated server? A server started from the Multiplayer menu uses the same ports, starting at 2302, so the same router rule applies.

UPnP: setting upnp = 1; in server.cfg asks a UPnP-enabled router to create the mappings for you. It only helps when the router itself has a public IPv4 address, and Bohemia warns it can delay server start-up by up to 10 minutes if UPnP is blocked, so a manual rule is more predictable.

Running More Than One Arma 3 Server

Each instance needs its own block of five ports. Bohemia suggests leaving at least 100 ports between instances, so the second server uses -port=2402 (UDP 2402–2406), the third -port=2502 (UDP 2502–2506), and so on. Arma 2 servers on the same machine use overlapping defaults, so move one of them.

Troubleshooting

Arma 3 Server Not Showing or Players Can’t Join

Not in the server browser, but Direct Connect works

The game port is open but the Steam query (+1) or master (+2) port is not. Forward the whole 2302–2306 range, not just 2302.

Players time out on join

Check that the rule is UDP, points at the current local IP, and that Windows Firewall allows the range. A second router in front of yours (double NAT) also causes this.

Kicked with BattlEye errors

Make sure +4 (2306 by default) is forwarded and that outbound TCP/UDP 2344 and TCP 2345 to BattlEye are not blocked by a firewall.

You can’t join your own server by public IP

Many routers do not support NAT loopback. Join with 127.0.0.1 on the server PC or the LAN IP from another PC at home.

Everything looks right, still unreachable

Compare your router’s WAN IP with your public IP. If they differ or the WAN IP is 100.64–100.127, you are behind CGNAT or DS-Lite, which Arma 3 cannot host through.

Ports open, still “closed” in a checker

A checker only sees an open port while the server is running and listening. Start the server first, then test.
No public IPv4?

Hosting Arma 3 Behind CGNAT or DS-Lite

Because the Arma 3 server needs real IPv4 and five fixed, consecutive ports, CGNAT (Starlink Residential, 5G home internet, many fibre ISPs) and DS-Lite (common on German and UK cable) leave you three options:

  1. Ask your ISP for a public IPv4 address. Some providers switch you off CGNAT or DS-Lite for free or for a small fee. Then forward ports as above.
  2. Rent a game server or VPS where the provider controls the ports. Best for a 24/7 community server.
  3. Use a VPN that forwards the exact ports. The VPN server supplies the public IPv4, and players join its address on 2302. It has to let you choose the ports: Proton VPN assigns one random port, which cannot cover the +1 to +4 ports Arma 3 needs.
Can forward 2302–2306 UDP

PureVPN

The port forwarding add-on lets you open all ports in one click, or add specific ports up to 15 at a time, so you can open 2302, 2303, 2304, 2305 and 2306 exactly as Arma 3 expects.
  • Choose the exact port numbers instead of a random port
  • Gives the server the public IPv4 that CGNAT and DS-Lite take away
  • Optional dedicated IP so the server address stays the same between sessions
  • Windows app runs on the same PC as arma3server_x64.exe
  • 31-day money-back guarantee
−87%
Black Friday

5-year plan·$1.69/mo $12.95/mo

This page contains affiliate links. If you sign up through them, NAT Checker may earn a commission at no extra cost to you.

Expect added latency: pick a VPN server close to most of your players. If only you and a few friends play, a rented server can cost less. More options are compared in port forwarding behind CGNAT and our VPN port forwarding guide.

Arma 3 vs Arma Reforger Ports

The two games use different ports. Arma 3 needs UDP 2302–2306; Arma Reforger uses UDP 2001 for the game and UDP 17777 for the Steam query. Rules made for one will not work for the other. See the Arma Reforger port forwarding guide if you host both.

Related Game Server Guides

Sources (checked October 30, 2026):

Arma 3 Port Forwarding FAQ

Forward UDP 2302–2306. Bohemia lists 2302 as the game port (gameplay and VON), 2303 as the Steam query port, 2304 as the Steam master port, 2305 as a reserved VON port and 2306 for BattlEye traffic. Change -port and all five move together.

UDP. All five incoming server ports are UDP. The only TCP traffic is outbound from the server to BattlEye on ports 2344 and 2345, which home routers allow by default.

Share this article