Usage

Here are some one-liners to quickly start a BF2 server.

If you want the BF2 server to be listed on a master server, see DNS Spoofing.

BF2

# BF2 server
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0

# BF2 server with random coop maps
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0 bash -c '(esai-helper -m bf2 get maplist; esai-helper -m xpack get maplist) | grep gpm_coop | shuf > /server/bf2/mods/bf2/settings/maplist.con && exec ./start.sh'

# BF2 server with random conquest maps
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0 bash -c '(esai-helper -m bf2 get maplist; esai-helper -m xpack get maplist) | grep gpm_cq | shuf > /server/bf2/mods/bf2/settings/maplist.con && exec ./start.sh'

# Read BF2 server readme
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/readmes/readme-linux.txt
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/readmes/readmeserver.txt

# By using this image, you agree to the licenses
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/readmes/eula.txt # EULA for the BF2 dedicated Linux server
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/readmes/lgpl.txt # LGPL
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/readmes/pb_eula.txt # EULA for the EULA for PunkBuster

To customize the server, edit serversettings.con and maplist.con accordingly, and start the server:

# Generate serversettings.con and customize
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/mods/bf2/settings/serversettings.con > serversettings.con
# Generate maplist.con (coop)
docker run --rm startersclan/docker-bf2:v1.5.3153.0 bash -c '(esai-helper -m bf2 get maplist; esai-helper -m xpack get maplist) | grep gpm_coop' > maplist.con
# Generate maplist.con (conquest)
docker run --rm startersclan/docker-bf2:v1.5.3153.0 bash -c '(esai-helper -m bf2 get maplist; esai-helper -m xpack get maplist) | grep gpm_cq' > maplist.con
# BF2 server
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp \
    -v "$(pwd)/serversettings.con:/server/bf2/mods/bf2/settings/serversettings.con:ro" \
    -v "$(pwd)/maplist.con:/server/bf2/mods/bf2/settings/maplist.con:ro" \
    startersclan/docker-bf2:v1.5.3153.0

See docker-compose examples:

BF2 LAN server
BF2 server with PRMasterServer as master server
BF2 server with PRMasterServer as master server running as a sidecar
BF2 server with BF2Hub as master server
BF2 server with BF2Hub as master server (using bf2hub binaries)
BF2 LAN server with an ESAI default strategy
BF2 LAN server with community-optimized ESAI strategies
BF2 LAN server with custom ESAI strategies

BF2 with BF2Statistics 2.x.x

To customize the server, edit serversettings.con and maplist.con accordingly, and start the server with DNS spoofing to the ASP webserver 192.168.1.100:

# Generate serversettings.con and customize
docker run --rm startersclan/docker-bf2:v1.5.3153.0-bf2stats-2.9.4 cat /server/bf2/mods/bf2/settings/serversettings.con > serversettings.con
# Generate maplist.con (coop)
docker run --rm startersclan/docker-bf2:v1.5.3153.0-bf2stats-2.9.4 bash -c '(esai-helper -m bf2 get maplist; esai-helper -m xpack get maplist) | grep gpm_coop' > maplist.con
# Generate maplist.con (conquest)
docker run --rm startersclan/docker-bf2:v1.5.3153.0-bf2stats-2.9.4 bash -c '(esai-helper -m bf2 get maplist; esai-helper -m xpack get maplist) | grep gpm_cq' > maplist.con
# Generate BF2StatisticsConfig.py and customize
docker run --rm startersclan/docker-bf2:v1.5.3153.0-bf2stats-2.9.4 cat /server/bf2/python/bf2/BF2StatisticsConfig.py > BF2StatisticsConfig.py
# BF2 server with BF2Statistics 2.x.x
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp \
    -v "$(pwd)/serversettings.con:/server/bf2/mods/bf2/settings/serversettings.con:ro" \
    -v "$(pwd)/maplist.con:/server/bf2/mods/bf2/settings/maplist.con:ro" \
    -v "$(pwd)/BF2StatisticsConfig.py:/server/bf2/python/bf2/BF2StatisticsConfig.py:ro" \
    --add-host bf2web.gamespy.com:192.168.1.100 \
    --add-host gamestats.gamespy.com:192.168.1.100 \
    --add-host eapusher.dice.se:192.168.1.100 \
    startersclan/docker-bf2:v1.5.3153.0-bf2stats-2.9.4

See docker-compose examples:

BF2 LAN server with BF2Statistics 2.x.x ASP as stats server
BF2 server with BF2Hub as master server and BF2Statistics 2.x.x ASP as stats server

BF2 with BF2Statistics 3.x.x

To customize the server, edit serversettings.con and maplist.con accordingly, and start the server with DNS spoofing to the ASP webserver 192.168.1.100:

# Generate serversettings.con and customize
docker run --rm startersclan/docker-bf2:v1.5.3153.0-bf2stats-3.3.0 cat /server/bf2/mods/bf2/settings/serversettings.con > serversettings.con
# Generate maplist.con (coop)
docker run --rm startersclan/docker-bf2:v1.5.3153.0-bf2stats-3.3.0 bash -c '(esai-helper -m bf2 get maplist; esai-helper -m xpack get maplist) | grep gpm_coop' > maplist.con
# Generate maplist.con (conquest)
docker run --rm startersclan/docker-bf2:v1.5.3153.0-bf2stats-3.3.0 bash -c '(esai-helper -m bf2 get maplist; esai-helper -m xpack get maplist) | grep gpm_cq' > maplist.con
# Generate BF2StatisticsConfig.py and customize
docker run --rm -it startersclan/docker-bf2:v1.5.3153.0-bf2stats-3.3.0 cat /server/bf2/python/bf2/BF2StatisticsConfig.py > BF2StatisticsConfig.py
# BF2 server with BF2Statistics 3.x.x
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp \
    -v "$(pwd)/serversettings.con:/server/bf2/mods/bf2/settings/serversettings.con:ro" \
    -v "$(pwd)/maplist.con:/server/bf2/mods/bf2/settings/maplist.con:ro" \
    -v "$(pwd)/BF2StatisticsConfig.py:/server/bf2/python/bf2/BF2StatisticsConfig.py:ro" \
    --add-host bf2web.gamespy.com:192.168.1.100 \
    --add-host gamestats.gamespy.com:192.168.1.100 \
    --add-host eapusher.dice.se:192.168.1.100 \
    startersclan/docker-bf2:v1.5.3153.0-bf2stats-3.3.0

See docker-compose examples:

BF2 LAN server with BF2Statistics 3.x.x ASP as stats server
BF2 server with BF2Hub as master server and BF2Statistics 3.x.x ASP as stats server

AIX 2.0 mod

# BF2 server running AIX 2.0 mod
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0-aix2

# BF2 server running AIX 2.0 mod with random coop maps
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0-aix2 bash -c 'esai-helper -m aix2 get maplist | grep gpm_coop | shuf > /server/bf2/mods/aix2/settings/maplist.con && exec ./start.sh +modPath mods/aix2'

