Page 1 of 1

port forward rules not working wrt1900acv2

Posted: Tue Nov 12, 2019 3:34 pm
by karenmcd
I recently updated from the image I downloaded and installed in June 2019 to the one released at the end of October. My friends and I stopped playing Rust recently and switched over to ARK SE. I deleted the dedicated server for Rust and installed an ARK dedicated server.

canyouseeme.org reports:
Error: I could not see your service on x.x.x.x on port (7777) Reason: Connection refused

I have sudo ufw disable on the server machine.
Image

Added the rules in the appropriate section.
Image

Verified that they are indeed in the rules after router, server and modem reboots.
Image

DMZ is successful in allowing the ports to be reached, but obviously this is not an option other than for troubleshooting.

Am I missing something? Also, I am curious as to why iptables uses the host name instead of the ip as provided in the rule interface. This isn't intuitive to me, but I'm also just a hobby'ist.

Re: port forward rules not working wrt1900acv2

Posted: Tue Nov 12, 2019 4:07 pm
by Lantis
Do you have anything actually listening on that port currently? If there's nothing actively listening the connection will still appear closed even though the port forward is working fine.
The connection is forwarded to the device which says "I'm not expecting unsolicited connections on this port. Reject"

Re: port forward rules not working wrt1900acv2

Posted: Tue Nov 12, 2019 5:07 pm
by karenmcd
I ran netstat -pnltu

It shows the server listening on port 27015 only (not 7777).
Image

canyouseeme.org reports:
Error: I could not see your service on x.x.x.x on port (27015) Reason: Connection refused

This is strange

Re: port forward rules not working wrt1900acv2

Posted: Tue Nov 12, 2019 5:15 pm
by RomanHK
:idea: If your DMZ is working, there will be a problem opening the correct ports, try 27016. Instructions here: https://ark.gamepedia.com/Dedicated_Ser ... Forwarding

EDIT: Just note that OpenWrt since version 18.06 (Gargoyle 11.1.) Has no functional iptable helpers for security reasons! This can complicate port forwarding a bit, as is the case with FTP and passive ports.

Re: port forward rules not working wrt1900acv2

Posted: Tue Nov 12, 2019 7:26 pm
by RomanHK
karenmcd wrote:Also, I am curious as to why iptables uses the host name instead of the ip as provided in the rule interface.
The system will automatically resolve them if DNS is known. If you want a listing without translations, use the -n (--numeric) switch.

Example:

Code: Select all

iptables -L -n | grep 192.168.1.231