Ports 21 and 22 are open but the rest are not.

[astronovaval]

Ports 21 and 22 are open just fine. I add ports 28015, 28016 and 28083 along side 21 and 22 but the 280XX arent opening, this is for setting up a Rust Dedicated Game Server.

[KeithFrench]

In ss the UDP state is unconnected, listen is only for TCP connections.

[astronovaval]

still nope, i feel like any udp port i allow is just always closed, and the tcp ports are working fine. 

[KeithFrench]

I have just found the socket statistics command in linux, it might help:-

sudo ss -tulpn

[astronovaval]

I'm going to try use port 28013 and 28014 after forwarding and allowing them on gufw. ill let you know how it goes.

[KeithFrench]

Your UDP port 28015 is closed on the game server.

[astronovaval]

Edit: **trace removed**
this should include it

[astronovaval]

nevermind, ive fixed it by just running sudo wireshark in a fresh terminal

[astronovaval]

wireshark is now just being extremely odd.. 

   

[KeithFrench]

OK, get me another trace of you trying 28015.

[astronovaval]

yes, i know, what i mean is that 28015 is not working properly, everything else it except that, steam needs that port to be open for players to connect to the server, since 28083 is just the games addon app, 28016 is remote console and 28015 is the games default server port itself.

[KeithFrench]

I said before, 28015 being UDP is not compatible with port-checking websites, as they only work with TCP.

[astronovaval]

ive just tested the portchecker and both 28083 and 28016 are open, yay. for some reason it still seems that 28015 is blocked. or it could be that ive not allowed an important steam port through, i need to double check.

[astronovaval]

still seems to be a local server 😕

[KeithFrench]

Well, it proved that 28083 is now OK, might be worth checking 28016 and the UDP one via another trace. Is this working any better now?

[astronovaval]

All i did was, start capturing, run the server, once its fully turned on i stopped capturing. is this what you wanted?

[KeithFrench]

I have just been analysing your latest Wireshark trace. Good news, TCP port 28083 now opens correctly from the internet. I assume that this was from a port-checking website, as the session starts to close just a few microseconds after it was successfully opened. I tried looking for TCP port 28016, but there wasn't anything from that port in the trace.

[astronovaval]

ive been timed out for sending too many PMs in a short amount of time, going to have to talk on the original post now.

[KeithFrench]

Hi @astronovaval 

Whatever you have done has totally changed things & not for the better. I have done some tests in Linux Mint & everything was exactly as I expected when the port was open, or when it was closed. I have sent you a PM with the details.

[KeithFrench]

I will do some testing on my Linux Mint later today, with the port open and then shut. I'll then compare firewall rules in Linux along with some more Wireshark traces & let you know.

[astronovaval]

Turns out there was a hidden file in linux that was blocking ipv4 and ipv6 port forwarding, just uncommented 2 lines and i can now connect to 28083, still cannot telnet localhost 28015 though..  (also not sure what ive changed but now RCON is just not working)