ASUS DSL-AX82U router with hub5x problem

[kevinbuckley70]

I have the ASUS DSL-AX82U router configured as a mesh system with multiple AX92U nodes (irrelevant to this question). All been working fine with NowTV broadband router for the last two years.

Just got VM fibre and it came with a hub5x. I was surprised to find no modem mode option in the menu but discovered it still exists if you manually enter 192.168.0.1/?page=modemmode.

Switched to modem mode and the light went green. 

I have connected the ASUS router WAN port to port4 on the hub5x. No other cables connected. 

The ASUS router is in WAN DHCP mode.

I have tried both options of power-on sequence: hub5 first and ASUS first. But in each case, the hub5x does not appear to provide the ASUS with an IP address.

Does the hidden modem mode on the hub5x actually work? 

Not quite pulling my hair out yet. But close. 

 

[Client62 · Accepted solution]

The modem mode option is hidden because it does not work, many have tried & end up resetting the Hub 5x,
and there is no timeline for when or if that will change.

[kevinbuckley70]

Darn. I have seen an alternative of setting the DMZ to 192.168.0.9, but disabling hub5 DHCP and, presumably, using the ASUS DHCP to assign ip's. But my ASUS is set to use 192.168.1.x so is there a way in the ax82u to translate from those two different network domains? Or should I set the hub5 to use 192.168.1 rather than 192.168.0? The reason is that I have WiFi devices connected to the mesh network which will be a pain to change if I have to switch them to 192.168.0

Any help greatly appreciated. 

[legacy1]

you can double NAT and hope VM understand passing the WAN IP is desirable.

set your router WAN with

fixed IP 192.168.0.254

subnet 255.255.255.0 

gateway 192.168.0.1

DMZ on hub to 192.168.0.254 

DNS on your router LAN to use 194.168.4.100 and 194.168.8.100

[sophist]

Unless things have changed, the hub can only be configured on the 192.168.0.x/24 network.

You have a couple of options, neither is perfect.

Option 1 - Double NAT.

Both hub and ASUS stay as they are - hub has 192.168.0.x/24 address space, ASUS router is assigned an address on the WAN side of (for e.g.) 192.168.0.10.  Then on the LAN side, it continues to operate 192.168.1.0/24 and all of the clients on your network connect to teh ASUS as they do currently for all services.

There are some drawbacks to this approach, as double-NAT can be a pain - it should *mostly* work, but you may find some services that require inbound connectivity (e.g. video games, voice chat) may struggle.. there are ways around it, but it can get messy and frustrating quickly if you don't understand what you're doing.  I would avoid this if possible.

Option 2 - Leave hub as router but put the ASUS into Bridge/Access point mode

The devices on your network will still connect to the ASUS for WiFi but they will pick up ip addresses from teh hub in the 192.168.0.x/24 range - this should be fine for any device that uses dhcp to configure the network, but any devices that you have configured with a static IP address will need to be reconfigured in the new range.  

In both scenarios, you should disable WIFi on the hub.