Anyone else having HUB4 modem mode issues?

[dl12345]

Yesterday I started experiencing poor performance on my Gig1 line. I run my HUB4 in modem mode.

I tried to access the web interface to check the network log and see if there were any errors. No matter what I tried to do, I could not access it. The port was open, but it was refusing the connection.

Undeterred, I did a hard factory reset by pressing the reset button for 60 seconds. It came up in default router mode setup. I duly set the language, changed the password and then set it into modem mode.

It came up in modem mode and failed to respond to DHCP requests. 

About 10 factory resets and 22 hours later, the problem persists.

Running a tcpdump, there is just radio silence. Occasionally, but not every time, and right after rebooting, it will respond to the DHCP solicitation and allocate me a 192.168.100.0/24 IP address, which it clearly should not be doing in modem mode.

There's absolutely nothing changed on my router: it's been running perfectly this way for a good 4 years now with the same HUB4 running in modem mode. 

I do recall once early on in the factory reset process that it flashed the LED green-yellow, so it appears to have updated the firmware at some point. Perhaps Virgin has published broken firmware? This horrible black box of a device has literally no log-level capability beyond the physical DOCSIS parameters, so impossible to even see what its doing.

Virgin telephone support indicated their second level support "knows about this problem", since I described it in some detail and said my tcpdumps were not showing any response to DHCP solicitations. Perhaps some of the forum denizens can shed some light for me?

[legacy1]

I think VM want to end modem mode or just make it hard and Oh look router mode use it no VM stop it.

Try modem mode with a PC no router and we go from their.

and your router is a router and not a mesh?

[dl12345]

No it doesn' work with a PC, but not surprising, since VM lock their IP address assignment when using modem mode to a single MAC address, so while a DHCP lease is active / the MAC address is cached by the VM equipment, it won't assign a lease to a new MAC address. 

Yes, my router is a router. Is an x86_64 router running OpenWrt that I've been using with exactly the same HUB4 for 4 years and it's had zero configuration changes. The only thing I did was factory reset the HUB4 and then put it back into modem mode. I know the router works and it's had no config changes.

Since the router has a full Linux command line, I can run a tcpdump on the external ethernet interface and see all the traffic. The VM equipment is simply not replying to the DHCP solicit. 

[Mr-Dice]

I needed my Hub4 in modem  mode and found i couldn't get access  to the modems settings . I would get a white screen . I have an android  phone and had a mess around . I factory  reset the Hub4  then connected  my phone to the wifi . Then i went to the WiFi settings  of my phone and changed my ip  to static . I then changed my DNS to 1.1.1.1 and 8.8.8.8  . I then rebooted not reset the modem  with the switch at the back .  Once fully booted  I put in the browser  of my phone using Chrome 192.168.0.1 and changed the modems login password to something easy fast and simple  . Then I switched  the hub4 off and on again . As soon as it fully booted I quickly  logged in with the simple password  and clicked modem mode and apply . At this point it freezes every time and doesn't  restart  as it should to apply the setting  . So then I turned  the hub4 off and on again and it went into modem  mode . Now  Some  times when i want to login  using 192.168.0.1 it will freeze but if I try a few times I can get in the modems settings.  

[dl12345]

Seems to have resolved itself now. Not sure why, perhaps the result of a support intervention, since I logged a call today. 

[legacy1]

---

@dl12345 wrote:

No it doesn' work with a PC, but not surprising, since VM lock their IP address assignment when using modem mode to a single MAC address, so while a DHCP lease is active / the MAC address is cached by the VM equipment, it won't assign a lease to a new MAC address. 

---

Oh it should of worked with a PC the MAC change happens when you power hub the hub for 2mins in modem mode because how else would router mode with one MAC be allowed and the another MAC router or PC be allowed.