Hey Guys,
there seems to be a problem with the ip binding when oxide is activated.
We tested it without oxide

Here two screenshots when oxide is active! then the rcon port is bound to 0.0.0.0



when oxide is not activ on the gameserver its bound to the "rcon.ip" we set in the cmd line


is this an known issue and can be fixed :) ?

You may disable oxide rcon in /oxide/oxide.config.json afaik, or enable it.

we dont want to disable it just to ask why the ip binding is not working correctly if there is someone aware or it is wished like this to bind it to 0.0.0.0

No, oxide rcon can be disabled since rust has its own. Also, 0.0.0.0 has a couple of different meanings, but in this context, when a server is told to listen on 0.0.0.0 that means "listen on every available network interface".

hey yes we know about the 0.0.0.0 meaning but we working with some cleanup routines what is not allowing binding on 0.0.0.0 thats why we dont want to use this ok but thanks! for the information how to disable it!