Server List - Multi NIC Server

Discussion in 'Rust Discussion' started by [FPSPlayers]Colin M, May 31, 2015.

  1. [FPSPlayers]Colin M

    [FPSPlayers]Colin M

    I figured I would post this here because the support from Facepunch in terms of documentation is pretty terrible.

    So I have a server in my house which has two active NIC's where the second NIC is the First NIC IP+1, so x.x.x.250 & x.x.x.251 - earlier today I was no longer able to connect using my domain name & port which is configured on my router to point directly to x.x.x.250, so I changed the ports and set them on to the x.x.x.251 NIC which then worked and actually put the server up on the multi-player browser list after weeks of not being listed when I had the x.x.x.250 address forwarded.

    The problem was that while the x.x.x.251 address worked for me, it did not work for anyone else; so I set the forward back to the x.x.x.250 address so now everybody can connect using the client.connect DOMAIN_NAME:pORT prefix, the server still shows up in the list for me now under Modded & History, however players are reporting that they cannot find the server on the list regardless of the Search function or even looking at the History tab for the server itself, all ports are forwarded via Windows Firewall & the router on my network.

    Is there a way specifically to bind the Rust Server to an IP address?
     
    [FPSPlayers]Colin M, May 31, 2015
    #1
  2. Wulf

    Wulf Community Admin

    Use +server.ip x.x.x.x in your startup script or command-line. Keep in mind that this won't work behind a router, so you may need to use 0.0.0.0 instead. If you are local to the server, you should always be able to connect, as routers generally loop you back to yourself when using the external IP inside the network. If users still can't connect

    Also keep in mind that the Rust server list only shows 200 servers total per tab.
     
    Wulf, May 31, 2015
    #2
  3. [FPSPlayers]Colin M

    [FPSPlayers]Colin M

    Will check out the +server.ip parameter next. I'm local to the server and was able to connect only when I went from "client.connect x.x.x.250" to "client.connect x.x.x.251" which is pretty strange - this was all done WITHOUT the +server.ip parameter defined

    [Update]
    Added +server.ip parameter, seems alright now - although it is a different player connecting who found it easier.
     
    Last edited by a moderator: Jun 1, 2015
    [FPSPlayers]Colin M, May 31, 2015
    #3