Question Unconfigurable hardware with a different network ID. Easiest fix?

[medic5678]

I bought another camera with a static IP address that is different from my current network's ID. I'm on xxx.xxx.10.x and this is set at xxx.xxx.1.188. I usually pull out my other router, which can access that network ID and I change the camera's firmware to DCHP. Then I move it to my xxx, xxx.10.xx network and when I plug it in , it's assigned an address on that network. When I try to load the xxx.xxx.1.188 address when it's on the xxx.xxx.1.xx router where I can access it, it tells me I need a config tool, which I don't have. I did download the tool it but it still doesn't allow me to access the camera's firmware. So I can't seem to modify that camera to knock out the static address.

One other option is I could change my main network over to xxx.xxx.1.xx but that's a lot of work for one camera. Anyone know of a quick way to solve this?

 

[kanewolf]

I bought another camera with a static IP address that is different from my current network's ID. I'm on xxx.xxx.10.x and this is set at xxx.xxx.1.188. I usually pull out my other router, which can access that network ID and I change the camera's firmware to DCHP. Then I move it to my xxx, xxx.10.xx network and when I plug it in , it's assigned an address on that network. When I try to load the xxx.xxx.1.188 address when it's on the xxx.xxx.1.xx router where I can access it, it tells me I need a config tool, which I don't have. I did download the tool it but it still doesn't allow me to access the camera's firmware. So I can't seem to modify that camera to knock out the static address.

One other option is I could change my main network over to xxx.xxx.1.xx but that's a lot of work for one camera. Anyone know of a quick way to solve this?

Factory reset the camera. Typically it will default to DHCP and will therefore be in the correct subnet.

 

[medic5678]

That's the way it comes from the vendor. there is no reset button or firmware access where I can do that.

 

[lantis3]

What brand/model? You sure there is no reset button? When I setup the old Chromecast, I also could not find it.

Besides, you don't have to mask LAN IP address, no one can access.

Just put full LAN IP addresses, it's easier to read.

 

[medic5678]

Figured it out. Downloaded Palemoon 32 bit browser, that let me access the firmware. Now I've got it by the balls . Thanks.

 

[bill001g]

Glad you fixed this will add another comment if someone finds this is the future.

Although very messy to use long term you can actually have your nic on multiple subnets at the same time.

There is a option to set a secondary IP address. I would only use this to get past some strange restriction because even though it might appear the networks are different they actually overlap and all the ARP and other broadcast messages are all mixed together.

 

[medic5678]

What if you just used 255.255.240.0 for the subnet mask? That would allow xxx.xxx.x10.xxx and xxx.xxx.x01.xxx on the same subnet.

 

[Ralston18]

@medic5678

FYI:

https://www.lifewire.com/what-is-a-private-ip-address-2625970

 

[medic5678]

@medic5678

FYI:

https://www.lifewire.com/what-is-a-private-ip-address-2625970

How is that relevant when I'm talking about expanding the pool of host addresses within my private network?

 

[Ralston18]

As I read and understood the posts you were masking/redacting private IP addresses.

E.g. :

"I bought another camera with a static IP address that is different from my current network's ID. I'm on xxx.xxx.10.x and this is set at xxx.xxx.1.188. I usually pull out my other router, which can access that network ID and I change the camera's firmware to DCHP. Then I move it to my xxx, xxx.10.xx network and when I plug it in , it's assigned an address on that network. When I try to load the xxx.xxx.1.188 address when it's on the xxx.xxx.1.xx router where I can access it, it tells me I need a config tool,"

Not uncommon for posters to do such things when providing "ipconfig /all" results or other similar information that requires IP addresses.

Masking/redacting private IP addresses is not necessary (per the link) and being able to see the full IP address with respect to the three commonly used IP address blocks is helpful when troubleshooting.

That was also noted by @lantis3 in Post #4

Knowing the subnet masking is also important. Sometimes that gets redacted as do macs.

Your network is using the same private IP addresses being used by thousand of other networks - including mine (192.168.1.1, subnet 255.255.255.0).

Very likely that the camera's default IP address was within one of the three ranges and the camera's admin functions would be reachable via any browser. Appears to now be moot anyway....

I reference that Lifewire link just a matter of information for posters and others who read the posts.

There is no need to mask/redact Private IP addresses.

No offense intended.