Putting VM Superhub 2ac into modem mode
Putting VM Superhub 2ac into modem mode
Author
Discussion

Dr Mike Oxgreen

Original Poster:

4,473 posts

196 months

Tuesday 7th August 2018
quotequote all
Ever since I updated my iPhone 6 and iPad Air 2 to iOS 11.4.1, I have had a problem where the wifi connection seems to "go to sleep" - it's still connected with strong signal, but no traffic gets through. This happens randomly after anywhere between 10 minutes up to an hour or more. And then a week or so later Mrs Oxgreen upgraded her iPhone SE and immediately started getting the same issue. On all devices you can wake up the wifi by switching wifi off and back on again, but it's annoying.

This is now a well-known issue, and appears to be related to Virgin Media customers with Superhub 2. Or, perhaps more specifically, it appears to be an incompatibility between iOS 11.4.1 and the chipset used in the SH2. Some people in the US with older routers are reporting the same problem.

Currently the solutions to this problem are 1) persuade VM to send you a Superhub 3 (but this invariably means spending hours on the phone to Pakistan while they endlessly go through their diagnostic flowchart), or 2) switch your Superhub 2 into modem mode.

I currently have my SH2 in router mode, but with wifi turned off. Wifi is provided by an Apple Airport Extreme. I would like to try switching my SH2 into modem mode, but I just want to check what is required to make that work.

