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.

[astronovaval]

Still nothing, going to try updating the game server since there is a new patch out

[astronovaval]

Okay, Port 28083 is not blocked by my firewall but for some reason it seems 28015 is.. despite allowing it on UDP

i just ran telnet on localhost for port 28015 and its saying connection refused. all the other ports are fine and connect. 
22 ALLOW IN Anywhere
21 ALLOW IN Anywhere
28015 ALLOW IN Anywhere
28016 ALLOW IN Anywhere
28082 ALLOW IN Anywhere
28083 ALLOW IN Anywhere

Edit: specified from port 28015 to port 28015/UDP. going to see if this does anything

[astronovaval]

Alright ill have a look now, thank you!

[KeithFrench]

Hi @astronovaval 

Wireshark never lies!

Looking at TCP port  28083. Your problem is that the initial request comes in from the internet, through the router fine, but there is no response from the game server.

The most likely case is that the Linux firewall is blocking the initial TCP packet from getting to your game server. It is possible though that the packet reaches the port & it is closed. The reject packet that the application will send if the port is closed could be blocked by the firewall. 

There is one other possibility that the game server only opens port 28083 after successful traffic comes in on one of the other ports.

The problem is therefore with your Linux or game server, not the router.

I'd suggest that you contact the game server's support people, or investigate the Linux Firewall further. I must say though that I have never had any problems in opening ports in it.

Let me know what you find out.

[KeithFrench]

I have downloaded your trace, thanks very much. I have also deleted it from your thread, as it can be seen by anyone.

The real order to do this in is:-

1. Start the trace
2. Test the application
3. When it fails, stop & save the trace.

I'll look at it now & get back to you shortly.

[astronovaval]

I believe this is what i'm supposed to have done, started the server then started capturing.

[Karl-TalkTalk]

No Problem 🙂

Karl 

[KeithFrench]

Thanks @Karl-TalkTalk.

[Karl-TalkTalk]

Hi

Should be enabled now @KeithFrench 

Karl.

[KeithFrench]

You do not have PMs enabled currently within your Community Profile, I will ask TalkTalk to enable them for you.

[KeithFrench]

I will PM you shortly.

[KeithFrench]

No problem.

Give me a shortwhile to update my guide on how to install it in Linux & I will send it to you.

[astronovaval]

Its running Linux Ubuntu currently, and I'm pretty unfamiliar with Wireshark.

edit: ive just installed it on the machine

[KeithFrench]

Assuming that you are not testing like your UDP ones & falling victim to NAT Loopback, then the next step is Wireshark. Is your device on 192.168.1.10 either a Windows or Linux PC? They are the two most common operating systems that support Wireshark. I can analyse the traces for you if required. If you are not familiar with Wireshark, then I can send you a guide of mine on it.  

[astronovaval]

that makes sense, if the UDP port was open, you would be able to see my server in the game's server list and have anyone connect to it. but you cannot sadly.
the main thing im worried about is the 28083 port still not being open, its a key part of the game that i'd really like to have working. 

[astronovaval]

still nothing.. still showing most ports as closed

[KeithFrench]

If you are trying to connect from a local device via the router's WAN IP address, that will never work, due to NAT Loopback blocking the port on its return to the router. I thought from one of your early posts that you were only trying a port-checking website.

[KeithFrench]

You shouldn't have to, but I did see someone the other day where it started working after a router reboot.

[astronovaval]

Will i have to restart my router for these changes to take effect?

the UDP one is pretty easy to test, i have my other machine that cannot connect to the server via the public ipv4 address, only via the internal local ip of the server. 

[KeithFrench]

Thanks, no problems there. Can you try deleting the TCP one that does not work & then adding it again? How are you testing the UDP one? The only difference with mine is that I only ever set the protocol to TCP & UDP if it will use either, if not I always specify them exactly:-

My rules