Rust RCON not binding to specific IP

Hi,

We seem to be having a bit of trouble making Rust rcon bind to a specific IP. It just listens on all IPs:

Code:

root@server:~# netstat -tulnp | grep 28016
tcp        0      0 0.0.0.0:28016           0.0.0.0:*               LISTEN      20938/RustDedicated

This is the command line:
-batchmode +server.maxplayers 50 +server.ip 178.33.38.xx +server.port 28015 +rcon.web 1 +rcon.ip 178.33.38.xx +rcon.port 28018 +rcon.password "XXXX" -logfile "log.txt"

Anyone know why it won't work? We've also tried setting rcon.ip in the cfg.

It's kind of a problem since we use TCAdmin to host servers, and all rcon ports should be the same.

 

i use tcadmin aswell, but i do not use the rcon.ip Command. try to remove it, never heard of such command. as tcadmin has stated the Ip in the Service settings.

 

Yeah, but the Rcon IP isn't specified anywhere in TCAdmin. TCAdmin doesn't tell the game server to run on a specific IP unless you tell it to.

 

Look in the command line.

 

I never used and rcon ip, only an rcon port, and rcon works just fine,

I will send you my command line when i am back home,

 

Hmm, this is odd. It seems like it's actually working on services that aren't running +rcon.web 1

Code:

./RustDedicated -batchmode +server.maxplayers 50 +server.ip 176.31.21.146 +server.port 28015 +rcon.ip 176.31.21.146 +rcon.port 28017 +rcon.password "4o6itt" -logfile "log.txt"

binds to the specified port, but

Code:

./RustDedicated -batchmode +server.maxplayers 50 +server.ip 176.31.21.146 +server.port 28015 +rcon.web 1 +rcon.ip 176.31.21.146 +rcon.port 28017 +rcon.password "4o6itt" -logfile "log.txt"

binds to all ports. How come? Bug or is this the intended purpose?

 

When I put web recon to 1 on my server I'm no longer able to use rustadmin on my iPad but I can on my pic. Not sure why but I always set it to 0
[DOUBLEPOST=1482575132][/DOUBLEPOST]Are you sure your server is updated by the way.

 

It's a new form of rcon protocol for Rust. The "experimental" rcon protocol will not keep being supported AFAIK, so we've started using the websocket rocn protocol.

 

Hmm ok.

 

I've created an issue for this on GitHub as it seems like a bug