Menu
What's new
By:
Filters Better Search

[RT-N16] Port Forward wont work (3.0.0.4.374.33)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

N

NickDP

New Around Here
Hello

Yesterday my portforward stopped working, for some strange reason.

Today i've tried "anything", to get it back to work, re-flashing, erasing nvram etc etc.

But nothing seems to be working, so i realy hope some of you great minds can help me out here.

Im not sure what kind of info i would need to give you but here is the log file, when i try to open a port this is what i get:

My system log when i try to open a port: View attachment log.txt

and under the port it says:

Code: 
Destination     Proto. Port range  Redirect to     Local port
ALL             TCP    20          192.168.1.120   21         
ALL             TCP    21          192.168.1.120   21         
ALL             TCP    2021        192.168.1.1     21

The firmware is Asuswrt-Merlin (3.0.0.4.374.33)
The router is a Asus RT-N16

Hope you can help me out here :/

Best regards
Nick
 
The most likely cause for port forwarding to stop working overnight if you didn't change anything is that your DDNS isn't properly updating, so your DNS entry is no longer resolving to the correct IP.
 
RMerlin said:
The most likely cause for port forwarding to stop working overnight if you didn't change anything is that your DDNS isn't properly updating, so your DNS entry is no longer resolving to the correct IP.
Click to expand...

The ip is correct im afraid, and works inside "lan"
 
Last edited:
iptables --table nat --list -v -n

Give out the following:

Chain PREROUTING (policy ACCEPT 1477 packets, 94670 bytes)
pkts bytes target prot opt in out source destination
0 0 VSERVER all -- * * 0.0.0.0/0 100.81.226.216

Chain POSTROUTING (policy ACCEPT 150 packets, 9739 bytes)
pkts bytes target prot opt in out source destination
555 40651 MASQUERADE all -- * eth0 !100.81.226.216 0.0.0.0/0
0 0 MASQUERADE all -- * * 0.0.0.0/0 0.0.0.0/0 MARK match 0xd001

Chain OUTPUT (policy ACCEPT 150 packets, 9739 bytes)
pkts bytes target prot opt in out source destination

Chain LOCALSRV (0 references)
pkts bytes target prot opt in out source destination

Chain VSERVER (1 references)
pkts bytes target prot opt in out source destination
0 0 VUPNP all -- * * 0.0.0.0/0 0.0.0.0/0
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:20 to:192.168.1.120:21
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:21 to:192.168.1.120:21
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:2021 to:192.168.1.1:21

Chain VUPNP (1 references)
pkts bytes target prot opt in out source destination

Chain YADNS (0 references)
pkts bytes target prot opt in out source destination
Click to expand...


Im not sure if its usefull or not :/, i cant see anything wrong
 
What are you trying to forward, and to what? How are you testing it?
 
NickDP said:
Right now im trying to forward port 21, to my server(192.168.1.120), and im testing it with http://www.yougetsignal.com/tools/open-ports/ and i have a friend who tries to log on from the outside.
Click to expand...

Try using a different port such as 2222 just to make sure it's not that port 21 is blocked by something else. Also check on the FTP server that its firewall isn't blocking accesses.
 
RMerlin said:
Try using a different port such as 2222 just to make sure it's not that port 21 is blocked by something else. Also check on the FTP server that its firewall isn't blocking accesses.
Click to expand...

I tried 2021, same thing, and everything is disabled on the server :/
 
NickDP said:
I tried 2021, same thing, and everything is disabled on the server :/
Click to expand...

Try something really different like the port I suggested. 2021 is the default port Asus uses to forward to its own internal FTP server.
 
Since your DNAT entries do show and it stopped working overnight, then something must have been changed at some point, either in your environment, or in your modem's configuration. I would take a closer look at the modem itself, in case your ISP remotely pushed configuration changes to it.

I assume you already ensured that your dyndns IP was really your public IP and not an internal one?
 