# BF2 server running AIX 2.0 mod with random conquest maps
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0-aix2 bash -c 'esai-helper -m aix2 get maplist | grep gpm_cq | shuf > /server/bf2/mods/aix2/settings/maplist.con && exec ./start.sh +modPath mods/aix2'

To customize the server, edit serversettings.con and maplist.con accordingly:

# Generate serversettings.con and customize
docker run --rm startersclan/docker-bf2:v1.5.3153.0-aix2 cat /server/bf2/mods/aix2/settings/serversettings.con > serversettings.con
# Generate maplist.con (coop)
docker run --rm startersclan/docker-bf2:v1.5.3153.0-aix2 esai-helper -m aix2 get maplist | grep gpm_coop > maplist.con
# Generate maplist.con (conquest)
docker run --rm startersclan/docker-bf2:v1.5.3153.0-aix2 esai-helper -m aix2 get maplist | grep gpm_cq > maplist.con
# BF2 server running AIX 2.0 mod
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp \
    -v "$(pwd)/serversettings.con:/server/bf2/mods/aix2/settings/serversettings.con:ro" \
    -v "$(pwd)/maplist.con:/server/bf2/mods/aix2/settings/maplist.con:ro" \
    startersclan/docker-bf2:v1.5.3153.0-aix2

See docker-compose examples:

BF2 LAN server running AIX 2.0 mod

BF2All64 mod

# BF2 server running BF2All64 mod
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0-bf2all64

# BF2 server running BF2All64 mod with random coop maps
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0-bf2all64 bash -c 'esai-helper -m bf2all64 get maplist | grep gpm_coop | shuf > /server/bf2/mods/bf2all64/settings/maplist.con && exec ./start.sh +modPath mods/bf2all64'

# BF2 server running BF2All64 mod with random conquest maps
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0-bf2all64 bash -c 'esai-helper -m bf2all64 get maplist | grep gpm_cq | shuf > /server/bf2/mods/bf2all64/settings/maplist.con && exec ./start.sh +modPath mods/bf2all64'

To customize the server, edit serversettings.con and maplist.con accordingly:

# Generate serversettings.con and customize
docker run --rm startersclan/docker-bf2:v1.5.3153.0-bf2all64 cat /server/bf2/mods/bf2all64/settings/serversettings.con > serversettings.con
# Generate maplist.con (coop)
docker run --rm startersclan/docker-bf2:v1.5.3153.0-bf2all64 esai-helper -m bf2all64 get maplist | grep gpm_coop > maplist.con
# Generate maplist.con (conquest)
docker run --rm startersclan/docker-bf2:v1.5.3153.0-bf2all64 esai-helper -m bf2all64 get maplist | grep gpm_cq > maplist.con
# BF2 server running BF2All64 mod
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp \
    -v "$(pwd)/serversettings.con:/server/bf2/mods/bf2all64/settings/serversettings.con:ro" \
    -v "$(pwd)/maplist.con:/server/bf2/mods/bf2all64/settings/maplist.con:ro" \
    startersclan/docker-bf2:v1.5.3153.0-bf2all64

See docker-compose examples:

BF2 LAN server running BF2All64 mod
BF2 LAN server running BF2All64 mod with ESAI optimized strategies

Forgotten Hope 2 mod

# BF2 server running Forgotten Hope 2 mod
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0-fh2-4.6.304

# BF2 server running Forgotten Hope 2 mod with random coop maps
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0-fh2-4.6.304 bash -c 'esai-helper -m fh2 get maplist | grep gpm_coop | shuf > /server/bf2/mods/fh2/settings/maplist.con && exec ./start.sh +modPath mods/fh2'

# BF2 server running Forgotten Hope 2 mod with random conquest maps
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp startersclan/docker-bf2:v1.5.3153.0-fh2-4.6.304 bash -c 'esai-helper -m fh2 get maplist | grep gpm_cq | shuf > /server/bf2/mods/fh2/settings/maplist.con && exec ./start.sh +modPath mods/fh2'

To customize the server, edit serversettings.con and maplist.con accordingly:

# Generate serversettings.con and customize
docker run --rm startersclan/docker-bf2:v1.5.3153.0-fh2-4.6.304 cat /server/bf2/mods/fh2/settings/serversettings.con > serversettings.con
# Generate maplist.con (coop)
docker run --rm startersclan/docker-bf2:v1.5.3153.0-fh2-4.6.304 esai-helper -m fh2 get maplist | grep gpm_coop > maplist.con
# Generate maplist.con (conquest)
docker run --rm startersclan/docker-bf2:v1.5.3153.0-fh2-4.6.304 esai-helper -m fh2 get maplist | grep gpm_cq > maplist.con
# BF2 server running fh2 mod
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp \
    -v "$(pwd)/serversettings.con:/server/bf2/mods/fh2/settings/serversettings.con" \
    -v "$(pwd)/maplist.con:/server/bf2/mods/fh2/settings/maplist.con" \
    startersclan/docker-bf2:v1.5.3153.0-fh2-4.6.304

See docker-compose examples:

BF2 LAN server running Forgotten Hope 2 mod

DNS spoofing

DNS spoofing: Background

Problem: The Battlefield 2 client and server binaries are hardcoded with gamespy DNS records, e.g. bf2web.gamespy.com. Because gamespy has shut down, the DNS records no longer exist on public DNS servers. In order to keep the game's multiplayer working, DNS must be spoofed to keep it working.

Here's a table of needed DNS entries:

DNS entry	Description	Needed by Client?	Needed by Server?
battlefield2.available.gamespy.com	To reach master server and CD key server	✅	✅
battlefield2.master.gamespy.com	To reach master server and CD key server	✅	✅
battlefield2.ms14.gamespy.com	To reach master server and CD key server	✅	✅
master.gamespy.com	To reach master server and CD key server	✅	✅
motd.gamespy.com	To reach master server and CD key server	✅	✅
gpsp.gamespy.com	To reach master server and CD key server	✅	✅
gpcm.gamespy.com	To reach master server and CD key server	✅	✅
gamespy.com	To reach master server and CD key server	✅	✅
bf2web.gamespy.com	For client: For BFHQ to work in-game For server: To get stats from the web stats server (i.e. ASP)	✅	✅
gamestats.gamespy.com	Unknown. May be needed by server?	❓	❓
eapusher.dice.se	For client: For the EA popup image to work upon logging in. The address is hardcoded as http://eapusher.dice.se/image_english.png	✅	❌

You will need to spoof the DNS accordingly, based on your setup.

DNS spoofing: for server to be listed on BF2Hub master server

If you want the BF2 server to be listed a public master server such as BF2Hub, for better server discoverability by clients and to make it easier for clients to connect to your server, DNS spoofing is needed for the BF2 server. DNS spoofing can be done using --add-host on docker run, or extra_hosts key in docker-compose.yml.

To list a BF2 server on BF2Hub (IP address 92.51.181.102):

If the server is behind NAT, ensure to port-forward both UDP ports 16567 and 29900 to your server. sv.internet 1 must be used in serversettings.con (already present by default).

