What's new

RT-N66U official firmware 3.0.0.3_162

  • 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!

Howdy,
First it sounds like your not understanding what DynDNS does with what local ip addressing does. The DynDNS will get you back to your dynamic assigned ip address. That is all. The router is the item which you then need to configure to give up the tcp ports to another location behind your firewall. The best way is to make sure a reserved IP is assigned (set as static too if you want) the NAS. Now for example you use 192.168.1.10 for your NAS. Under the RT-N66U you would have a DHCP reserved for that specific MAC setup. The under the WAN tab, you would enable port forwarding, you would then make the custom rule for what you want. You would not worry about the drop downs, go right to the service name slot, type in a name you want, set the port you want, use drop down to select the IP address (192.168.1.10), and then the matching local port you want it matched to, then TCP, and then select the big + sign, don't forget to the hit apply at the bottom. done. :)

1 Hi Daybreak, or who ever is willing to help!
You are right about me not understanding Dyndns and VPN, you lost me when you quoted you would then make the custom rule for what you want. But I am trying and hopefully I will learn.
What I need to do is connect to 2 devices on my LAN Remotely Via the internet from any PC but will only concentrate on 1 device (Thecus NAS) at the moment.
I have listed the RT-N66U settings in the UI below which I think is needed to be completed and filled in the ones that I feel are correct or left as default , If possible could you pass or change the settings to the best of your ability.
1) I have finally managed to get the Dyndns to connect to the router by adding port 8080 to the end of my http://hostname.dyndns.org by luck which was the last port of an old dyndns account I had. I only remembered that because my ISP blocks port 80.
I am guessing that my Dyndns is working and have the setting correct in the RT-N66U UI DDNS
2) My NAS has a static IP of 192.168.1.3, it has 2 default ports the 1st one is http port 80 and the 2nd one is https port 443 I have tried different ports (8000,4443,1080) with no success but have put them back to the default ports
3) In the RT-N66U UI under WAN-Vitual Server/Port Forwarding under basic config Enable port Enable port forward is checked-Yes
Famous server list is at-Please select
Famous game list is at- Please select
FTP server port is at-2021
In the Port forwarding list at the bottom of the page
Service name is at- NAS
Port range is at- 80 I have tried the other ports mentioned above (8000,4443,1080)
Local IP is at- 192.168.1.3
Local port is at- 80 I have tried the other ports mentioned above (8000,4443,1080)
Protocol is at-TCP
I then hit the + and Apply.
4) In the RT-N66U firewall setting
Enable fire wall is checked-Yes
Enable Dos Protection checked-No
Logged packets type is-None
Enable web from WAN is checked -Yes
Port of web access from WAN is -HTTP 8080
Respond ping request from WAN is checked- No.
5) In the RT-N66U UI under VPN/Server/Basic Config
Enable PPTP server is checked-Yes
Broadcast support is checked-Yes
Username is at-Dyndns login username
Password is at- Dyndns login password
I then hit the + and Apply.
6) In the RT-N66U UI under VPN/Detail/Basic Config
Broadcast Support is at-Disable
Authentication is at-Auto
MPPE Encryption is at- All 3 boxes ticked
Connect to DNS server automatically is checked-Yes
Connect to WINS server automatically is checked-Yes
Client IP address is at 192.168.10.2-192.168.10.11

Cheers!

Ozmade
 
Is it possible to write my current settings to a file?

Plug a USB disk to your router. Then, run the following command to generate a complete output:

nvram show > /mnt/sda1/settings.txt

Don't forget to use the web interface to unplug the USB disk (Network Map, click on the USB disk, then select the option to safely remove it).
 
Ozmade, if you are going to use a DynDNS, then do not forward any port at all. The idea of the VPN is that once you connect with a VPN, it will be as if your laptop is connected directly on the router, bypassing entirely the router's firewall.

1) Set your VPN IP range to be 192.168.1.245-254 (if you don't, you will need to create static routes on your laptop, OR set it to route all traffic through the gateway - something that you usually want to avoid)
2) Connect to VPN using the hostname of your DynDNS
3) access directly the NAS's IP, i.e. http://192.168.1.3:8080 (if the NAS is on that IP)

Think of VPN as a hole through your firewall, giving you access to your whole network, without the need of any port forwarding.
 
