Page MenuHomeFeedback Tracker

Steam browser picks up on wrong IP, so impossible to join server
Closed, ResolvedPublic


The steam browser appears to pick up on the base IP of the server box, rather than the IP that the Arma server is running on. When this happens it is impossible to join the server via the steam browser.

This still happens in 1.18


Legacy ID
Server Browser Steam
Steps To Reproduce

Start a server onan IP other than the base one for the box and try and connect via the steam browser, either in-game or out of game

Event Timeline

Bravo17 edited Steps To Reproduce. (Show Details)May 1 2014, 4:50 AM
Bravo17 edited Additional Information. (Show Details)
Bravo17 set Category to Server Browser Steam.
Bravo17 set Reproducibility to Always.
Bravo17 set Severity to None.
Bravo17 set Resolution to Fixed.
Bravo17 set Legacy ID to 2329542924.May 7 2016, 6:32 PM

Hello, could you post a little bit more details about the problem? You mean the Steam server pick up local IP instead of public WAN address? Or you have multiple LAN cards and it picks up the wrong one?

Bravo17 added a subscriber: Bravo17.May 7 2016, 6:32 PM

One LAN card with multiple IPs associated with it. This is how most clans dedicated server boxes will be set up.

we have a IP assignment, so the addresses available on the box for use are 114 (the primary or base IP) through 126.

The Arma 3 server is on 116, but the out of game steam browser shows it as being on 114. I assume that the in-game one also has it on 114, but it doesn't seem to show the IP anywhere.

we have on the command line.

I've adjusted a Steam server initialization, the -ip= param is passed to the Steam to force it to use this interface.

r. 124227

Great! Thank you.

Which version will this be available in?

It will be in dev build, the version of the game has to be greater than 1.19.124227

Can someone please test it and confirm that the fix is working?

I'm away from home at the moment, but I will see what I can do.

Resolved according CL.

zind added a subscriber: zind.May 7 2016, 6:32 PM
zind added a comment.May 13 2014, 1:25 AM

When will the fix be in the stable release?

Fixed in 1.20 stable

MadDogX added a subscriber: MadDogX.May 7 2016, 6:32 PM

Mass closing tickets marked as resolved more than 1 month ago.

If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.