The server will be listed as an unranked server on BF2Hub, since it is not a BF2Hub official server.

# BF2 server with BF2Hub as master server
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp \
    --add-host battlefield2.available.gamespy.com:92.51.181.102 \
    --add-host battlefield2.master.gamespy.com:92.51.181.102 \
    --add-host battlefield2.ms14.gamespy.com:92.51.181.102 \
    --add-host master.gamespy.com:92.51.181.102 \
    --add-host motd.gamespy.com:92.51.181.102 \
    --add-host gpsp.gamespy.com:92.51.181.102 \
    --add-host gpcm.gamespy.com:92.51.181.102 \
    --add-host gamespy.com:92.51.181.102 \
    startersclan/docker-bf2:v1.5.3153.0

To get BF2Hub.com IP addresses:

nslookup servers.bf2hub.com

See docker-compose example:

BF2 server with BF2Hub as master server

DNS spoofing: for server to be listed on PRMasterServer master server

If you want the BF2 server to be listed on a private master server such as PRMasterServer, for better server discoverability by clients and to make it easier for clients to connect to your server, DNS spoofing is needed for the BF2 server. DNS spoofing can be done using --add-host on docker run, or extra_hosts key in docker-compose.yml.

To list a BF2 server on PRMasterServer (assuming PRMasterServer IP address is 192.168.1.100):

If the server is behind NAT, ensure to port-forward both UDP ports 16567 and 29900 to your server. sv.internet 1 must be used in serversettings.con (already present by default).

# BF2 server with PRMasterServer as master server
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp \
    --add-host battlefield2.available.gamespy.com:192.168.1.100 \
    --add-host battlefield2.master.gamespy.com:192.168.1.100 \
    --add-host battlefield2.ms14.gamespy.com:192.168.1.100 \
    --add-host master.gamespy.com:192.168.1.100 \
    --add-host motd.gamespy.com:192.168.1.100 \
    --add-host gpsp.gamespy.com:192.168.1.100 \
    --add-host gpcm.gamespy.com:192.168.1.100 \
    --add-host gamespy.com:192.168.1.100 \
    startersclan/docker-bf2:v1.5.3153.0

See docker-compose examples:

BF2 server with PRMasterServer as master server
BF2 server with PRMasterServer as master server running as a sidecar

DNS spoofing: for server to send stats snapshots to BF2Statistics 2.x.x

In order for bf2stats-2.x.x variants to be able to send stats snapshots to a BF2Statistics 2.x.x ASP webserver, DNS spoofing is needed for the BF2 server. DNS spoofing can be done using --add-host on docker run, or extra_hosts key in docker-compose.yml.

To send stats snapshots from bf2stats-2.x.x (assuming BF2Statistics 2.x.x ASP webserver IP address is 192.168.1.100):

# BF2 server with BF2Statistics 2.x.x
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp \
    --add-host bf2web.gamespy.com:192.168.1.100 \
    --add-host gamestats.gamespy.com:192.168.1.100 \
    --add-host eapusher.dice.se:192.168.1.100 \
    startersclan/docker-bf2:v1.5.3153.0-bf2stats-2.9.4

See docker-compose examples:

BF2 server with BF2Statistics 2.x.x ASP as stats server
BF2 server with BF2Hub as master server and BF2Statistics 2.x.x ASP as stats server

DNS spoofing: for server to send stats snapshots to BF2Statistics 3.x.x

In order for bf2stats-3.x.x variants to be able to send stats snapshots to a BF2Statistics 3.x.x ASP webserver, DNS spoofing is needed for the BF2 server. DNS spoofing can be done using --add-host on docker run, or extra_hosts key in docker-compose.yml.

To send stats snapshots from bf2stats-3.x.x (assuming BF2Statistics 3.x.x ASP webserver IP address is 192.168.1.100):

# BF2 server with BF2Statistics 3.x.x
docker run --rm -it -p 16567:16567/udp -p 29900:29900/udp \
    --add-host bf2web.gamespy.com:192.168.1.100 \
    --add-host gamestats.gamespy.com:192.168.1.100 \
    --add-host eapusher.dice.se:192.168.1.100 \
    startersclan/docker-bf2:v1.5.3153.0-bf2stats-3.3.0

See docker-compose examples:

BF2 server with BF2Statistics 3.x.x ASP as stats server
BF2 server with BF2Hub as master server and BF2Statistics 3.x.x ASP as stats server

ESAI

ESAI greatly enhances bot performance, and is compatible with any BF2 mod. It is included but not enabled by default.

A handy tool called esai-helper is included in all images. It can be used to list gamemodes, generate maplists for a mod, list a levels' strategies.ai, apply default or custom strategies.ai to levels, and more. See esai-helper --help for usage.

To use a default strategy for all levels, see this example.

To override the default strategy with a level-specific strategy, optimized strategies config files are included in each image. These strategies have been optimized by the BF2SP64 community:

/esai-optimized-strategies-bf2.txt
/esai-optimized-strategies-bf2all64.txt
/esai-optimized-strategies-xpack.txt

To use optimized strategies for levels, see this example. For bf2all64 mod, see this example.

To use custom strategies for levels, see example.

# Read ESAI readmes
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/mods/bf2/esai/readme.txt
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/mods/bf2/esai/directory.txt
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/mods/bf2/esai/credits.txt
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat "/server/bf2/mods/bf2/esai/quick start.txt"
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat "/server/bf2/mods/bf2/esai/users guide.txt"
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/mods/bf2/esai/version.txt
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/mods/bf2/esai/mapfiles/dir.txt
docker run --rm startersclan/docker-bf2:v1.5.3153.0 cat /server/bf2/mods/bf2/esai/plugin/dir.txt

# esai-helper useful one-liners
docker run --rm startersclan/docker-bf2:v1.5.3153.0 esai-helper --help # See usage
docker run --rm startersclan/docker-bf2:v1.5.3153.0 esai-helper --mod bf2 get gamemodes # Get gamemodes
docker run --rm startersclan/docker-bf2:v1.5.3153.0 esai-helper --mod bf2 get levels # Get levels
docker run --rm startersclan/docker-bf2:v1.5.3153.0 esai-helper --mod bf2 get maplist # Generate a maplist for maplist.con
docker run --rm startersclan/docker-bf2:v1.5.3153.0 esai-helper --mod bf2 get mods # Get mods
docker run --rm startersclan/docker-bf2:v1.5.3153.0 esai-helper --mod bf2 get strategies # Get strategies
docker run --rm startersclan/docker-bf2:v1.5.3153.0 esai-helper --mod bf2 apply default-strategy <strategy> # Apply a default strategy
docker run --rm startersclan/docker-bf2:v1.5.3153.0 esai-helper --mod bf2 apply <level> <gamemode> <size> <strategy> # Apply a strategy for a level
docker run --rm startersclan/docker-bf2:v1.5.3153.0 esai-helper --mod bf2 delete <level> <gamemode> <size> <strategy> # Delete a strategy for a level
docker run --rm startersclan/docker-bf2:v1.5.3153.0 esai-helper --mod bf2 apply -f strategies.txt # Apply strategies for levels
docker run --rm startersclan/docker-bf2:v1.5.3153.0 esai-helper --mod bf2 delete -f strategies.txt # Delete strategies for levels