Ozmade, if you are going to use a DynDNS, then do not forward any port at all. The idea of the VPN is that once you connect with a VPN, it will be as if your laptop is connected directly on the router, bypassing entirely the router's firewall.

1) Set your VPN IP range to be 192.168.1.245-254 (if you don't, you will need to create static routes on your laptop, OR set it to route all traffic through the gateway - something that you usually want to avoid)
2) Connect to VPN using the hostname of your DynDNS
3) access directly the NAS's IP, i.e. http://192.168.1.3:8080 (if the NAS is on that IP)

Think of VPN as a hole through your firewall, giving you access to your whole network, without the need of any port forwarding.

Hi RMerlin,

Does that mean I need to have a PC with VPN program connected on the LAN turned on at all times, or a PC with VPN program which I use to connect to the internet remotely.
Where do I set my VPN IP range on the PC, or in the router UI, if I try to set IP 192.168.1.245-254 in the router it says it is in Conflict with the router's DHCP IP pool: 192.168.1.2 ~ 192.168.1.254
 
Hi RMerlin,

Does that mean I need to have a PC with VPN program connected on the LAN turned on at all times, or a PC with VPN program which I use to connect to the internet remotely.
Where do I set my VPN IP range on the PC, or in the router UI, if I try to set IP 192.168.1.245-254 in the router it says it is in Conflict with the router's DHCP IP pool: 192.168.1.2 ~ 192.168.1.254

The VPN server is in your router. You only need the VPN client to connect on the computer that will be remotely accessing your network. It needs to connect every time you need to access your LAN.

Change you DHCP pool to only cover 192.168.1.2 through 192.168.1.240, leaving the 245-254 range free for VPN clients.
 
The VPN server is in your router. You only need the VPN client to connect on the computer that will be remotely accessing your network. It needs to connect every time you need to access your LAN.

Change you DHCP pool to only cover 192.168.1.2 through 192.168.1.240, leaving the 245-254 range free for VPN clients.

Hi RMerlin,
My reason for being on this particular forum is I assume that most people on here would have experience with the Asus RT-N66U Router and its can and can not do’s
I was hoping this would be a little more intuitive for the layman but it seems to be a little more in depth than I imagined! This is all very helpful information, however, I am far from an IT guy!
Daybreak, suggest that I Enable port forwarding and you suggests VPN with no port forwarding at all I am a little confused,
1) I have done a restore and cleared the NVRam on the N66U
2) I have enabled DDNS with my Dyndns info
3) I have changed DHCP pool to only cover 192.168.1.2 through 192.168.1.240, leaving the 245-254 range free for VPN clients.
4) In the VPN I have Enabled PPTP server,
Enabled broadcast to (Both)
Added a username and password,
Hit + and apply
MPPE Encryption ticked all boxes
Connect to DNS auto YES
Connect to Wins auto YES
Set IP range to be 192.168.1.245-254,
Hit apply.
5) In the firewall I have Enabled the firewall.
Enabled web access from LAN Port 8080
My Nas has static IP 192.168.1.3 with a default port of 80
My ISP I know blocks port 80
I then tried to log using my 3G iPhone on to http://Hostname.dyndns.org the page just timed out. Then http://Hostname.dyndns.org:8080 and straight to the N66U UI.

Is there anything I am doing wrong that you can see? Anybody!!

Thanks!
Ozmade
 
Hi RMerlin,
My reason for being on this particular forum is I assume that most people on here would have experience with the Asus RT-N66U Router and its can and can not do’s
I was hoping this would be a little more intuitive for the layman but it seems to be a little more in depth than I imagined! This is all very helpful information, however, I am far from an IT guy!
Daybreak, suggest that I Enable port forwarding and you suggests VPN with no port forwarding at all I am a little confused,
1) I have done a restore and cleared the NVRam on the N66U
2) I have enabled DDNS with my Dyndns info
3) I have changed DHCP pool to only cover 192.168.1.2 through 192.168.1.240, leaving the 245-254 range free for VPN clients.
4) In the VPN I have Enabled PPTP server,
Enabled broadcast to (Both)
Added a username and password,
Hit + and apply
MPPE Encryption ticked all boxes
Connect to DNS auto YES
Connect to Wins auto YES
Set IP range to be 192.168.1.245-254,
Hit apply.
5) In the firewall I have Enabled the firewall.
Enabled web access from LAN Port 8080
My Nas has static IP 192.168.1.3 with a default port of 80
My ISP I know blocks port 80
I then tried to log using my 3G iPhone on to http://Hostname.dyndns.org the page just timed out. Then http://Hostname.dyndns.org:8080 and straight to the N66U UI.

