nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to connect to devices with address 192.168.0.x

hz101

I have a FiOS-G1100 router. Its address is 192.168.1.1.

It shows a device with address 192.168.0.88 is connected as following:

However, I cannot connect to this device which is an IP camera. This is the case for other devices with IP 192.168.0.x. There is no problem in connetion with any device with IP address 192.168.1.x.

Could anyone shed some light on this?

Accepted answers

CRobGauth

I have two guesses.

1) Router doesn't route between different subnets without a static route. Even if they are within the router.

2) The IP address on the wifi subnet of the router was not configured as the default gateway of the device that was on that subnet. For example: if roouter was set to 192.168.0.2 and default gateway of device was set to 192.168.0.1

All comments

CRobGauth

How are you creating a seperate subnet?

Do you have a second router?

If so, the routers need static routes to point to each other to make this work.

hz101

Thank you for lending a hand here. I have been puzzled by what is going on. I used to have a router with IP 192.168.0.1. Now FiOS-G1100 has 192.168.1.1. I have changed its usbnet mask to 255.255.254.0.

Those devices use DHCP. When I connect it to the rotuer via an Ethernet cable, it gets a 192.168.1.x address. When it is switched to Wi-Fi, it uses the old address 192.168.0.x. I do not have problem with it as long as it works. Unfortunately, it does not.

CRobGauth

Why not just keep subnet mask to 255.255.255.0?

And then everything should be on the same subnet and no issues at that point.

hz101

That was the case. I could not get connect to the devices using Wi-Fi even though they are using DHCP, so I changed the mask to 255.255.254.0.

hz101

I am very sorry but I have just realized the Ethernet IP4 and the Wireless IP4 have different configurations. Ethernet IP4 was using DHCP, but the Wireless IP4 was using a fixed IP. That was the casue of the problem. The problem has been solved. I can access the device now.

I would still love to know why the router shows there the device with IP 192.168.0.x, but my computer cannot connect to it.

tns2

@CRobGauth wrote:
Why not just keep subnet mask to 255.255.255.0?
And then everything should be on the same subnet and no issues at that point.

When you want to use both 192.168.0.x and 192 168.1.x ip addresses and have both subnets talk to each other then the correct mask is 255.255.254.0. But in this case the use of these addresses was a mistake.

Child Item