FAQ

Q: Server not listed on master server

A: Ensure you spoof Gamespy DNS for the gameserver. See this example.

In addition, the gameserver lists its info on master server based on the sv.serverPort and sv.gameSpyPort in serversettings.con. If you are running on non-standard ports instead of the standard gameserver ports UDP 16567 and UDP 29900, you need to use those ports in docker-compose.yml and serversettings.con.

Q: Server not listed on master server after `docker-compose down && docker-compose up`

A: This is caused by stale UDP conntrack entries which are not deleted by docker on container teardown that was recently fixed in docker v23.0.0.

For older docker version, the solution is to run a sidecar container that deletes the stale UDP conntrack entries on BF2 container startup, see this example. Alternatively, a sidecar init-container can achieve the same result, see this example. Alternatively, run on host networking (i.e. network_mode: host in docker-compose.yml) to avoid SNAT completely, but that is not advised because it defeats the purpose of containerization.

To illustate the details:

# Start BF2 server
$ docker-compose up
$ sleep 10

# Get UDP conntrack entries
# 92.51.181.102:27900 is BF2Hub master server
# 92.51.181.102:29910 is BF2Hub cdkey server
# 92.51.149.13 is the BF2Hub master listing server
# 192.168.1.100 is our host machine's IP address
# 172.17.48.2:29900 is the bf2 container's IP address and gamespy port
# 1st line: On init, the BF2 server talks to the BF2Hub master server and registers itself to be listed. After which, both send heartbeats to each other at regular intervals. Hence [ASSURED]
# 2st line: The BF2 server sends heartbeats to the cd key server at regular intervals without a response. Hence [UNREPLIED]
# 3rd line: A few seconds after the BF2 server registers itself to be listed, the BF2 master listing server talks with the BF2 server, and the BF2 server sends its details, at regular intervals. Hence [ASSURED]
$ sudo conntrack -L -p udp | grep 92.51
udp      17 115 src=172.17.48.2 dst=92.51.181.102 sport=29900 dport=27900 src=92.51.181.102 dst=192.168.1.100 sport=27900 dport=29900 [ASSURED] mark=0 use=1
udp      17 25 src=172.17.48.2 dst=92.51.181.102 sport=29900 dport=29910 [UNREPLIED] src=92.51.181.102 dst=192.168.1.100 sport=29910 dport=29900 mark=0 use=1
udp      17 118 src=92.51.149.13 dst=192.168.1.100 sport=58665 dport=29900 src=172.17.48.2 dst=92.51.149.13 sport=29900 dport=58665 [ASSURED] mark=0 use=1

# Stop and tearfown BF2 server
$ docker-compose down

# Get UDP conntrack entries
# Line 1: Notice that this UDP conntrack entry to the BF2 master server remains and is not removed
# Line 2: Notice that this UDP conntrack entry to the BF2 master server remains and is not removed
# If we started a new BF2 server container now, it will not receive any UDP packets from the BF2Hub master server and listing server, since the packets will end up being sent to the old container's IP (172.17.64.2), and instead of the new container's IP
$ sudo conntrack -L -p udp | grep 92.51
udp      17 23 src=172.17.48.2 dst=92.51.181.102 sport=29900 dport=29910 [UNREPLIED] src=92.51.181.102 dst=192.168.1.100 sport=29910 dport=29900 mark=0 use=1
udp      17 113 src=172.17.48.2 dst=92.51.181.102 sport=29900 dport=27900 src=92.51.181.102 dst=192.168.1.100 sport=27900 dport=29900 [ASSURED] mark=0 use=1

# Start BF2 server with a new container IP address
$ docker-compose up
$ sleep 10

# Get UDP conntrack entries
# 172.17.64.2 is the new BF2 container's IP address
# Line 1: BF2 server talking with the BF2Hub master server. However, instead of [ASSURED], it is [UNREPLIED]
# Line 2: This is the culprit. This stale UDP conntrack entry is directing BF2Hub master server replies to the old container IP (172.17.48.2), and the entry remains [ASSURED]
# Line 3: BF2 server talking with the BF2Hub cd key server. [UNREPLIED] is expected
# Line 4: The master listing server talks with the BF2 server. [ASSURED] is expected
# Hence, to solve this we need to remove the 3rd line from the conntrack table
$ sudo conntrack -L -p udp | grep 92.51
udp      17 26 src=172.17.64.2 dst=92.51.181.102 sport=29900 dport=27900 [UNREPLIED] src=92.51.181.102 dst=192.168.1.100 sport=27900 dport=40589 mark=0 use=1
udp      17 77 src=172.17.48.2 dst=92.51.181.102 sport=29900 dport=27900 src=92.51.181.102 dst=192.168.1.100 sport=27900 dport=29900 [ASSURED] mark=0 use=1
udp      17 26 src=172.17.64.2 dst=92.51.181.102 sport=29900 dport=29910 [UNREPLIED] src=92.51.181.102 dst=192.168.1.100 sport=29910 dport=40589 mark=0 use=1
udp      17 106 src=92.51.149.13 dst=192.168.1.100 sport=58665 dport=29900 src=172.17.64.2 dst=92.51.149.13 sport=29900 dport=58665 [ASSURED] mark=0 use=1

# Delete the stale UDP conntrack entries from gameserver destined for BF2Hub master server
$ conntrack -D -p udp --orig-port-dst 27900
udp      17 24 src=172.17.64.2 dst=92.51.181.102 sport=29900 dport=27900 [UNREPLIED] src=92.51.181.102 dst=192.168.1.100 sport=27900 dport=40589 mark=0 use=1
udp      17 77 src=172.17.48.2 dst=92.51.181.102 sport=29900 dport=27900 src=92.51.181.102 dst=192.168.1.100 sport=27900 dport=29900 [ASSURED] mark=0 use=1
conntrack v1.4.5 (conntrack-tools): 2 flow entries have been deleted
$ conntrack -D -p udp --orig-port-dst 29910
udp      17 25 src=172.17.64.2 dst=92.51.181.102 sport=29900 dport=29910 [UNREPLIED] src=92.51.181.102 dst=192.168.1.100 sport=29910 dport=40589 mark=0 use=1
conntrack v1.4.5 (conntrack-tools): 1 flow entries have been deleted

# Delete the stale UDP conntrack entries from master listing server destined for gameserver
$ conntrack -D -p udp --orig-port-src 58665
udp      17 106 src=92.51.149.13 dst=192.168.1.100 sport=58665 dport=29900 src=172.17.64.2 dst=92.51.149.13 sport=29900 dport=58665 [ASSURED] mark=0 use=1
conntrack v1.4.5 (conntrack-tools): 1 flow entries have been deleted

