Virgin Media Community

[shabble]

Yesterday, I was a happy bunny.

- My WiFi devices were in 192.168.0.0/24 along with the single desktop on the LAN,

- I had DHCP fixed for some devices so

- - my DMZ was a laptop connected via WiFi,

- - I had port-forwards set up to WiFi devices.

- I could administer via webadmin from the comfort of my sofa.

I get home today, to find that all WiFi devices are now on 192.168.1.0/24. As a result:

I can't use the webadmin on 192.168.0.1 unless it's from the desktop in a cramped space.

My DMZ and port forwards are now

1) all broken

2) can't be fixed since they can only be set on 192.168.0.0/24

3a) and I can't fix DHCP for any devices since applying changes refreshes the page (with no warning or error displayed) and the rule to be applied, isn't.

3b) The fixing a DHCP address page has the MAC addresses offset by one to the connected hosts when clicking the option box to pre-populate the form. e.g. click the 5th option box, and the data for the 6th listed computer is pre-populated.

3c) Even so, I can't change the 3rd octet (from 1 to 0 e.g.) since clicking the options set the first 3 octets, only leaving the 4th changable.

Info page:

   The information below shows the current status of this Hub 3.0.
   Standard specification compliant : DOCSIS 3.0
   Hardware version                 : 10
   Software version                 : 9.1.116V
   Cable MAC address                : **:**:**:**:**:**
   Cable modem serial number        : AAAP607<more numbers>

   System up time                   : 0 days 0h:43m:10s
   Network access                   : Allowed

   Your current Hub 3.0 internet settings are displayed below:
   MAC address : **:**:**:**:**:**
   IPv6 address         : Not Available
   IPv6 default gateway : ::1999:9999:0:6
   IPv6 lease time      : 0 days 0h:0m:0s
   IPv6 lease expire    : 0-00-00 00:00:00.00
   IPv6 DNS servers     : ::
   IPv4 address      : <deleted>
   Default gateway   : <deleted>
   IPv4 lease time   : 6 days 18h:36m:22s
   IPv4 lease expire : 2018-05-23 12:27:33.00
   IPv4 DNS servers  : 194.168.4.100
   IPv6 DS-Lite status : Disable
   DS-Lite-FQDN        :
   DS-Lite-address     : ::

[Roger_Gooner]

This is why some of us use our own router with the hub in modem mode.

[Nat_J]

I'm sorry to hear about this shabble,

I'd like to help with this.

I've sent you a private message so that we can chat some more.

Speak soon,

Nat_J

[Nat_J]

Many thanks for your quick reply,

I've checked your equipment from this end and everything appears within specification.

Have you tried completing a pin-hole reset at all?

Nat_J

[shabble]

No, because we'd only had it a couple of weeks 'without problems,' and the only possible, likely, cause is a remote update of the firmware, which I presume would would be re-instated on such a reset, and result in the same problems.

In checking the equipment, and stating it 'appears within specification,' are you saying that

- the move of wifi devices from 192.168.0/24 to 192.168.1/24, leaving the router itself and LAN connected devices on 192.168.0/24

- the inability of devices on the two CIDR blocks to communicate between the CIDR blocks

- the current inability to fix DHCP addresses (in general, and for wifi devices specifically) where previously it was fine

- the current inability to set the DMZ to a wifi-connected device where, again previously, it was fine

are all expected, and intended, behaviour?

[cje85 · Accepted solution]

It's definitely not a firmware update as you're still on 9.1.116V, which is well over a year old but still the latest official release.

There is an update likely soon but it will be the first since November 2016.

[shabble]

> which is well over a year old but still the latest official release.

Ok, I'll try a hard-reset when we can do without the internet for a while..

[Nat_J]

Thanks for updating shabble, 

How have things been since posting?

Nat_J

[shabble]

I have been unable to obtain sufficient time (either I'm not there, or when I am, others just "have to use use" the internet) to reset it.

Struggling using workarounds at the moment.