Virgin media internal ip
Discussion
Should be accessible anyway, just might need to change the network mask on the connecting device adapter to 255.255.0.0 (or /16) so it sees that devicd as in the 'local' range and doesn't try to get the gateway to route to it?
Shouldn't need to move the whole network to match one device!
Shouldn't need to move the whole network to match one device!
thebraketester said:
Probably because putting it a .10 puts it within its own dhcp range.
Try .1 at the end
That's the starting range for dhcp assignment, should be fine? Usually on these things it has to be in the same range as the device itself was set to so you need to change the device *and* the dhcp settings.Try .1 at the end
Obviously any static assignments have to shift too.
Your VM Hub has an internal IP address of 192.168.0.1. We know this because it is in the URL used to access the hub.
Your VM Hub is using a the 192.168.0 subnet and it can address itself and 254 devices. We know this because some of the devices have been assigned /24 addresses which shows that there are 24 bits in the subnet mask which is 11111111.11111111.11111111.0 more commonly written 255.255.255.0. The 0 at the end is how 256 addresses are accessible being 0 and then 1 to 255.
To set your DHCP like you have tried won't work because 192.168.1.0 is on a different subnet to the hub.
You need to change the IP address of the hub to 192.168.1.1 and then set the DHCP to 192.168.1.10 and then restart the hub but at first none of your devices will connect to the hub or the Internet although it might start working when the devices get given their new 192.168.1.0 addresses. So change the hub IP address and then the DHCP and only then restart the hub and then restart all your devices and they should get 192.168.1 addresses. If they don't then you won't be able to open the hub web page and you will have to factory reset the hub. Or manually set your devices with static 192.168.1 addresses.
Setting up the 192.168.1.0 subnet will not connect to a 192.168.254.9 address because 1 and 254 are on different subnets and to make this work you should use 192.168.254.1 as the hub address.
Alternatively...
As a shortcut find the page where the hub address is set and if there is a subnet mask then change it from 255.255.255.0 to 255.255.0.0 and keep the 192.168.0.1 address. Using the new net subnet mask the hub can address anything in from 192.168.0.1 to 192.168.255.255. This 65,536 addresses and includes all 192.168.0.1 up to 192.168.254.9.
Problems you may encounter is that the hub gets setup but none of your devices get the message and won't get any connection and don't work.
Have your hub factory reset procedure at hand as you might need it.
Please note that I am self taught and mainly learn by making mistakes.
Your VM Hub is using a the 192.168.0 subnet and it can address itself and 254 devices. We know this because some of the devices have been assigned /24 addresses which shows that there are 24 bits in the subnet mask which is 11111111.11111111.11111111.0 more commonly written 255.255.255.0. The 0 at the end is how 256 addresses are accessible being 0 and then 1 to 255.
To set your DHCP like you have tried won't work because 192.168.1.0 is on a different subnet to the hub.
You need to change the IP address of the hub to 192.168.1.1 and then set the DHCP to 192.168.1.10 and then restart the hub but at first none of your devices will connect to the hub or the Internet although it might start working when the devices get given their new 192.168.1.0 addresses. So change the hub IP address and then the DHCP and only then restart the hub and then restart all your devices and they should get 192.168.1 addresses. If they don't then you won't be able to open the hub web page and you will have to factory reset the hub. Or manually set your devices with static 192.168.1 addresses.
Setting up the 192.168.1.0 subnet will not connect to a 192.168.254.9 address because 1 and 254 are on different subnets and to make this work you should use 192.168.254.1 as the hub address.
Alternatively...
As a shortcut find the page where the hub address is set and if there is a subnet mask then change it from 255.255.255.0 to 255.255.0.0 and keep the 192.168.0.1 address. Using the new net subnet mask the hub can address anything in from 192.168.0.1 to 192.168.255.255. This 65,536 addresses and includes all 192.168.0.1 up to 192.168.254.9.
Problems you may encounter is that the hub gets setup but none of your devices get the message and won't get any connection and don't work.
Have your hub factory reset procedure at hand as you might need it.
Please note that I am self taught and mainly learn by making mistakes.
dba3087108 said:
I need to access a hikvision camera on 192.168.254.9.
I have a Poe switch. Would it work if I disconnected the virgin and had solely the laptop, camera and Poe switch and obviously changed the IP in windows to the same range?
They have a ‘virtual host’ feature on the NVR for this. Cameras are reachable on the NVR IP with port numbers 65001 for camera 1, 65002 etc.I have a Poe switch. Would it work if I disconnected the virgin and had solely the laptop, camera and Poe switch and obviously changed the IP in windows to the same range?
I put a static route on my network for the NVR subnet, so can use either method.
dba3087108 said:
I need to access a hikvision camera on 192.168.254.9.
I have a Poe switch. Would it work if I disconnected the virgin and had solely the laptop, camera and Poe switch and obviously changed the IP in windows to the same range?
Get you.... Can you access the NVR admin page via a browser? You'll need to enable virtual host (Network >> Advanced Settings) to get access to the cameras admin pages.I have a Poe switch. Would it work if I disconnected the virgin and had solely the laptop, camera and Poe switch and obviously changed the IP in windows to the same range?
Edited by thebraketester on Friday 20th March 07:20
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff


