Superhub Question for you networking geniuses

smallclone · 15-07-2015, 22:10

I have an Asus rt-n66u.
My IP address is 192.168.1.1
I am in modem mode using the superhub.
I have created an access point in 192.168.1.2

What I would like to do is log in to my router and connected USB drive remotely on the internet. (using AIcloud app)

I used to be able to do this. Now I can't. I get an Invalid IP address warning. And my DDNS page of the router says:

"The wireless router currently uses a private WAN IP address (192.168.x.x, 10,x,x,x, or 172.16.x.x).
This router may be in the multiple-NAT environment and DDNS service cannot work in this environment."

My WAN IP: 192.168.0.2

Any tips? I'd be hugely grateful.

General Maximus · 16-07-2015, 20:56

you need to clear a few things up dude. When you say you have created an access point are you talking about another router which you are only using as a wireless access point or are you talking about a second wireless network on the n66?

You aren't going to have two wan ips. The n66 is only going to have one wan ip which will be the address VM gives you and mine starts 82.205.xxx.xx. If you are looking to map an internal ip for your second wireless network or for the router then it is going to be either of the lan addresses 192.168.1.1 or 1.2. I don't know where you got 192.168.0.2 from but it isn't in the same subnet as the first two which is why it isn't working.

smallclone · 16-07-2015, 22:18

I figured it out just now........get this......my superhub wasn't in modem mode.

I haven't touched the settings for years so christ knows how that happenned. I'm surprised my internet and router haven't been misbehaving more to be honest.

Cheers anyway.

General Maximus · 16-07-2015, 22:57

aye, 192.168.0.1 is the shub's ip address in router mode and 192.168.0.2 would be the next address it hands out to the n66 via dhcp and it would show up as the wan ip address in the n66's settings because it is coming over the wan port.

qasdfdsaq · 17-07-2015, 22:01

Quote:

Originally Posted by smallclone

I figured it out just now........get this......my superhub wasn't in modem mode.

That much was obvious ten seconds into reading your post