Currently my SH2 connects to a switch, and the Airport Extreme connects to that switch via its WAN port (although it's in Bridge Mode so I think that means the WAN port is acting as a normal LAN port - correct?).

Am I right in thinking that the SH2 will need to connect directly to the Airport Extreme's WAN port without going via the switch when I put the SH2 into modem mode? I would then need to run another ethernet cable between the Airport Extreme and the switch.

I'm also assuming that the SH2 will stop doing DHCP when I switch it to modem mode, so I'll need to put the Airport Extreme into "DHCP only" mode (and I assume this makes it behave as a router)? In preparation for this switchover of DHCP responsibility, I have reconfigured the Airport Extreme, iPhone, iPad and desktop computer to fixed IP addresses (picking addresses well up the range so that they're unlikely to clash with anything DHCP assigns), so that I don't lose connectivity if something goes wrong.

The other issue is that I'm currently using the SH2's second ethernet port to connect an Apple TV and Sky+ HD, and I believe that port will stop working when I go into modem mode - so I'll have to reroute those devices into the other switch.

Am I right so far?

When I transfer DHCP from the SH2 to the Airport Extreme, how likely is it that all the other devices in the house will succeed in automatically obtaining IP addresses from the new server, or will they all start sulking? I can force-renew the lease on Mrs Oxgreen's laptop, but I've no idea how to do the same on her Samsung tablet, or the Apple TV boxes, or the Sky+ HD.

I'm reasonably tech savvy, but the pessimist in me always expects things to go wrong, especially where DHCP and routers are involved. I'm very reluctant to cock up my network too badly because Mrs Oxgreen relies on internet access for online tutoring.

If anyone can tell me if I'm heading in the right direction then I'd be very grateful.

Edited by Dr Mike Oxgreen on Tuesday 7th August 12:24

outnumbered

4,900 posts

265 months

Tuesday 7th August 2018
quotequote all
I use my Superhub in modem mode, and I can confirm that you'll lose all the other ports apart from the WAN port and one internal port that you then need to connect to whatever you're going to use as a router. In most cases, this would need to be a direct connection rather than going via a switch.

The DHCP switchover can be fairly transparent if you're using the same subnet for the new DHCP server but it depends a bit on what happens if the new server happens to assign a duplicate address. The simplest thing would just be to restart all the clients.

I don't know anything about the capabilities of the airport extreme though.

In my configuration, the "WAN" port on my router is connected to the internal port on the Superhub, and uses a DHCP client to get its public WAN IP address, which comes directly from the CMTS in Virgin's network. My router then has its own DHCP server and hands out internal addresses (192.168.0.0/24 in my case) to the internal network.

You can get to the Superhub on address 192.168.100.1 when it's running in modem mode (both ping and web interface).

I'll also add that my network is a lot more stable with the hub in modem mode, we also used to get regular outages when it was running as a router.

Edited by outnumbered on Tuesday 7th August 13:59


Edited by outnumbered on Tuesday 7th August 14:01

Dr Mike Oxgreen

Original Poster:

4,473 posts

196 months

Tuesday 7th August 2018
quotequote all
Thanks outnumbered!

So to confirm, does your Superhub in modem mode still provide the DHCP service? If so then perhaps I don't need to fanny around with DHCP...?

Edited again: Just re-read and you do say that your router (presumably not the Superhub) is providing DHCP.

Edited to add: I've now successfully transferred DHCP from the SH2 to the Apple Airport Extreme, and everything seems to be happy bunnies - although the Airport is flashing at me and warning that there's now nothing plugged into its WAN port. That's fine though - the WAN port will be populated when I put the SH2 into modem mode.

So now just to buy a couple of cables and I'm away.

Edited by Dr Mike Oxgreen on Tuesday 7th August 15:22

Dr Mike Oxgreen

Original Poster:

4,473 posts

196 months

Wednesday 8th August 2018
quotequote all
Okay, I’ve got the cables I need. Before I start I do have one or two more questions for anybody who can answer...

After I’ve switched the Superhub to modem mode, what should I set the “router address” setting to in the Apple AirPort Extreme and client devices?

I have a feeling I might be over-thinking this, although my confusion may simply stem from the fact that Apple uses the terminology “router address” where everybody else says “gateway address” or “default gateway”. If Apple really means “gateway” when they say “router” then I reckon it seems obvious to set it to 192.168.100.1.

Currently I’ve got the AirPort on a fixed IP, the mask is 255.255.255.0, and the router address is 192.168.0.1 (which is the address of the Superhub). But clearly this address won’t exist once the Superhub is in modem mode.

Should this be changed to 192.168.100.1, i.e. the new address of the Superhub in modem mode, even though it isn’t a router any longer? Is this setting more correctly described as the “gateway” address, in which case 192.168.100.1 makes sense?

Or should the router address be set to the address of the AirPort, on the grounds that this is what’s now behaving as a router? Will the AirPort get confused if I give it its own IP address as the router address?

And what about clients on fixed IPs - which address should they be using as their “router address”?

outnumbered

4,900 posts

265 months

Wednesday 8th August 2018
quotequote all
Dr Mike Oxgreen said:
Currently I’ve got the AirPort on a fixed IP, the mask is 255.255.255.0, and the router address is 192.168.0.1 (which is the address of the Superhub). But clearly this address won’t exist once the Superhub is in modem mode.

Should this be changed to 192.168.100.1, i.e. the new address of the Superhub in modem mode, even though it isn’t a router any longer? Is this setting more correctly described as the “gateway” address, in which case 192.168.100.1 makes sense?

Or should the router address be set to the address of the AirPort, on the grounds that this is what’s now behaving as a router? Will the AirPort get confused if I give it its own IP address as the router address?

And what about clients on fixed IPs - which address should they be using as their “router address”?
A router is a device that routes IP traffic between different subnetworks. In your new setup, the AirPort will be routing between the WAN and your local LAN.

The AirPort needs to get it's WAN address via DHCP from Virgin's network - this will be a public IP address, and you should also receive a default route from Virgin (whether this works at all depends on the capabilities of the AirPort, which I don't know about). You'd have to plug the AirPort's WAN port into the correct Superhub LAN port, and "somehow" configure the AirPort to acquire an address through it.

The AirPort also needs an address on the internal subnet that you're using for your clients. You can re-use 192.168.0.1 for that since the Superhub is no longer using it.

192.168.100.1 is just the host address of the Superhub to let you manage it via a browser. When it's in modem mode it isn't acting as a router at all.

Dr Mike Oxgreen

Original Poster:

4,473 posts

196 months

Thursday 9th August 2018
quotequote all
Thanks for that!

I can only find one IP setup for the AirPort, which gives the options DHCP, Static or PPPoE. At the moment I’ve set it to a static IP address, with the Superhub’s 192.168.0.1 address as the “router address”. I’m pretty sure this must therefore be the LAN address of the AirPort. If I set this to DHCP then I’m not sure whether it’ll be assigning itself a LAN address using its own DHCP, or whether it’ll obtain a WAN address from Virgin.

There doesn’t appear to be another setup to tell the AirPort to obtain a DHCP WAN address. Maybe it does this anyway, via whatever is connected to the WAN port.

I reckon this is simply going to require some experimentation. If it all turns to cheese then I can do a factory reset on the AirPort and/or the Superhub and start again.

Dr Mike Oxgreen

Original Poster:

4,473 posts

196 months

Thursday 9th August 2018
quotequote all
Well that was a voyage of discovery!

I put the Superhub into modem mode, and then I couldn't access 192.168.100.1 no matter what I tried. Even connecting the computer direct to the Superhub.

I dicked about for ages on the AirPort, trying various options for the router address, none of which worked. It wouldn't let me put it into "DHCP and NAT" mode, because it said that my DHCP address range conflicted with the WAN address. Not that I can find anywhere in the AirPort utility's user interface where it will tell me what the WAN address currently is.

This last error message chimed with something I read on a web page, that sometimes a modem will give out a 192.168.0.xxx address as the WAN address, and that you can fix this by moving your router to a completely different range of local addresses so that it doesn't conflict.

At this point, I thought "sod it" and simply did a pinhole factory reset on the AirPort. I then used the AirPort utility on my iPad and let it go through the setup routine. Eventually, things started working. And perhaps not surprisingly it has chosen a completely different range of LAN addresses based on 10.0.1.xxx

So I think I've got everything working. It's now a waiting game to see if our iOS 11.4.1 devices maintain a stable wifi connection.

Many thanks for your help! smile


And bugger it, this job is obeying Murphy’s Law of Network Cabling, namely that if you buy a cable of length x you will discover that you actually need a cable of length y, where y is 1 metre longer than the next available cable length, thus forcing you to buy a cable 3 times as long as you really need.

Edited by Dr Mike Oxgreen on Thursday 9th August 17:16

outnumbered

4,900 posts

265 months

Friday 10th August 2018
quotequote all

I did a quick google yesterday and saw that the Airport Extreme has a router mode and a bridge mode. It might be that it was previously set up with bridge mode (where the WAN port just acts like another LAN port, and which would make sense if you were using it behind the Superhub as a router), and the reset has put the AirPort back into router mode. The switch to a 10.x.x.x address range will be fine as long as you don't have any clients with statically assigned addresses in the 192.168.x.x range.




Dr Mike Oxgreen

Original Poster:

4,473 posts

196 months

Saturday 11th August 2018
quotequote all
Yup, it was previously in bridge mode. I had changed to “DHCP only” mode and switched DHCP off in the Superhub, but the AirPort wouldn’t let me go into “DHCP and NAT” mode because it reported a conflict between its WAN address and the 192.168.0.xxx address range.

When I noticed that the LAN range had switched to 10.0.1.xxx I immediately took all devices off their static addresses and allowed them to pick a DHCP address, which they did.

The Apple TV boxes both found a new address without any prompting, as did Mrs Oxgreen’s Samsung tablet, and the Sky+HD just required a “reset” on the network settings page. Mrs Oxgreen’s laptop needed an “ipconfig /release” followed by an “ipconfig /renew”. I told my elderly Kindle to forget the WiFi network and logged on again.

All is now well with the world.

And, best of all, none of the three Apple devices running iOS 11.4.1 have needed WiFi switching off and back on again, and it has now been a couple of days. The problem is definitely cured - yay! smile