Cannot Access hub 4 in modem mode

What’s the error from the web browser? Why on earth do you need to clone the MAC address, it goes against all networking ‘rules’. Just set up correctly, instructions follow:

How to put a VM hub into modem mode:

1) Access your hub on 192.168.0.1, sign on and put it into modem mode. On the Hub3 the bottom LED will change to magenta, on a Hub4 the LED band will be green, on a Hub5 the LED will be green. Best done from a wired connection.

2) Turn off the hub and disconnect any Ethernet cables

3) Fully initialise your own router or mesh master unit and make sure the WAN port is set to DHCP (for some routers or mesh this may have to be done in router mode before entering modem mode)

4) Connect your router or mesh master unit to the VM hub with an Ethernet cable, Cat5e or Cat6, any higher specification is a waste of money. On a Hub5 use port 4.

5) Turn on the VM hub.

6) You should now be able to access the internet and the hub will now be on 192.168.100.1

Note1: this only needs doing once for each new router or when VM changes your WAN IP address.

Note2: If you have a Hub4 and your own router is NOT 192.168.0.1 then it’s possible that you can still access the VM hub on 192.168.0.1

---

luke140488 wrote:

 I need to clone the MAC to the router but cannot login to get it.

 

---

will not work if you was hoping to get the WAN MAC from router mode it will not work on your router.

if you can ping 192.168.100.1 then you should get to the hub but you know these new hubs are coded badly that port 80 locked up maybe caused by the hub seeing port 80 from WAN and messed it up. Some reports say a reboot will fix that.

Hello,

You have probably tried this, but just in case, I had a similar problem when I first tried to log into the hub in modem mode with my web browser, turns out my issue was just to log in with 'http' not the default 'https' in the url. It was probably due to me setting up Firefox security quite strict, but perhaps worth a try with your browser.

http://192.168.100.1/

I would refrain from asking anything technical at Virgin Media forums as the users have incredibly bad cogntive problems. This includes both the customers with the silly badges and the members of staff.

The reason why you can't access your modem is because your IP ranges are different. Please note that your modem is 192.168.100.1 and your router is 192.168.0.1 (observe the black numbers).

Most routers will not deal with this problem nicely.

The only ways you can access your modem are as follows:

1) unplug everything and plug a laptop (or any device with ethernet) to the LAN1 port on this modem. If needed, perform an IP renew on this device. This will be necessary every time you want to connect to 192.168.100.1.

2) Change the IP on your ROUTER to 192.168.100.2. By doing this, you will be able to access your modem from any device connected to your router at any point. Note that if you have manually configured IPs on your network (not DHCP) you will need to change everything to 100.XXX as you will have no connection.

It would only be a problem if years and years of it working with old routers that someone went no source MAC outside a WAN subnet should happen so like I 94_173_27_164 can ARP to 94_173_27_80 because that within the subnet all other traffic like 1.1.1.1 goes to the gateway 94_173_26_1 (because of subnet 255.255.254.0) but with 192.168.100.1 which works fine for me and many others you ARP to the WAN gateway 94_173_26_1 get the MAC you send SYN to 80 to the gateway then hub picks this up and sends SYN, ACK from the source MAC DEAD of 192.168.100.1 which maybe some router think no I'm not going to allow it because I thinks it should not see a another MAC by 192.168.100.1 it should come from gateway MAC which is wrong because all old routers just accept it.

Which would mean the only way such a router would get to 192.168.100.1 would be as you said or on the WAN interface add a virtual interface 192.168.100.254/24 which the router can ARP from to 192.168.100.1 but only high end routers do this some newer routers that block 192.168.100.1 DEAD MAC are in the wrong.