# Get UDP conntrack entries
# Line 1: BF2 server talking with the BF2Hub cd key server. [UNREPLIED] is expected
# Line 2: BF2 server talking with the BF2Hub master server. It is now [ASSURED] which is expected
# Line 3: The master listing server talks with the BF2 server. [ASSURED] is expected
# Now we see that the new BF2 container IP (172.17.64.2) correctly talks with the BF2Hub master server, and our server is now listed
$ sudo conntrack -L -p udp | grep 92.51
udp      17 25 src=172.17.64.2 dst=92.51.181.102 sport=29900 dport=29910 [UNREPLIED] src=92.51.181.102 dst=192.168.1.100 sport=29910 dport=29900 mark=0 use=1
udp      17 114 src=172.17.64.2 dst=92.51.181.102 sport=29900 dport=27900 src=92.51.181.102 dst=192.168.1.100 sport=27900 dport=29900 [ASSURED] mark=0 use=1
udp      17 119 src=92.51.149.13 dst=192.168.1.100 sport=58665 dport=29900 src=172.17.64.2 dst=92.51.149.13 sport=29900 dport=58665 [ASSURED] mark=0 use=1

Q: Server not listed on master server on Kubernetes

A: If the pod is not running on hostNetwork: true, the Kubernetes Container Network Interface (CNI) is likely performing SNAT (via iptables POSTROUTING rules) on outgoing UDP packets from the gameserver pod, thereby changing the gameserver's source port(s).

The easy solution is to use hostNework: true for bf2 pods. However, this has security implications since the is running in the host's network namespace.

Better solutions:

Change the CNI configuration to perform SNAT while still preserving the outgoing port(s), for bf2 pods. However, not many CNIs offer this kind of customization.
Disable outgoing SNAT via the CNI configuration specifically for bf2 pods, so that the CNI does not create an iptables POSTROUTING table SNAT or MASQUERADE rule that mutates the gameserver outgoing traffic ports. Then manually create a POSTROUTING rule that preserves the UDP ports 16567 (sv.serverPort) and 29900 (sv.gameSpyPort), especially so for the sv.gameSpyPort which is responsible for talking with the gamespy master server, for example:
```
# This inserts two rules to the top of the POSTROUTING table, that performs outgoing SNAT while still preserving the outgoing UDP ports 16567 and 29900 for the bf2 server
iptables -t nat -I POSTROUTING 1 -p udp --sport=16567 -j MASQUERADE --to-ports=16567
iptables -t nat -I POSTROUTING 1 -p udp --sport=29900 -j MASQUERADE --to-ports=29900
```

To illustrate the problem:

Run the gameserver.

The tcpdump in the gameserver pod is generally good. The first outgoing packet's random outgoing UDP port 56631 is fine. The second outgoing packet's outgoing UDP port 29900 is correct. However as seen later on the host, both outgoing ports are randomized by the CNI. This second outgoing packet has created a conntrack entry mapping UDP port 10.0.1.2.29900 -> 92.51.181.102.27900 in the container to UDP port 192.168.1.100.58159 -> 92.51.181.102.27900 on the host. When the master server replies 92.51.181.102.27900 -> 192.168.1.100.29900 to the host, it cannot be mapped to 92.51.181.102.27900 -> 10.0.1.2.29900 in the pod because of the existing conntrack entry, so a new conntrack is created 92.51.181.102.1024 > 10.0.1.2.29900 with a wrong master server source port 1024. With a wrong master server source port, the gameserver cannot properly register itself with the master server:

# 92.51.181.102:27900 is BF2Hub master server
# 92.51.181.102:29910 is BF2Hub cdkey server
# 92.204.50.3 is the BF2Hub master listing server
# 192.168.1.100 is the kubernetes host machine's IP address
# 10.0.1.2:29900 is the bf2 pod's IP address and gamespy port

# In pod
$ tcpdump -p udp -n -A
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
12:54:28.995563 IP 10.0.1.2.56631 > 92.51.181.102.27900: UDP, length 18
E...2.@.@...
.&.\3.f.7l...B. ....battlefield2.
12:54:29.236465 IP 92.51.181.102.27900 > 10.0.1.2.56631: UDP, length 7
E..#....q./.\3.f
.&.l..7..kI..   ....
12:54:31.265344 IP 92.204.50.3.59171 > 10.0.1.2.29900: UDP, length 11
E..'e...q.$A\.2.
.&..#}...,Y...qYQU....
12:54:32.205484 IP 10.0.1.2.29900 > 92.51.181.102.27900: UDP, length 831
E..[3r@.@...
.&.\3.f}.l..GE.....zlocalip0.10.0.1.2.localport.29900.natneg.0.statechanged.3.gamename.battlefield2.hostname..gamename.battlefield2.gamever.1.5.3153-802.0.mapname..gametype..gamevariant..numplayers..maxplayers..gamemode.openplaying.password..timelimit..roundtime..hostport..bf2_dedicated..bf2_ranked..bf2_anticheat..bf2_os.linux-64.bf2_autorec..bf2_d_idx..bf2_d_dl..bf2_voip..bf2_autobalanced..bf2_friendlyfire..bf2_tkmode..bf2_startdelay..bf2_spawntime..bf2_sponsortext..bf2_sponsorlogo_url..bf2_communitylogo_url..bf2_scorelimit..bf2_ticketratio..bf2_teamratio..bf2_team1..bf2_team2..bf2_bots..bf2_pure..bf2_mapsize..bf2_globalunlocks..bf2_fps.34.000000.bf2_plasma..bf2_reservedslots..bf2_coopbotratio..bf2_coopbotcount..bf2_coopbotdiff..bf2_novehicles.....player_.score_.ping_.team_.deaths_.pid_.skill_.AIBot_....team_t.score_t..MEC.0.EU.0.
12:54:32.205709 IP 10.0.1.2.29900 > 92.204.50.3.59171: UDP, length 777
E..%q.@.@..b
.&.\.2.}..#.....qYQUsplitnum...hostname..gamename.battlefield2.gamever.1.5.3153-802.0.mapname..gametype..gamevariant..numplayers..maxplayers..gamemode.openplaying.password..timelimit..roundtime..hostport..bf2_dedicated..bf2_ranked..bf2_anticheat..bf2_os.linux-64.bf2_autorec..bf2_d_idx..bf2_d_dl..bf2_voip..bf2_autobalanced..bf2_friendlyfire..bf2_tkmode..bf2_startdelay..bf2_spawntime..bf2_sponsortext..bf2_sponsorlogo_url..bf2_communitylogo_url..bf2_scorelimit..bf2_ticketratio..bf2_teamratio..bf2_team1..bf2_team2..bf2_bots..bf2_pure..bf2_mapsize..bf2_globalunlocks..bf2_fps.34.000000.bf2_plasma..bf2_reservedslots..bf2_coopbotratio..bf2_coopbotcount..bf2_coopbotdiff..bf2_novehicles....player_...score_...ping_...team_...deaths_...pid_...skill_...AIBot_.....team_t..MEC.EU..score_t..0.0...
12:54:32.447508 IP 92.51.181.102.1024 > 10.0.1.2.29900: UDP, length 28
E..8....r...\3.f
.&...}..$.V......z7sv"3i00B48153267D01.
12:54:32.448025 IP 10.0.1.2.29900 > 92.51.181.102.1024: UDP, length 34
E..>3.@.@...
.&.\3.f}....*B.....zlTE1YLS3GwjGfT+6atCy/gxSSAQA.
12:54:32.688665 IP 92.51.181.102.1024 > 10.0.1.2.29900: UDP, length 7
E..#....r...\3.f
.&...}.......
...z
12:54:51.526895 IP 92.204.50.3.59171 > 10.0.1.2.29900: UDP, length 7
E..#f...q.$>\.2.
.&..#}....]..   cwbI
12:54:51.547225 IP 10.0.1.2.29900 > 92.204.50.3.59171: UDP, length 7
E..#|R@.@...
.&.\.2.}..#.... cwbI0.

