Modem -> VoIP -> N66U = no FTP/VPN via DDNS

[Swift0114]

I'm a pure noob to this router or any routers this powerful. My last one was WRT54G that's ~10 years old . I just picked this puppy up yesterday.

Anyways, running stock firmware 3.0.0.4.260.

I've been having trouble getting/logging into my FTP via DDNS or any way outside of my internal network. I know where the problem lies but I do not know how to fix it. Hoping you pros can help me out.

As the title states, I have my Cable Modem connected to my VoIP (SPA-2102) which is connected to my N66U. If I take my VoIP out of the equation and connect my cable modem directly to my N66U, all is good. I can't login via my DDNS (ex. myftp.asuscomm.com). After doing some reading, I realized that my WAN IP is the issue. When my N66U is directly connected to my modem, it spits out (ex. 67.134.54.130) on the Network Map but when my VoIP is in the equation, I get the local LAN IP of the VoIP (ex. 192.168.7.1).

I know my problem is there but how do I get around this? I tried changing my connections to cable modem -> N66U -> VoIP but then I end up with no phone. VoIP becomes useless...

Is there any way around this?
Appreciate the help.

 

[RMerlin]

The problem is indeed the fact that your VoIP box is also a router. Having two routers one in front of another will prevent things such as port forwarding from working properly, since the first router (the SPA) will firewall all connections, preventing them from reaching the second router (the RT-N66U).

You will have to check the documentation of your VoIP device to see if it allows to completely disable its router function and turn it into a plain ATA (like the SPA112 which I have here at home). Once that's done (assuming it's possible), you will be able to move behind of your RT-N66U instead of in front.

 

[Swift0114]

The problem is indeed the fact that your VoIP box is also a router. Having two routers one in front of another will prevent things such as port forwarding from working properly, since the first router (the SPA) will firewall all connections, preventing them from reaching the second router (the RT-N66U).

You will have to check the documentation of your VoIP device to see if it allows to completely disable its router function and turn it into a plain ATA (like the SPA112 which I have here at home). Once that's done (assuming it's possible), you will be able to move behind of your RT-N66U instead of in front.

Thanks Merlin, I checked my provider (italkBB) and noticed they have the SPA112 as well. I am almost tempted to call them and get that instead of having to do the run around to reconfigure the settings.

I've been researching on how to change the settings but nothing clear yet. So far, I've just read to turn off DHCP and set the WAN connection type on the SPA2102 to Static IP with an address similar to my N66U 192.168.1.X. Also with the gateway the same as my N66u (192.168.1.1).

Hopefully this will work when I try it at home.

 

[JoeSchmoe007]

Thanks Merlin, I checked my provider (italkBB) and noticed they have the SPA112 as well. I am almost tempted to call them and get that instead of having to do the run around to reconfigure the settings.

I've been researching on how to change the settings but nothing clear yet. So far, I've just read to turn off DHCP and set the WAN connection type on the SPA2102 to Static IP with an address similar to my N66U 192.168.1.X. Also with the gateway the same as my N66u (192.168.1.1).

Hopefully this will work when I try it at home.

You may not even need to disable router function on you VOIP adapter if you don't connect any devices to it. I don't recall disabling router function on my OBi-202, I just put it behind N-66 (OBi-202 has WAN and LAN port. I connected WAN port to RT-N66). I do recommend changing N-66 from default setting of 192.168.1.* to something different, like 192.168.8.* before you do this.

 

[Swift0114]

You may not even need to disable router function on you VOIP adapter if you don't connect any devices to it. I don't recall disabling router function on my OBi-202, I just put it behind N-66 (OBi-202 has WAN and LAN port. I connected WAN port to RT-N66). I do recommend changing N-66 from default setting of 192.168.1.* to something different, like 192.168.8.* before you do this.

The default (if i recall) is 192.168.7.1 right now. My N66 is 192.168.1.1. When I plug the port #1 of my N66 into the WAN of VoIP, phone does not work...

Maybe I need to somehow disable DHCP on the VoIP? Not sure if I can. I know Static IP was one of the options which I was going to try yesterday but figured I would check here first.

 

[JoeSchmoe007]

The default (if i recall) is 192.168.7.1 right now. My N66 is 192.168.1.1. When I plug the port #1 of my N66 into the WAN of VoIP, phone does not work...

Maybe I need to somehow disable DHCP on the VoIP? Not sure if I can. I know Static IP was one of the options which I was going to try yesterday but figured I would check here first.

But did you check that your VOIP adapter received IP address (in 192.168.1.* range) from RT-N66U? Because if it didn't - no surprise it doesn't work.

 

[Swift0114]

But did you check that your VOIP adapter received IP address (in 192.168.1.* range) from RT-N66U? Because if it didn't - no surprise it doesn't work.

A lightbulb clicked as soon as you said that. You are absolutely right, I powered down everything then made my connections as I powered each device up. Modem -> N66U -> VoIP, waited a few mins, logged into my N66U and checked the clients. Noticed the VoIP was assigned 192.168.1.189. Picked up my phone and callled myself and voila my cell phone rings! Thank you for the tip!

So it works now and I will try the ftp next. However, I can't log onto my VoIP box anymore even using 192.168.1.189. Do I have to connect a physical line into the VoIP, type in 192.168.7.1 again in order to access it?

 

[JoeSchmoe007]

A lightbulb clicked as soon as you said that. You are absolutely right, I powered down everything then made my connections as I powered each device up. Modem -> N66U -> VoIP, waited a few mins, logged into my N66U and checked the clients. Noticed the VoIP was assigned 192.168.1.189. Picked up my phone and callled myself and voila my cell phone rings! Thank you for the tip!

