1. I have set up a new server today and shutdown the old machine. The new machine is in my work's server room. The way that the network is setup is that my machine has ip xxx.xxx.214.144, but to connect to it, you have to do client.connect xxx.xxx.214.145:28015, because the NAT is configured to translate all incoming connections securely from the xxx.xxx.214.145 address to the xxx.xxx.214.144 address. With this in mind, the ports are forwarded for the 214.145 address, since that's the IP that accepts incoming connections. (No, don't tell me to change the way this is configured, I won't do it and neither the other network admins will).

    Now the problem is, the players can connect fine by doing client.connect xxx.xxx.214.145:28015 on the console, BUT the server does not show on the server browser in-game, nor the live-map shows up in the list on playrust.io. HOWEVER, I can access the livemap for my server if I manually type the IP of it in the bar: http://map.playrust.io/?xxx.xxx.214.145.

    So no issue, just one huge annoyance. Is there a way to make the server appear on the list in-game and on the livemap list on the website, without changing my network configurations?
     
  2. Wulf

    Wulf Community Admin

    For the Rust server list issue, each list is limited to 200 servers total shown at one time, so it's possible that you may never see it on there unless you search or use a creative name.

    For the map, make sure you have TCP port 28015 open on your router or with your host, that's what Rust:IO uses.
     
  3. All ports are open, DMZed, and I never had trouble searching my old server by name. If the port wasn't open, people wouldn't be able to connect to the server. What I'm trying to say is that the machine IP is xxx.144, but players connect through xxx.145 which translates the incoming connections to xxx.144, however, RustIO and Rust don't deal with the issue where NAT makes so that incoming connections from one IP are translated to another and that outgoing connections are detected from the right IP address.
     
  4. Wulf

    Wulf Community Admin

    Rust uses UDP, the map uses TCP, not the same thing. Make sure your server's port is open for TCP.
     
  5. All ports are open, port forwarding is not an issue. I mentioned that on the first post.
    [DOUBLEPOST=1436131557][/DOUBLEPOST]Also, the issue is not solved, the problem IS NOT with port forwarding, the problem is that Rust and RustIO don't properly handle servers that have NAT configured to translate incoming connections from one IP to another.
     
  6. I can remember that with Nat i had to set the rust server.ip via plugin/after startup to the real external ip (empty/no server.ip set via commandline)...
    Used this simple plugin(updated it to current rust):
    Code:
    PLUGIN.Title = "ServerIP"
    PLUGIN.Description = "Sets Server IP after start if empty"
    PLUGIN.Author = "Nogrod"
    PLUGIN.Version = V(1, 0, 0)
    PLUGIN.HasConfig = truefunction PLUGIN:Init()
        self.Config.Settings = self.Config.Settings or {}
        self.Config.Settings.IP = self.Config.Settings.IP or ""
        self:SaveConfig()
    endfunction PLUGIN:OnServerInitialized()
        if (ConVar.Server.ip == "") then
            global.ConsoleSystem.Run.Server:Normal("server.ip " .. self.Config.Settings.IP)
        end
    end
     
  7. This is the kind of attempt to solve the problem I'm looking for, thank you good sir! I will try it and report the outcome!
    [DOUBLEPOST=1436134666][/DOUBLEPOST]Edit: When I reloaded RustIO, it said that my address is "not valid in its context". I think there is an issue with the way Rust does IP bindings.
     
  8. Wulf

    Wulf Community Admin

    I'm sorry, but you can't set your server.ip to an IP address that isn't assigned to your computer, you can only use your local IP address assigned to your computer via your router, or 0.0.0.0. Ex. 10.0.1.10, 192.168.1.100, or 0.0.0.0 would be the only acceptable IP addresses generally in a home network setup.
     
  9. So the server.ip command can only be set to local IPs?
     
  10. Wulf

    Wulf Community Admin

    It can only be set to IP addresses that your computer has assigned to it, IP addresses that it is able to bind to. Your external/public IP address that your modem has assigned to you router is not one of those.
     
  11. I use this plugin for my windows vbox on my debian server which uses nat. local ip is 10.0.1.x with this plugin the ip is set to the external ip of the debian server and the rust server is listed an can be joined without issues. It doesn't set the bind ip since it is already bound on boot.
     
  12. Wulf

    Wulf Community Admin

    I was wondering how that'd work, but it generally shouldn't be an issue. Have you tested to see if it's needed in the past few months?
     
  13. The problem isn't that people can't join. Infact, people are able to join the server easily. They just have to use client.connect IP:pORT, the issue is that the server does not display on the list, and that can be annoying to have to copy and paste the IP every time you want to join the server.
     
  14. Wulf

    Wulf Community Admin

    Did you get the live map working? The live map not showing on the list is 99% of the time because the playrust.io site cannot see your TCP port as being open. The Rust server list is generally still because it's limited. Can you see your server on any of the other lists such as Friends, History, etc?
     
  15. It was needed to get the server on the list while using nat. Havn't checked if it's still working/needed.
     
  16. Btw, the live map DOES work, however, to access it, you have to type the external IP of the machine manually into the address bar. This is the server btw: http://map.playrust.io/?65.51.214.145

    That's the external IP of the NAT that's translating to the 214.144 address. You can see everyone on the map and such, but if you were to type the name of the server on the search bar, you would not find it. It doesn't display on the list because of the way NAT is configured.
     
  17. Wulf

    Wulf Community Admin

    The map is not accessible for me, it may only work for you locally.
     
  18. It should be. Also, I am not locally connected to it. I am 3 US states away from the server. Other players on the server are also able to use the map.
     
  19. Wulf

    Wulf Community Admin

    It's showing now, but it was unresponsive earlier. I might have caught it during a restart? It sounds like your only issue right now then is the in-game server list, but I'd recommend seeing if you can get to it via Friends, etc for it to show in your history, or try searching for it by name.
     
  20. The thing is, it works, but I want to be able to find it by typing the name on the list. Which is the only problem with the livemap. For some reason the livemap works but it doesn't show on the list. The exact same thing with the server in the in-game server list.