Is there anything I am doing wrong that you can see? Anybody!!

Thanks!
Ozmade

Are you trying to get to the webUI of the nas?
 
I then tried to log using my 3G iPhone on to http://Hostname.dyndns.org the page just timed out. Then http://Hostname.dyndns.org:8080 and straight to the N66U UI.

Is there anything I am doing wrong that you can see? Anybody!!

Thanks!
Ozmade

If you are going to configure a VPN, then you have to connect to that VPN. As someone else mentioned, you seem to be confusing VPNs with port forwarding. Those are two completely different things, with different goals in mind.

When you said you wanted to access your NAS, I assumed you wanted to access its network share. If that's the case, you NEED to use a VPN.

If all you want to do is access its web interface, then you don't need a VPN, and just need to forward ports. You will have to use different ports than 80 (blocked by your ISP) for that.

Start by reading Asus's FAQ on VPNs: http://support.asus.com/search.aspx?SLanguage=en&keyword=ASUSWRT VPN . See if that's really what you want to do.

I can't help you about the iPhone VPN configuration, I don't use Apple products. Sorry.

You need to make it clear what is your intended goal first. Do you just need to access the NAS's web interface, or do you need to also access its other services?
 
Last edited:
If you are going to configure a VPN, then you have to connect to that VPN. As someone else mentioned, you seem to be confusing VPNs with port forwarding. Those are two completely different things, with different goals in mind.

When you said you wanted to access your NAS, I assumed you wanted to access its network share. If that's the case, you NEED to use a VPN.

If all you want to do is access its web interface, then you don't need a VPN, and just need to forward ports. You will have to use different ports than 80 (blocked by your ISP) for that.

Start by reading Asus's FAQ on VPNs: http://support.asus.com/search.aspx?SLanguage=en&keyword=ASUSWRT VPN . See if that's really what you want to do.

I can't help you about the iPhone VPN configuration, I don't use Apple products. Sorry.

You need to make it clear what is your intended goal first. Do you just need to access the NAS's web interface, or do you need to also access its other services?

When I access the Thecus NAS over LAN I would use IE and enter IP 192.168.1.3 into the address bar that would open the NAS UI, from there I can access all my file through the webdisk and the admin. With my last router (D-Link) which a friend setup, I am not sure if VPN or Port forwarding was set up. When I wanted to access the NAS remotely over the internet I would use my http://hostname.dyndns.org:8080 that would open the NAS UI where I could access files through the webdisk and the admin exactly like being on LAN, Unfortunately my friend has move and is working offshore and is very hard to get in contact with. The NAS webservice port settings are still the same as then http port 80 & https 443.
I have read the FAQ on VPN. In the VPN I have Enabled PPTP server,
Enabled broadcast to (Both)
Added a username and password,
Hit + and apply
MPPE Encryption ticked all boxes
Connect to DNS auto YES
Connect to Wins auto YES
Set IP range to be 192.168.1.245-254,
Hit apply.
I have tried changing the portsin the NAS and adding to the hostname and still cannot get connected.
On the iPhone I use safari to access the WWW
 
Since all you require is web-based access to your NAS then you have no need for VPNs, as long as your NAS web interface is protected by a secure password.

Go to the WAN -> Virtual Server page. Make sure "Enable Port Forwarding" is set to "Yes".

Create a port forward entry under Virtual Server.
Service: NAS HTTP
Port range: 8080
Local IP: 192.168.1.3
Local Port: 80 (assuming your NAS uses port 80)
Protocol: TCP
Click on the "+" under Add/Delete to add the new rule.

You can repeat it for HTTPS access:
Service: NAS HTTPS
Port range: 443
Local IP: 192.168.1.3
Local Port: 443
Protocol: TCP
Click on the "+" under Add/Delete to add the new rule.

Then click on Apply at the bottom.

You should then be able to connect using http://hostname.dyndns.org:8080 (not recommended since this is not encrypted) or https://hostname.dyndns.org. If it doesn't work then it means your DynDNS might not be properly configured. To check, open a command prompt in Window, and type the following:

nslookup hostname.dyndns.org

It should return your WAN IP. If not, re-check your DynDNS configuration (username, password and hostname).
 
IPtv stream

Is it possible to stream IPTV to WAN via udpxy without VPN?

my ISP provides me IPTV and I can watch it using VLC player, for exampe IPTV channel from my ISP: udp://@239.255.1.19:5000
On RT-N66U I enabled Udpxy with port 4000. Now I can watch IPTV also with URL http://192.168.1.1:4000/udp/239.255.1.19:5000 . This URL also works when I connect from remote PC to VPN connection and I easily can watch TV. But... How I can make IPTV stream available from WAN without VPN connection? For example I want to use this URL: http://MY-EXTERNAL-IP:4000/udp/239.255.1.19:5000 ?
 
5Ghz coverage is terrible compared to the 2,4Ghz band but not on this router on all of them, the RT-N66U has probably has better coverage than others.
My RT-N56U is more or less unusable on the 5Ghz band once you leave the same room.

If yours is from the US you can boost the 5Ghz to 250mW.

What's the relation of mw to wifi range or bandwidth?
 
Hi RMerlin,
My reason for being on this particular forum is I assume that most people on here would have experience with the Asus RT-N66U Router and its can and can not do’s
I was hoping this would be a little more intuitive for the layman but it seems to be a little more in depth than I imagined! This is all very helpful information, however, I am far from an IT guy!
Daybreak, suggest that I Enable port forwarding and you suggests VPN with no port forwarding at all I am a little confused,
1) I have done a restore and cleared the NVRam on the N66U
2) I have enabled DDNS with my Dyndns info
3) I have changed DHCP pool to only cover 192.168.1.2 through 192.168.1.240, leaving the 245-254 range free for VPN clients.
4) In the VPN I have Enabled PPTP server,
Enabled broadcast to (Both)
Added a username and password,
Hit + and apply
MPPE Encryption ticked all boxes
Connect to DNS auto YES
Connect to Wins auto YES
Set IP range to be 192.168.1.245-254,
Hit apply.
5) In the firewall I have Enabled the firewall.
Enabled web access from LAN Port 8080
My Nas has static IP 192.168.1.3 with a default port of 80
My ISP I know blocks port 80
I then tried to log using my 3G iPhone on to http://Hostname.dyndns.org the page just timed out. Then http://Hostname.dyndns.org:8080 and straight to the N66U UI.

Is there anything I am doing wrong that you can see? Anybody!!

Thanks!
Ozmade

I'm having the exct same problem... I can connect to my router by http://XXXXX.asuscomm.com:8080.

When connected by the vpn connection, if I type 192.168.1.1 I get acces to my router at home also. When I put 192.168.133 I can go on gui page of my network printer at home. by putting 192.168.1.122 I can acces my NAS, but by web interface, and that sucks because it uses ajax file browser that don't allow me to watch videos.
I can also connect to my 2 other routers (home) at 192.168.1.2 and 3. They have DHCP disabled, are on the same subnet and are used like switches and to extend wifi range, one is also used to provide B/G with wep encription for my kids DSi.

When i go to windows explorer->network, I don't see any of my computers, their shared folders or NAS that I have at home. I only see my other computer in my office. ( this setup is simple Modem->router-> 2 PC and network printer)

I'm connected thru my home network to the internet from my workplace, but I can't communicate the same way as if I would be at home.
my DHCP on my Main router (192.168.1.1) is set from ...1.100 to ....1.250. Vpn is from ....1.251 to ....1.254 , so there are no conflicts.

I'm really clueless, any guide and help would be appreciated. I'm working on stock firmware that came with the router .112. newer been flashed (yet ;) )
 
When i go to windows explorer->network, I don't see any of my computers, their shared folders or NAS that I have at home. I only see my other computer in my office. ( this setup is simple Modem->router-> 2 PC and network printer)

Network browsing will always be tricky over VPN. Your local master browser (probably your server at work) has no clue about the existence of your home network, so it won't list those machines when your access your desktop's network listing.

Simplest is to access those machines directly using their IP or hostname (i.e. \\MyNAS if name resolution works, or else \\192.168.1.111).

