Port Forwarding when SuperHub is in Modem mode not working

[Geoghs]

I previously used SuperHub in router mode with port forwarding working uneventfully. I then decided to use it in Modem mode and connect it to an Asus mesh network to fix the appalling wifi. Port forwarding now doesn't seem to work.

Setup is:
Internet>>>SuperHub>>Asus>>Switch>>Everything on my network
(Also tried just the 2 devices connected to the router without a switch in between)

Devices that need port forwarding to work are Desktop PC and a NAS (VPN service). The services on the devices have remained unchanged and the ports are correctly configured in the Asus router but any connection from outside the LAN times out.

If I try using the website https://canyouseeme.org/ it tells me that the ports are closed.

All devices on the network have internet access. The DynDNS service is correctly updating my external IP address.

Looking deeper into the router settings, it seems that the WAN IP address that the router is using is a "private" IP address in the range 192.168.100.x but my IP address when I use https://www.whatismyip.com/ is coming up as a "proper" IP address 82.x.x.x.

It seems that the SuperHub is doing some sort of NAT, converting an external IP to an internal IP despite me wanting it to work only as a modem. Is there anyway that this can be turned off or is there some other workaround to allow port forwarding to work properly?

Thanks.

[spgray]

i have a few ports open, and they are all working fine.
WAN ip is set to "automatic IP" and DHCP query frequency is set to "aggresive mode"

[Geoghs]

That's very helpful. Thank you.

My configuration page is slightly different in that there is no option for NAT Type and I don't get to specify the UPnP range. Other than that, I am setup the same.

In my Network Map though, the WAN IP is an internal IP address of 192.168.0.14
I have no idea where that is coming from. The SuperHub in modem mode should have an internal IP of 192.168.100.1. My ASUS Router is giving out IP addresses in the range 192.168.50.x

I get the warning message below in the DDNS Tab:
The wireless router currently uses a private WAN IP address.
This router may be in the multiple-NAT environment and DDNS service cannot work in this environment.

[Geoghs]

Mine is setup much the same. The configuration options are slightly different but I don't think they're significant.

The problem is though that the WAN IP is an internal one - 192.168.0.14
Given that the SH in modem mode should have an IP of 192.168.100.1 and my Router is giving out addresses in the range 192.168.50.x I don't know where that WAN address comes from.

I'm getting the following error message in the DDNS tab also:
The wireless router currently uses a private WAN IP address. 
This router may be in the multiple-NAT environment and DDNS service cannot work in this environment.

The SH was factory reset, restarted and turned from router to modem mode.
I've turned the SH and router off then turned the SH back on , left it until all the lights stopped flashing before turning on the router. Still the same problem.

There must be something funny going on with the SH that causes there to be some NAT to occur before traffic hits my router.

[sophist]

your hub is still in router mode..

Log into the hub on http://192.168.0.1 and select the option to put the hub into modem mode (the hub will then reboot and come back up in modem mode - give it five minutes to settle down)

Disconnect all ethernet cables from the hub

Power off the Hub and your router/mesh system

Power on the hub and leave it five minutes to settle down

Connect your router/mesh system to the hub via ethernet cable and switch it on - leave it five minutes to settle down

Should all be working.

[spgray]

are you 100% sure the hub is in mode mode?
it doesn't look like it is, if it's giving the asus router a DHCP address in the 192.168.0.x range

[Tudor]

“The problem is though that the WAN IP is an internal one - 192.168.0.14”
It’s that address because your VM hub is still in router mode, not modem mode. You are suffering from double NAT and you can never get port forwarding to work unless the VM hub is put into modem mode.

[Geoghs]

The plot thickens!

So despite me being 100% certain I had enabled modem mode, as everyone else was sure I hadn't, I checked. Still in Router mode! *facepalm*
Evidently I hadn't applied the settings.

However..........now modem mode is enabled. I get the following:

I've just done a factory reset on both Superhub and Asus router, and will let them settle down before trying again.

[gary_dexter]

---

@Geoghs wrote:

The plot thickens!

So despite me being 100% certain I had enabled modem mode, as everyone else was sure I hadn't, I checked. Still in Router mode! *facepalm*
Evidently I hadn't applied the settings.

However..........now modem mode is enabled. I get the following:

I've just done a factory reset on both Superhub and Asus router, and will let them settle down before trying again.

---

You need to power off both routers.

Make sure nothing is connected to the hub by cable except the ASUS.

Power on the hub only and wait 5 mins.

Then power on the ASUS.

[Geoghs]

Tried that. Same problem - ISP DHCP not functioning properly.

There seems to be no way to speak to a Virgin engineer. The 150 customer support runs as test, tells me to reboot the router and offers to send me a link to the online help which doesn't help me.

I might try leaving it off overnight, reboot in the morning, leave it for an hour or so and try again.

[gary_dexter]

Have you set the DHCP mode on the ASUS to Dynamic/Automatic?