This page explains what the -multihome launch parameter does, when it should be used, and why it is usually a bad idea to set it incorrectly.
.\StarRuptureServerEOS.exe -Log -port=7777 -multihome=192.168.1.50
In this example, the dedicated server will only listen on the local LAN IP address 192.168.1.50.
The -multihome parameter forces the server to bind to one specific local network interface (IP address).
Without -multihome, the server binds to:
0.0.0.0 (all available network interfaces)
This default behavior is recommended for most users.
A very common mistake is setting -multihome to your public (WAN) IP address, for example:
-multihome=203.0.113.42
This can result in:
Port forwarding already handles WAN → LAN traffic.
-multihomeshould never be used to configure a public IP address.
-multihome should only be used when a single server has multiple local IP addresses or network connections.
Example:
-multihome=192.168.10.25
This restricts the server to listening only on that LAN IP.
If you only have one LAN IP, -multihome provides no benefit and increases the chance of misconfiguration.
.\StarRuptureServerEOS.exe -Log -port=7777
✔ Works with port forwarding
✔ Automatically binds to the correct interface
✔ Lowest chance of networking issues
.\StarRuptureServerEOS.exe -Log -port=7777 -multihome=LAN_IP_ADDRESS
✔ Use only if multiple LAN IPs exist
✔ Never use a WAN / public IP
-multihome does not open ports-multihome does not improve performance-multihome should never be set to a WAN IP-multihome is only for restricting which local LAN IP the server listens onIf you don’t know why you need
-multihome, you probably don’t need it.