I'm really clueless, any guide and help would be appreciated. I'm working on stock firmware that came with the router .112. newer been flashed (yet ;) )

I'd strongly advise you upgrade to the latest version (3.0.0.3.162) as it fixes a LOT of issues since build 112.
 
Since all you require is web-based access to your NAS then you have no need for VPNs, as long as your NAS web interface is protected by a secure password.

Go to the WAN -> Virtual Server page. Make sure "Enable Port Forwarding" is set to "Yes".

Create a port forward entry under Virtual Server.

Click on the "+" under Add/Delete to add the new rule.

You can repeat it for HTTPS access:

Click on the "+" under Add/Delete to add the new rule.

Then click on Apply at the bottom.

You should then be able to connect using http://hostname.dyndns.org:8080 (not recommended since this is not encrypted) or https://hostname.dyndns.org. If it doesn't work then it means your DynDNS might not be properly configured. To check, open a command prompt in Window, and type the following:



It should return your WAN IP. If not, re-check your DynDNS configuration (username, password and hostname).

I have tried all of those steps and when I enter http://hostname.dyndns.org it still connects to the N66U UI.
I have tried the CMD command and it returns the correct WAN IP.
Below are the settings of the Virtual server under WAN,
I have also disabled VPN

Basic Config
Enable Port Fowarding Yes
Famous Server List Please select
Famous Game List Please select
FTP Server Port 8080

Port Forwarding List
Service Name Port Range Local IP Local Port Protocol

NAS HTTP 8080 192.168.1.3 80 TCP

Thanks! http://forums.smallnetbuilder.com/images/smilies/confused.gif

Ozmade
 
Network browsing will always be tricky over VPN. Your local master browser (probably your server at work) has no clue about the existence of your home network, so it won't list those machines when your access your desktop's network listing.

Simplest is to access those machines directly using their IP or hostname (i.e. \\MyNAS if name resolution works, or else \\192.168.1.111).
As I said in my post my office network is small, and have no server. Just modem ddwrt router, 2 PC ans network printer.

I just figured it out, maybe ozmade have similar issue.
The problem in my case had nothing to do with asus, but with windows. My office computers are on workgroup named "work" My computers at home work on workgroup named "workgroup" When I changed my 2 computers workgroup to "workgroup" everything started to work!!!
The bad part is that if someone would be an part of big workgroup named let's say "office" at his workplace,he would have to change his workgroup on his computer every time he would want to connect his network at home, and loosing his network availability at work.
I'd strongly advise you upgrade to the latest version (3.0.0.3.162) as it fixes a LOT of issues since build 112.

Originally Posted by Shikami
The annoying dmesg issue with VPN is still there:
Jul 25 19:37:02 kernel: protocol 0000 is buggy, dev eth0
Jul 25 19:37:02 kernel: protocol 0000 is buggy, dev eth0
Jul 25 19:37:02 kernel: protocol 0000 is buggy, dev eth0
Jul 25 19:37:02 kernel: protocol 0000 is buggy, dev eth0

RMerlin, any reason for this VPN issue? Maybe you can pass on down some information about this, if possible?

This happens if you enable broadcast support for the VPN server. I haven't had a chance to look more in depth yet.
Can you help me out what does exactly broadcast support does? I think it has to be enabled to make the vpn connection work both ways.

Was looking at my log today:

Aug 2 05:19:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:20:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:20:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:20:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:20:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:20:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:20:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:20:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:20:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:21:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:21:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:21:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:21:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:21:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:21:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:21:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device
Aug 2 05:21:24 miniupnpd[3680]: sendto(udp_notify=14, 192.168.1.1): No such device

What it could be??
 
man, RT-N66U surely is a strong router, but the radiation is as well strong. Just test the radiation from a meter, the old linksys shows safe until next to it, while RT-N66U shows extreme dangerous even 2-3 feet away.

The large coverage does come with a price. Just make sure you don't sit next to it.
 
man, RT-N66U surely is a strong router, but the radiation is as well strong. Just test the radiation from a meter, the old linksys shows safe until next to it, while RT-N66U shows extreme dangerous even 2-3 feet away.

The large coverage does come with a price. Just make sure you don't sit next to it.

Just curious what you are using to measure "radiation", what band are you using, and what do you have the transmitter power set to?

Thanks.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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