Skip to content

Instantly share code, notes, and snippets.

@chuckg
Created March 13, 2012 21:51
Show Gist options
  • Save chuckg/2031981 to your computer and use it in GitHub Desktop.
Save chuckg/2031981 to your computer and use it in GitHub Desktop.
ASUS RT-N66U: Port forwarding issues

Firmware: 3.0.0.3.108

Port forwarding is completely broken. Adding a new port to forward to does not result in the internal device receiving the data and after checking the "System Log" under the "Port Forwarding" tab I'm presented with an empty forwarding table:

Destination     Proto. Port range  Redirect to     Local port

--

I ran through these these steps to add a port forward:

  • Visit http://192.168.1.1
  • Click "WAN"
  • Click "Virtual Server / Port Forwarding"
  • Type in a "Service Name": ssh
  • Type in a "Port Range": 22
  • Type in a "Local IP": x.x.x.x
  • Type in a "Local Port": 22
  • Select "Protocol": BOTH
  • Click the "+"
  • Click "Apply", wait till page reloads.
  • New entry is present

Temporary Fix

I was able to get forwarding "working" by setting a DMZ host. This, of course, is not true forwarding but it has enabled me to continue using the router while the problem is fixed. It's interesting to note that after adding a DMZ, the port forwarding table shows an entry:

Destination     Proto. Port range  Redirect to     Local port
ALL             ALL                192.168.1.9                

Issues:

I suspect setting a DMZ host completely breaks any ability to play video games reliably.

--

Related threads:

@andrewtheis
Copy link

Thanks for the solution. Have you found any other work-around other than enabling DMZ? ASUS still has not released a firmware update.

@chuckg
Copy link
Author

chuckg commented Mar 30, 2012

A few other users have suggested that using Internet Explorer (version 7) to configure the router may yield better results, but I have not been able to verify this.

@FlyingToaster
Copy link

I bought one of these routers tonight and updated it to the 3.0.0.3.108 firmware and so far looks like port forwarding is working. The box says the hardware version is B1, maybe that has something to do with it?

@andrewtheis
Copy link

I have the same version (B1). What browser are you using to configure?

@FlyingToaster
Copy link

Usually I use Google Chrome when I'm configuring my router. Sometimes I use Firefox (my former most-used browser).

I've read that the browser seems to make a difference for some people, but I don't see how. Saving the information is all done in the router; I wouldn't think it would leave any data on a client machine that the router would need in order to work properly.

@oosidat
Copy link

oosidat commented Jun 11, 2016

Leaving this here in case someone comes by it like I did...

I was getting the same issue with my Asus RT-N53, firmware 3.0.0.4.376_3754.

Problem: After inserting a valid row in the port forwarding table, and clicking on Apply, the row disappears from the table and has no trace in the Port Forwarding System Log. I was using my Macbook Pro OS X 10.11.5 on Wi-Fi (using Chrome 50.0.2661.102 and Firefox 46.0.1) to attempt this without success.

My solution: Used my desktop Windows 10 on Ethernet to successfully add a row to the port forwarding table (and subsequently, the Port Forwarding system log was populated).

My theory: Something is wonky when trying to Port Forward the Asus router on WiFi - try an Ethernet connection (however, this is unsubstantiated until I get a chance to make the same change using Ethernet and my Macbook).

@josharcheruk
Copy link

josharcheruk commented Aug 2, 2017

@oosidat It's a year late but you actually need to press the little + button to the right of the input line to actually insert the rule, then you click apply. Failing to do so will result in the 'disappearing' behaviour you see. Not that it matters much anyway, Port Forwarding doesn't seem to work if you do insert the rule successfully anyway.

EDIT - got it working. You only need to specify 'Service Name', 'Port Range'[1] and 'Local IP'. Obviously choose the protocol which will default to TCP. Adding anything else seems to break forwarding.

[1] Note - you can enter a single port number here, no need to set the local port. Or you can set a port range using : as a separator or mix and match with commas like so... 80,443,6700:6705,12342

@stonecharioteer
Copy link

@PuffinBlue,

this is still not working for me. I am trying to ssh into a raspberry pi publically, but it doesn't work. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment