Mount & Blade II: Bannerlord Updated May 11, 2026

Bannerlord Server Port Forwarding

All ports required for a Bannerlord dedicated server: game traffic, web admin, and Steam discovery.

BannerlordPortsFirewallNetworking

Required Ports

Port Protocol Purpose
7210 UDP Game traffic — client connections
7210 TCP Web admin panel and map downloads
27015 UDP Steam server discovery

All three must be open on the host firewall. Port 7210 serves double duty: UDP for game traffic and TCP for the web admin interface.

Changing the Default Port

The game port can be changed via the /port startup argument:

DedicatedCustomServer.Starter.exe /port 7211 /dedicatedcustomserverconfigfile default.txt /dedicatedcustomserverauthtoken YOUR_TOKEN

Update your firewall rules to match the custom port. The Steam query port (27015) is not affected by /port.

UFW (Ubuntu/Debian)

ufw allow 7210/udp
ufw allow 7210/tcp
ufw allow 27015/udp
ufw reload

firewalld (CentOS/RHEL/Fedora)

firewall-cmd --permanent --add-port=7210/udp
firewall-cmd --permanent --add-port=7210/tcp
firewall-cmd --permanent --add-port=27015/udp
firewall-cmd --reload

iptables

iptables -A INPUT -p udp --dport 7210 -j ACCEPT
iptables -A INPUT -p tcp --dport 7210 -j ACCEPT
iptables -A INPUT -p udp --dport 27015 -j ACCEPT

Multiple Servers on One Node

Each server instance needs its own unique port set. Increment by one for each additional instance:

Server 1: 7210 UDP/TCP, 27015 UDP
Server 2: 7211 UDP/TCP, 27016 UDP
Server 3: 7212 UDP/TCP, 27017 UDP

Pass the port to each instance via the /port startup argument. Update firewall rules for each set.

Panel Port Allocation

In WISP or Pterodactyl, allocate 7210 as the primary port and add 27015 as an additional allocation. Map them to the corresponding startup variables in your egg configuration.