I am actually having a similar problem. My port forwards work... kinda. Most, actually all but 2, forwarding works, however, anything that involves 5900 and 5901 seems to end up in the void.
This is what my VSERVER chain looks like:
Chain VSERVER (1 references)
pkts bytes target prot opt in out source destination
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:8080 to:192.168.1.1:80
5 320 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:8443 to:192.168.1.1:8443
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5000 to:192.168.1.11:5000
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:5000 to:192.168.1.11:5000
2049 131K DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5001 to:192.168.1.11:5001
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:5001 to:192.168.1.11:5001
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:1337 to:192.168.1.11:1337
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:1337 to:192.168.1.11:1337
3 184 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:32400 to:192.168.1.11:32400
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:32400 to:192.168.1.11:32400
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:8081 to:192.168.1.11:8081
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:8081 to:192.168.1.11:8081
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:8082 to:192.168.1.11:80
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:8082 to:192.168.1.11:80
1 64 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:224 to:192.168.1.11:22
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:224 to:192.168.1.11:22
840 48876 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:51413 to:192.168.1.11:51413
64 4142 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:51413 to:192.168.1.11:51413
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:51414 to:192.168.1.11:51414
13 720 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5900 to:192.168.1.4:5900
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:5900 to:192.168.1.4:5900
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:222 to:192.168.1.4:22
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:222 to:192.168.1.4:22
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:51412 to:192.168.1.4:51412
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:51412 to:192.168.1.4:51412
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:223 to:192.168.1.6:22
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:223 to:192.168.1.6:22
1 64 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5901 to:192.168.1.6:5900
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:5901 to:192.168.1.6:5900
 
ebalsumgo said:
I am actually having a similar problem. My port forwards work... kinda. Most, actually all but 2, forwarding works, however, anything that involves 5900 and 5901 seems to end up in the void.
This is what my VSERVER chain looks like:
Chain VSERVER (1 references)
pkts bytes target prot opt in out source destination
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:8080 to:192.168.1.1:80
5 320 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:8443 to:192.168.1.1:8443
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5000 to:192.168.1.11:5000
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:5000 to:192.168.1.11:5000
2049 131K DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5001 to:192.168.1.11:5001
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:5001 to:192.168.1.11:5001
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:1337 to:192.168.1.11:1337
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:1337 to:192.168.1.11:1337
3 184 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:32400 to:192.168.1.11:32400
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:32400 to:192.168.1.11:32400
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:8081 to:192.168.1.11:8081
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:8081 to:192.168.1.11:8081
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:8082 to:192.168.1.11:80
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:8082 to:192.168.1.11:80
1 64 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:224 to:192.168.1.11:22
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:224 to:192.168.1.11:22
840 48876 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:51413 to:192.168.1.11:51413
64 4142 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:51413 to:192.168.1.11:51413
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:51414 to:192.168.1.11:51414
13 720 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5900 to:192.168.1.4:5900
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:5900 to:192.168.1.4:5900
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:222 to:192.168.1.4:22
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:222 to:192.168.1.4:22
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:51412 to:192.168.1.4:51412
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:51412 to:192.168.1.4:51412
0 0 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:223 to:192.168.1.6:22
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:223 to:192.168.1.6:22
1 64 DNAT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5901 to:192.168.1.6:5900
0 0 DNAT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:5901 to:192.168.1.6:5900
Click to expand...

The port forwards on 5901 are working normally. See the first column, it does show that a packet hit the port, and was forwarded. Double-check your client at 192.168.1.6.
 
hmmmm... both clients 192.168.1.4 and 1.6 are running and are on two different platforms (one is a mac the other is a win box). I guess it is something with my servers.
 
You must log in or register to reply here.

Similar threads

G
VPN Client with Public IP, split tunnel web server over VPN and other traffic not on the VPN
Replies
4
Views
401
Grefyne
G
GShlomi
Sharing my DualWan with port forwarding and DDNS experience
Replies
0
Views
134
GShlomi
GShlomi
H
Port Forwarding Over WireGuard Connection?
2
Replies
22
Views
2K
houmi
houmi
V
Port forwarding not working?
Replies
6
Views
615
vkzl
V
CraigFoote
vsftpd.conf & port woes
Replies
16
Views
668
CraigFoote
CraigFoote
Similar threads
Thread starter Title Forum Replies Date
PaulA Port isolation on RT-AX88U-Pro (router) w/ Merlin w/ Tagged internet ISP Asuswrt-Merlin 1
N Connecting an ax58u to a BT homehub 5, via a lan port, and not getting internet access. Asuswrt-Merlin 3
D Redirect port 443 to 8443 Asuswrt-Merlin 6
GShlomi Sharing my DualWan with port forwarding and DDNS experience Asuswrt-Merlin 0
C 3004.388.6_2 media bridge mode (RT-AX86U but maybe others also) - port status missing Asuswrt-Merlin 8
P Google TV on lan port drops connection Asuswrt-Merlin 5
GShlomi Two WANs but not dual-WAN, with port-forwarding Asuswrt-Merlin 7
S Finding Port Connections Asuswrt-Merlin 2
John Tetreault How to open ipv6 firewall to a port on the router? Asuswrt-Merlin 4
S Unable to use port forward on the 2.5 Gbps WAN port Asuswrt-Merlin 1

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 817 (members: 31, guests: 786)
Top