So it works now and I will try the ftp next. However, I can't log onto my VoIP box anymore even using 192.168.1.189. Do I have to connect a physical line into the VoIP, type in 192.168.7.1 again in order to access it?

Yes, you may have to connect your computer directly into LAN port on your VOIP adapter in order to login and then use 192.168.7.1 to login. The most likely reason it doesn't work via 192.168.1.189 is that VOIP adapter by default is configured to only allow administration via LAN port due to security reasons (this is how my OBi-202 was configured). You can then login and see if there is an option to allow VOIP adapter administration via WAN.

After you get it all sorted out you may want to configure your VOIP adapter to always receive the same address from RT-N66 via LAN/DHCP Server/Manually Assigned IP around the DHCP list

 

[Swift0114]

Yes, you may have to connect your computer directly into LAN port on your VOIP adapter in order to login and then use 192.168.7.1 to login. The most likely reason it doesn't work via 192.168.1.189 is that VOIP adapter by default is configured to only allow administration via LAN port due to security reasons (this is how my OBi-202 was configured). You can then login and see if there is an option to allow VOIP adapter administration via WAN.

Looks like my VoIP adapter is the same. I can only access it via LAN. I currently have it connected my old WRT54G to the VoIP adapter via LAN port. This way I can access my VoIP adapter anytime. I will probably remove it once everything is steady due to possible signal interference with my N66U.

After you get it all sorted out you may want to configure your VOIP adapter to always receive the same address from RT-N66 via LAN/DHCP Server/Manually Assigned IP around the DHCP list

Thanks for the tip. I was wondering if it was required after I got it working. So currently, in my N66U, I set a static IP with reference to my VoIP MAC address under "Manually Assigned IP around the DHCP list(list limit:32)" as you have mentioned. I think that solves my VoIP problem. I have yet to try the FTP and VPN Been busy with a few other issues around the home.

Thanks again!

 

[JoeSchmoe007]

Looks like my VoIP adapter is the same. I can only access it via LAN. I currently have it connected my old WRT54G to the VoIP adapter via LAN port. This way I can access my VoIP adapter anytime. I will probably remove it once everything is steady due to possible signal interference with my N66U.



Thanks for the tip. I was wondering if it was required after I got it working. So currently, in my N66U, I set a static IP with reference to my VoIP MAC address under "Manually Assigned IP around the DHCP list(list limit:32)" as you have mentioned. I think that solves my VoIP problem. I have yet to try the FTP and VPN Been busy with a few other issues around the home.

Thanks again!

There is most likely a strong interference with WRT54G. I have GL version and until I turned it off wireless speeds on RT-N66U were abysmal.

FTP works but note that by default it allows anonymous logins.

I only tried PPTP VPN and it is rather slow. FTP in/out via VPN (I used Windows PC as FTP server) is 4-5 times slower comparing with FTP via port forwarding.

 

[Swift0114]

There is most likely a strong interference with WRT54G. I have GL version and until I turned it off wireless speeds on RT-N66U were abysmal.

FTP works but note that by default it allows anonymous logins.

I only tried PPTP VPN and it is rather slow. FTP in/out via VPN (I used Windows PC as FTP server) is 4-5 times slower comparing with FTP via port forwarding.

The WRT54G seems ok so far. I've only tested it for a few hours last night. I will disconnect it eventually.

Originally I was going to leave it since my printer only uses 802.11g and wanted to keep my N66 running 802.11n only. I guess I have to switch it back to mixed signal With the mixed, I recall seeing my laptop reaching 65 mbps vs the 150 mbps (max for the laptop network card) I am getting on 802.11n only.

I've added user login with the ftp and just tried it at work and I think I should be ok from amateur hackers.

I tried the VPN today and it was a bit slow at work. I have to look into port fowarding, I have never used it for a VPN. Only on certain applications (torrent/games) with my WRT54G.

 

[JoeSchmoe007]

The WRT54G seems ok so far. I've only tested it for a few hours last night. I will disconnect it eventually.

Originally I was going to leave it since my printer only uses 802.11g and wanted to keep my N66 running 802.11n only. I guess I have to switch it back to mixed signal With the mixed, I recall seeing my laptop reaching 65 mbps vs the 150 mbps (max for the laptop network card) I am getting on 802.11n only.

I've added user login with the ftp and just tried it at work and I think I should be ok from amateur hackers.

I tried the VPN today and it was a bit slow at work. I have to look into port fowarding, I have never used it for a VPN. Only on certain applications (torrent/games) with my WRT54G.

My point was to use port forwarding instead of VPN.

 

[Swift0114]

My point was to use port forwarding instead of VPN.

Port forwarding would require me to dedicate a PC for FTP and also have it connected via Ethernet line in the event I have to WOL. I don't have the resources for that right now. Unless I'm not understanding correctly how a port forward FTP works.......

VPN Server, although slow, is the only method (as far as I know) I can use to monitor my router away from home, make changes and most importantly, manage the Download Master. Unless there are other methods I don't know of..

 

[JoeSchmoe007]

Port forwarding would require me to dedicate a PC for FTP and also have it connected via Ethernet line in the event I have to WOL. I don't have the resources for that right now. Unless I'm not understanding correctly how a port forward FTP works.......

VPN Server, although slow, is the only method (as far as I know) I can use to monitor my router away from home, make changes and most importantly, manage the Download Master. Unless there are other methods I don't know of..

You are understanding it all correctly. I used PC as FTP server just to judge VPN performance. If you intend to use router as FTP server and Download Master port forwarding doesn't apply.

That being said you can probably enable router administration via WAN port and avoid using VPN but this would be a bad idea from security point of view. On top of this even if you use VPN for functionality that you mentioned (using router as FTP server and Download Manager) VPN would not affect performance of either of these.