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.
Added the rules in the appropriate section.
Verified that they are indeed in the rules after router, server and modem reboots.
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.
port forward rules not working wrt1900acv2
Moderator: Moderators
Re: port forward rules not working wrt1900acv2
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"
The connection is forwarded to the device which says "I'm not expecting unsolicited connections on this port. Reject"
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Please be respectful when posting. I do this in my free time on a volunteer basis.
Re: port forward rules not working wrt1900acv2
I ran netstat -pnltu
It shows the server listening on port 27015 only (not 7777).
canyouseeme.org reports:
Error: I could not see your service on x.x.x.x on port (27015) Reason: Connection refused
This is strange
It shows the server listening on port 27015 only (not 7777).
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
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.
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.
Turris Omnia with OpenWrt 21.02 - Tested
Linksys WRT3200ACM with Gargoyle 1.13.x
TL-WR1043ND v2 with Gargoyle 1.10.0
http://gargoyle.romanhk.cz custom builds by gargoyle users
Linksys WRT3200ACM with Gargoyle 1.13.x
TL-WR1043ND v2 with Gargoyle 1.10.0
http://gargoyle.romanhk.cz custom builds by gargoyle users
Re: port forward rules not working wrt1900acv2
The system will automatically resolve them if DNS is known. If you want a listing without translations, use the -n (--numeric) switch.karenmcd wrote:Also, I am curious as to why iptables uses the host name instead of the ip as provided in the rule interface.
Example:
Code: Select all
iptables -L -n | grep 192.168.1.231
Turris Omnia with OpenWrt 21.02 - Tested
Linksys WRT3200ACM with Gargoyle 1.13.x
TL-WR1043ND v2 with Gargoyle 1.10.0
http://gargoyle.romanhk.cz custom builds by gargoyle users
Linksys WRT3200ACM with Gargoyle 1.13.x
TL-WR1043ND v2 with Gargoyle 1.10.0
http://gargoyle.romanhk.cz custom builds by gargoyle users