The tcpdump on the kubernetes host is generally good. The first random outgoing packet's UDP port 6127 is fine. But the second random outgoing packet's UDP port 58159:

# On host
$ tcpdump -p udp -n -A
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
12:54:28.995659 IP 192.168.1.100.6127 > 92.51.181.102.27900: UDP, length 18
E...2.@.?.60....\3.f..l....1	....battlefield2.
12:54:29.236405 IP 92.51.181.102.27900 > 192.168.1.100.6127: UDP, length 7
E..#....r..?\3.f....l.........	...............
12:54:31.265287 IP 92.204.50.3.59171 > 192.168.1.100.29900: UDP, length 11
E..'e...r...\.2......#}........qYQU...........
12:54:32.205551 IP 192.168.1.100.58159 > 92.51.181.102.27900: UDP, length 831
E..[3r@.?.2.....\3.f./l..G.^....zlocalip0.10.0.1.2.localport.29900.natneg.0.statechanged.3.gamename.battlefield2.hostname..gamename.battlefield2.gamever.1.5.3153-802.0.mapname..gametype..gamevariant..numplayers..maxplayers..gamemode.openplaying.password..timelimit..roundtime..hostport..bf2_dedicated..bf2_ranked..bf2_anticheat..bf2_os.linux-64.bf2_autorec..bf2_d_idx..bf2_d_dl..bf2_voip..bf2_autobalanced..bf2_friendlyfire..bf2_tkmode..bf2_startdelay..bf2_spawntime..bf2_sponsortext..bf2_sponsorlogo_url..bf2_communitylogo_url..bf2_scorelimit..bf2_ticketratio..bf2_teamratio..bf2_team1..bf2_team2..bf2_bots..bf2_pure..bf2_mapsize..bf2_globalunlocks..bf2_fps.34.000000.bf2_plasma..bf2_reservedslots..bf2_coopbotratio..bf2_coopbotcount..bf2_coopbotdiff..bf2_novehicles.....player_.score_.ping_.team_.deaths_.pid_.skill_.AIBot_....team_t.score_t..MEC.0.EU.0.
12:54:32.205718 IP 192.168.1.100.29900 > 92.204.50.3.59171: UDP, length 777
E..%q.@.?.v.....\.2.}..#..S^.qYQUsplitnum...hostname..gamename.battlefield2.gamever.1.5.3153-802.0.mapname..gametype..gamevariant..numplayers..maxplayers..gamemode.openplaying.password..timelimit..roundtime..hostport..bf2_dedicated..bf2_ranked..bf2_anticheat..bf2_os.linux-64.bf2_autorec..bf2_d_idx..bf2_d_dl..bf2_voip..bf2_autobalanced..bf2_friendlyfire..bf2_tkmode..bf2_startdelay..bf2_spawntime..bf2_sponsortext..bf2_sponsorlogo_url..bf2_communitylogo_url..bf2_scorelimit..bf2_ticketratio..bf2_teamratio..bf2_team1..bf2_team2..bf2_bots..bf2_pure..bf2_mapsize..bf2_globalunlocks..bf2_fps.34.000000.bf2_plasma..bf2_reservedslots..bf2_coopbotratio..bf2_coopbotcount..bf2_coopbotdiff..bf2_novehicles....player_...score_...ping_...team_...deaths_...pid_...skill_...AIBot_.....team_t..MEC.EU..score_t..0.0...
12:54:32.447422 IP 92.51.181.102.27900 > 192.168.1.100.29900: UDP, length 28
E..8....s..)\3.f....l.}..$........z7sv"3i00B48153267D01.
12:54:32.448042 IP 192.168.1.100.29900 > 92.51.181.102.27900: UDP, length 34
E..>3.@.?.5.....\3.f}.l..*.A....zlTE1YLS3GwjGfT+6atCy/gxSSAQA.
12:54:32.688615 IP 92.51.181.102.27900 > 192.168.1.100.29900: UDP, length 7
E..#....s..=\3.f....l.}....,..
...z...........
12:54:51.526835 IP 92.204.50.3.59171 > 192.168.1.100.29900: UDP, length 7
E..#f...r...\.2......#}.......	cwbI...........
12:54:51.547273 IP 192.168.1.100.29900 > 92.204.50.3.59171: UDP, length 7
E..#|R@.?.o<....\.2.}..#..P\	cwbI0.

The conntrack table is generally good, except there is an invalid destination port dport=1024 to the master server from inside the gameserver pod, as explained earlier:

# Line 2: BF2 server talking with the BF2Hub cd key server. [UNREPLIED] is expected
# Line 1: BF2 server talking with the BF2Hub master server. It is now [ASSURED] which is expected. However, the master server source port should be 27900 instead of 1024
# Line 3: The master listing server talks with the BF2 server. [ASSURED] is expected
$ conntrack -L -p udp | grep 29900
udp      17 21 src=10.0.1.2 dst=92.51.181.102 sport=32001 dport=29910 [UNREPLIED] src=92.51.181.102 dst=192.168.0.196 sport=29910 dport=32001 mark=0 use=1
udp      17 89 src=92.51.181.102 dst=192.168.1.100 sport=27900 dport=29900 src=10.0.1.2 dst=92.51.181.102 sport=29900 dport=1024 [ASSURED] mark=0 use=1
udp      17 175 src=92.204.50.3 dst=192.168.1.100 sport=59171 dport=29900 src=10.0.1.2 dst=92.204.50.3 sport=29900 dport=59171 [ASSURED] mark=0 use=1

The cause is a CNI (calico in this case) iptables POSTROUTING MASQUERADE rule which randomizes the source port(s) of the gameserver pod's outgoing traffic:

$ iptables -t nat -L POSTROUTING -nv
Chain POSTROUTING (policy ACCEPT 95 packets, 6144 bytes)
 pkts bytes target     prot opt in     out     source               destination
2059K  130M cali-POSTROUTING  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* cali:O3lYWMrLQYEMJtB5 */
2908K  184M CNI-HOSTPORT-MASQ  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* CNI portfwd requiring masquerade */
2909K  184M KUBE-POSTROUTING  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* kubernetes postrouting rules */
    0     0 MASQUERADE  all  --  *      !docker0  172.17.0.0/16        0.0.0.0/0

