Thanks for this method, I too wanted to use a more complex address range so tried this and after some fiddling, it worked for me. However, I thought I'd put a bit of extra detail about my experience of this super hub 3 as there were a few bits where I did do further googling and thought this might help others.
First of all, I was told by VM that I could get this hub for a small charge along with a speed upgrade. OK, there was a small charge, but I was asking as my old hub was showing signs of faults. I asked and they said that settings backup was compatible. That is not the case and so I ended up with a task of setting things up manually. That's a bit of a pain for me as I use MAC filtering on the wifi and non-default settings.
Second, do your basic setup for the hub first. By this, I mean the plugging in, calling the number, reboot after 3 minutes, let it upgrade for 15mins. It'll save you hassle later.
Third, my network settings were controlled by DHCP throughout and I was using a wired connection to the hub
Finally, I think you should only do this if you have reasonable competence with networking at the command prompt. If you don't know what "ipconfig" does, this might not be for you. If you are OK with that, but perhaps like me you aren't familiar with the Chrome developer console and how websites work, here's some tips (based on Chrome Version 51.0.2704.103 m)...
1) Open a new Chrome session and navigate to the log on screen and then press F12. A pane opens to the right in your browser
2) In the menu bar, click on console
3) I suggest tick the "preserve log" box. This will give you more control.
4) Right-click anywhere in the window and select the Log XMLHttpRequests as suggested
5) Log into the hub in the left hand pane and you should see the calls being made by the hub configuration program being listed out in the console pane
6) You'll see that depending on where you right-click you can clear the history and also, right clicking on the link lets you copy it out to notepad. It's useful to clear it down when you navigate around the menu and of course capture the required value for n=
I noticed my links had an extra "&+=nnnnnnn" bit on the end. My experience was this should be ignored. The links above worked fine once you substiture your value to put in the first n= bit and your required Hex values for IP addresses
You must convert your IP addresses to Hex. This is the Hex converter site I used...
http://ncalculators.com/digital-computation/ip-address-hex-decimal-binary.htm
I did notice that the converter returned the Hex value with an upper case "C" but the link that was tracked by the Chrome console used a lower case "c". I went with lower case for .my changes.
I was able to set a range well away of the 1.* range and I was able to set a starting value for the Hub that wasn't 1. Here are some examples for a base address of 192.168.42.13 with starting of ...42.14 and range to 42.254
192.168.42.13=c0A82A0D
192.168.42.14=c0A82A0E
192.168.42.254=c0A82AFE
giving example links of...
http://192.168.37.1/snmpSet?oid=1.3.6.1.4.1.4115.1.20.1.1.2.2.1.5.200=%24c0A82A0D;4;&_n=08563
http://192.168.37.1/snmpSet?oid=1.3.6.1.4.1.4115.1.20.1.1.2.2.1.11.200=%24c0A82A0E;4;&_n=08563
http://192.168.37.1/snmpSet?oid=1.3.6.1.4.1.4115.1.20.1.1.2.2.1.13.200=%24c0A82AFE;4;&_n=08563
http://192.168.37.1/snmpSet?oid=1.3.6.1.4.1.4115.1.20.1.1.9.0=1;2;&_n=08563
I chose to do this in the same tab I logged into and that worked OK for me. Just enter each of your links, one after the other into the address bar and press return. After the last step, I got a response from the configuration app and then if I tried to refresh the page, a "network changed" error from chrome. When I checked my ipconfig in command prompt, my network had changed. I also experienced the temporary lock out behaviour but you can get past this quicker by power cycling the router and waiting for the main light to go white again. You might also find a "ping -t" running in a command window helps you track what is going on in your machine's network connection. I found mine dropped in and out a bit, even thought the light was white.
BTW, if you can't remember what your previous SSID was, you might find it useful to use regedit to search registry for the value which should be there if your computer has connected to your old network. I found mine in sections under HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/WindowsNT/CurrentVersion/NetworkList/Profiles
One last thing, remember to back up your settings as you go. After successfully changing settings, and backing up, I reset my hub. You will need to use the original address range and password to get back in but restoring the config gets it all back to where you set it.
Thanks again to Eddy29 for his method.