$ iptables -t nat -S |grep -E 'MASQUERADE|SNAT'
-A cali-nat-outgoing -m comment --comment "cali:5nyjfg7Yyt12dDfu" -m set --match-set cali40masq-ipam-pools src -m set ! --match-set cali40all-ipam-pools dst -j MASQUERADE --random-fully

Hence, the gameserver is not listed on the master server.

To illustrate the solution:

The solution is to insert two rules into the iptables POSTROUTING table:

# This inserts two rules at the top of the POSTROUTING table, that performs outgoing SNAT while still preserving the outgoing UDP port(s) 16567 and 29900 for the bf2 server
iptables -t nat -I POSTROUTING 1 -p udp --sport=16567 -j MASQUERADE --to-ports=16567
iptables -t nat -I POSTROUTING 1 -p udp --sport=29900 -j MASQUERADE --to-ports=29900

$ iptables -t nat -L POSTROUTING -nv
Chain POSTROUTING (policy ACCEPT 95 packets, 6144 bytes)
 pkts bytes target     prot opt in     out     source               destination
 0    96 MASQUERADE  udp  --  *      *       0.0.0.0/0            0.0.0.0/0            udp spt:16567 masq ports: 16567
 0   195 MASQUERADE  udp  --  *      *       0.0.0.0/0            0.0.0.0/0            udp spt:29900 masq ports: 29900
2059K  130M cali-POSTROUTING  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* cali:O3lYWMrLQYEMJtB5 */
2908K  184M CNI-HOSTPORT-MASQ  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* CNI portfwd requiring masquerade */
2909K  184M KUBE-POSTROUTING  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* kubernetes postrouting rules */
    0     0 MASQUERADE  all  --  *      !docker0  172.17.0.0/16        0.0.0.0/0

Run the gameserver.

The tcpdump in the gameserver pod is good. The first random outgoing packet's UDP port 43085 is fine. The second outgoing packet's outgoing UDP port 29900 is correct. Master server replies on the correct UDP source port 27900:

# 92.51.181.102:27900 is BF2Hub master server
# 92.51.181.102:29910 is BF2Hub cdkey server
# 92.204.50.3 is the BF2Hub master listing server
# 192.168.1.100 is the kubernetes host machine's IP address
# 10.0.1.2:29900 is the bf2 pod's IP address and gamespy port

# In pod
$ tcpdump -p udp -n -A
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
13:10:51.284905 IP 10.0.1.2.43085 > 92.51.181.102.27900: UDP, length 18
E....3@.@.JS
...\3.f.Ml....d ....battlefield2.
13:10:51.522886 IP 92.51.181.102.27900 > 10.0.1.2.43085: UDP, length 7
E..#....r..     \3.f
...l..M.. O..   ....
13:10:51.908569 IP 92.204.50.3.59171 > 10.0.1.2.29900: UDP, length 11
E..'g!..q..6\.2.
....#}........oxGS....
13:10:54.088919 IP 10.0.1.2.29900 > 92.51.181.102.27900: UDP, length 831
E..[0.@.@.D.
...\3.f}.l..G...T...localip0.10.0.1.2.localport.29900.natneg.0.statechanged.3.gamename.battlefield2.hostname..gamename.battlefield2.gamever.1.5.3153-802.0.mapname..gametype..gamevariant..numplayers..maxplayers..gamemode.openplaying.password..timelimit..roundtime..hostport..bf2_dedicated..bf2_ranked..bf2_anticheat..bf2_os.linux-64.bf2_autorec..bf2_d_idx..bf2_d_dl..bf2_voip..bf2_autobalanced..bf2_friendlyfire..bf2_tkmode..bf2_startdelay..bf2_spawntime..bf2_sponsortext..bf2_sponsorlogo_url..bf2_communitylogo_url..bf2_scorelimit..bf2_ticketratio..bf2_teamratio..bf2_team1..bf2_team2..bf2_bots..bf2_pure..bf2_mapsize..bf2_globalunlocks..bf2_fps.39.000000.bf2_plasma..bf2_reservedslots..bf2_coopbotratio..bf2_coopbotcount..bf2_coopbotdiff..bf2_novehicles.....player_.score_.ping_.team_.deaths_.pid_.skill_.AIBot_....team_t.score_t..CH.0.US.0.
13:10:54.089237 IP 10.0.1.2.29900 > 92.204.50.3.59171: UDP, length 776
E..$6.@.@...
...\.2.}..#..B..oxGSsplitnum...hostname..gamename.battlefield2.gamever.1.5.3153-802.0.mapname..gametype..gamevariant..numplayers..maxplayers..gamemode.openplaying.password..timelimit..roundtime..hostport..bf2_dedicated..bf2_ranked..bf2_anticheat..bf2_os.linux-64.bf2_autorec..bf2_d_idx..bf2_d_dl..bf2_voip..bf2_autobalanced..bf2_friendlyfire..bf2_tkmode..bf2_startdelay..bf2_spawntime..bf2_sponsortext..bf2_sponsorlogo_url..bf2_communitylogo_url..bf2_scorelimit..bf2_ticketratio..bf2_teamratio..bf2_team1..bf2_team2..bf2_bots..bf2_pure..bf2_mapsize..bf2_globalunlocks..bf2_fps.39.000000.bf2_plasma..bf2_reservedslots..bf2_coopbotratio..bf2_coopbotcount..bf2_coopbotdiff..bf2_novehicles....player_...score_...ping_...team_...deaths_...pid_...skill_...AIBot_.....team_t..CH.US..score_t..0.0...
13:10:54.330283 IP 92.51.181.102.27900 > 10.0.1.2.29900: UDP, length 28
E..8....r...\3.f
...l.}..$]....T...|#G2,l00B48153267D01.
13:10:54.348646 IP 10.0.1.2.29900 > 92.51.181.102.27900: UDP, length 34
E..>0.@.@.G.
...\3.f}.l..*.t.T...+ozUhb51x7cpIi+xhCLoE4MXga0A.
13:10:54.589484 IP 92.51.181.102.27900 > 10.0.1.2.29900: UDP, length 7
E..#....r...\3.f
...l.}....f..
T...
13:11:12.739887 IP 92.204.50.3.59171 > 10.0.1.2.29900: UDP, length 7
E..#g'..q..4\.2.
....#}.......   2TRR
13:11:12.748529 IP 10.0.1.2.29900 > 92.204.50.3.59171: UDP, length 7
E..#;(@.@..3
...\.2.}..#..?. 2TRR0.

The tcpdump on the kubernetes host is good. The first random outgoing packet's UDP port 43085 is fine. The second outgoing packet's outgoing UDP port 29900 is correct. Master server replies on the correct UDP source port 27900:

# On host
$ tcpdump -p udp -n -A
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
13:10:51.284977 IP 192.168.1.100.43085 > 92.51.181.102.27900: UDP, length 18
E....3@.?.:.....\3.f.Ml....1	....battlefield2.
13:10:51.522815 IP 92.51.181.102.27900 > 192.168.1.100.43085: UDP, length 7
E..#....s..<\3.f....l..M......	...............
13:10:51.908344 IP 92.204.50.3.59171 > 192.168.1.100.29900: UDP, length 11
E..'g!..r..i\.2......#}...~....oxGS...........
13:10:54.088984 IP 192.168.1.100.29900 > 92.51.181.102.27900: UDP, length 831
E..[0.@.?.5.....\3.f}.l..G.^.T...localip0.10.0.1.2.localport.29900.natneg.0.statechanged.3.gamename.battlefield2.hostname..gamename.battlefield2.gamever.1.5.3153-802.0.mapname..gametype..gamevariant..numplayers..maxplayers..gamemode.openplaying.password..timelimit..roundtime..hostport..bf2_dedicated..bf2_ranked..bf2_anticheat..bf2_os.linux-64.bf2_autorec..bf2_d_idx..bf2_d_dl..bf2_voip..bf2_autobalanced..bf2_friendlyfire..bf2_tkmode..bf2_startdelay..bf2_spawntime..bf2_sponsortext..bf2_sponsorlogo_url..bf2_communitylogo_url..bf2_scorelimit..bf2_ticketratio..bf2_teamratio..bf2_team1..bf2_team2..bf2_bots..bf2_pure..bf2_mapsize..bf2_globalunlocks..bf2_fps.39.000000.bf2_plasma..bf2_reservedslots..bf2_coopbotratio..bf2_coopbotcount..bf2_coopbotdiff..bf2_novehicles.....player_.score_.ping_.team_.deaths_.pid_.skill_.AIBot_....team_t.score_t..CH.0.US.0.
13:10:54.089261 IP 192.168.1.100.29900 > 92.204.50.3.59171: UDP, length 776
E..$6.@.?.......\.2.}..#..S].oxGSsplitnum...hostname..gamename.battlefield2.gamever.1.5.3153-802.0.mapname..gametype..gamevariant..numplayers..maxplayers..gamemode.openplaying.password..timelimit..roundtime..hostport..bf2_dedicated..bf2_ranked..bf2_anticheat..bf2_os.linux-64.bf2_autorec..bf2_d_idx..bf2_d_dl..bf2_voip..bf2_autobalanced..bf2_friendlyfire..bf2_tkmode..bf2_startdelay..bf2_spawntime..bf2_sponsortext..bf2_sponsorlogo_url..bf2_communitylogo_url..bf2_scorelimit..bf2_ticketratio..bf2_teamratio..bf2_team1..bf2_team2..bf2_bots..bf2_pure..bf2_mapsize..bf2_globalunlocks..bf2_fps.39.000000.bf2_plasma..bf2_reservedslots..bf2_coopbotratio..bf2_coopbotcount..bf2_coopbotdiff..bf2_novehicles....player_...score_...ping_...team_...deaths_...pid_...skill_...AIBot_.....team_t..CH.US..score_t..0.0...
13:10:54.330094 IP 92.51.181.102.27900 > 192.168.1.100.29900: UDP, length 28
E..8....s..&\3.f....l.}..$M....T...|#G2,l00B48153267D01.
13:10:54.348692 IP 192.168.1.100.29900 > 92.51.181.102.27900: UDP, length 34
E..>0.@.?.7.....\3.f}.l..*.A.T...+ozUhb51x7cpIi+xhCLoE4MXga0A.
13:10:54.589366 IP 92.51.181.102.27900 > 192.168.1.100.29900: UDP, length 7
E..#....s..:\3.f....l.}...z...
T..............
13:11:12.739834 IP 92.204.50.3.59171 > 192.168.1.100.29900: UDP, length 7
E..#g'..r..g\.2......#}.......	2TRR...........
13:11:12.748565 IP 192.168.1.100.29900 > 92.204.50.3.59171: UDP, length 7
E..#;(@.?..f....\.2.}..#..P\	2TRR0.
13:11:14.112726 IP 192.168.1.100.29900 > 92.51.181.102.27900: UDP, length 5
E..!=.@.?.+.....\3.f}.l....$.T...
13:11:14.113853 IP 192.168.1.100.29900 > 92.51.181.102.29910: UDP, length 4
E.. =.@.?.+.....\3.f}.t....#;
.9

The conntrack table is good, with source ports UDP 29900 preserved:

$ conntrack -L -p udp | grep 29900
# Line 1: BF2 server talking with the BF2Hub cd key server. [UNREPLIED] is expected
# Line 2: BF2 server talking with the BF2Hub master server. It is now [ASSURED] which is expected
# Line 3: The master listing server talks with the BF2 server. [ASSURED] is expected
udp      17 21 src=10.0.1.2 dst=92.51.181.102 sport=29900 dport=29910 [UNREPLIED] src=92.51.181.102 dst=192.168.1.100 sport=29910 dport=29900 mark=0 use=1
udp      17 173 src=92.204.50.3 dst=192.168.1.100 sport=59171 dport=29900 src=10.0.1.2 dst=92.204.50.3 sport=29900 dport=59171 [ASSURED] mark=0 use=1
udp      17 171 src=10.0.1.2 dst=92.51.181.102 sport=29900 dport=27900 src=92.51.181.102 dst=192.168.1.100 sport=27900 dport=29900 [ASSURED] mark=0 use=1

The gameserver is listed on the master server.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

usage.md

usage.md

Usage

BF2

BF2 with BF2Statistics 2.x.x

BF2 with BF2Statistics 3.x.x

AIX 2.0 mod

BF2All64 mod

Forgotten Hope 2 mod

DNS spoofing

DNS spoofing: Background

DNS spoofing: for server to be listed on BF2Hub master server

DNS spoofing: for server to be listed on PRMasterServer master server

DNS spoofing: for server to send stats snapshots to BF2Statistics 2.x.x

DNS spoofing: for server to send stats snapshots to BF2Statistics 3.x.x

ESAI

FAQ

Q: Server not listed on master server

Q: Server not listed on master server after `docker-compose down && docker-compose up`

Q: Server not listed on master server on Kubernetes

Files

usage.md

Latest commit

History

usage.md

File metadata and controls

Usage

BF2

BF2 with BF2Statistics 2.x.x

BF2 with BF2Statistics 3.x.x

AIX 2.0 mod

BF2All64 mod

Forgotten Hope 2 mod

DNS spoofing

DNS spoofing: Background

DNS spoofing: for server to be listed on BF2Hub master server

DNS spoofing: for server to be listed on PRMasterServer master server

DNS spoofing: for server to send stats snapshots to BF2Statistics 2.x.x

DNS spoofing: for server to send stats snapshots to BF2Statistics 3.x.x

ESAI

FAQ

Q: Server not listed on master server

Q: Server not listed on master server after docker-compose down && docker-compose up

Q: Server not listed on master server on Kubernetes

Q: Server not listed on master server after `docker-compose down && docker-compose up`