Cam1: No signal

I believe you need that Default Gateway 192.168.1.254 needs to be in that IPv4 settings box also.
 
  • Like
Reactions: Mikentosh2017
Since the Default Gateway (modem) is showing IPv6, I decided to log into the modem. It appears that the Device IPv4 Address .254 is outside the DHCPv4’s range of .253. Could this cause the modem to switch to an IPv6 address? Should I change the Device IPv4 Address to .222?
 

Attachments

  • 91CDB5DB-6836-400A-82A0-D649A1BB92B7.jpeg
    91CDB5DB-6836-400A-82A0-D649A1BB92B7.jpeg
    2.6 MB · Views: 13
Since the Default Gateway (modem) is showing IPv6, I decided to log into the modem. It appears that the Device IPv4 Address .254 is outside the DHCPv4’s range of .253. Could this cause the modem to switch to an IPv6 address? Should I change the Device IPv4 Address to .222?

In a short answer no. Your router is set to serve IP addresses from the .64 to .253 range, your router is set to .254 which is unusual but fine as it’s outside of the range of addresses that the router will server via DHCP.
 
Since the Default Gateway (modem) is showing IPv6, I decided to log into the modem. It appears that the Device IPv4 Address .254 is outside the DHCPv4’s range of .253. Could this cause the modem to switch to an IPv6 address?
No.
Log in to the router again and where it says (as in your image in post #22) "DHCPv4 end address" is "192.168.1.253", change that to "192.168.1.199" and save it. No need to have a DHCP pool of 149 IP addresses, let .200 to .253 be for YOUR use when assigning static IP's.

Then set things like I said in my post #9:

Default Gateway 192.168.1.254 (router's LAN )​
Computer 192.168.1.222​
Camera 192.168.1.200​
 
In a short answer no. Your router is set to serve IP addresses from the .64 to .253 range, your router is set to .254 which is unusual but fine as it’s outside of the range of addresses that the router will server via DHCP.
Actually, 192.168.1.254 is very common and has been for a long time for the gateway/LAN IP on AT&T DSL, uVerse and even Fixed Wireless, all on the AT&T (Pace) 5268 (suffixes of several versions) modem/router. At least that has been the case here in the SE area of the U.S.

I did think it unusual to have 149 IP's in the DHCP pool though, generally they run .1 to .99 or .49 to .199 at most. I advised the OP to limit the pool to .199 and use .200 to .253 for his static IP's.
 
Last edited:
  • Like
Reactions: Mikentosh2017
Actually, 192.168.1.254 is very common and has been for a long time for the gateway/LAN IP on AT&T DSL, uVerse and even Fixed Wireless, all on the AT&T (Pace) 5268 (suffixes of several versions) modem/router. At least that has been the case here in the SE area of the U.S.

I did think it unusual to have 149 IP's in the DHCP pool though, generally they run .1 to .99 or .49 to .199 at most. I advised the OP to limit the pool to .199 and use .200 to .253 for his static IP's.

I meant unusual for a home router as most all seem to use .1

The managed switches in my house are all configured with these higher addresses, so 251, 252, 253 and 254 for management.
 
I meant unusual for a home router as most all seem to use .1

The managed switches in my house are all configured with these higher addresses, so 251, 252, 253 and 254 for management.
That's true and I understand.

It's just that in his first post he explained his connections shown in the image as "Switch: #2 is going to the camera, #3 to the computer, #5 to the AT&T modem" and that AT&T modem is most likely a modem/router combo, which, in my experience, has a LAN/Gateway IP of 192.168.1.254. :cool:
 
  • Like
Reactions: sebastiantombs
Ok. I’m back in and there’s a video feed. A minute after shutting down 2 days ago I was thinking about opening another camera app. That’s what I did today and it worked. I went back to BI and deleted/installed a camera, like a poster previously recommended. And 1st the color bars then the video feed.

initially I saw the CPU go red (99%) for minutes. Now it settled to 22%. Now it’s taking minutes to Shutdown.
 
Ok. I’m back in and there’s a video feed.
Good news, I guess. So it's working with BI, right?

What are these values now?
  • Default Gateway _ _ _ . _ _ _ . _ _ _ . _ _ _ (router's LAN )
  • Computer _ _ _ . _ _ _ . _ _ _ . _ _ _
  • Camera _ _ _ . _ _ _ . _ _ _ . _ _ _
 
My sentiments too.
I guess the camera isn’t going to show up in ipconfig.
Correct.

It all looks good, the only difference I see and my suggestion is where I said "....let .200 to .253 be for YOUR use when assigning static IP's" and you have the cam at .199.
As long as that cam's .199 is OUTSIDE of the router's DHCP pool and it's set to static in the cam then all is well! :cool:
 
  • Like
Reactions: Mikentosh2017
Correct.

It all looks good, the only difference I see and my suggestion is where I said "....let .200 to .253 be for YOUR use when assigning static IP's" and you have the cam at .199.
As long as that cam's .199 is OUTSIDE of the router's DHCP pool and it's set to static in the cam then all is well! :cool:

I’ll go back in and set the range from 00 to 53.
 
I’ll go back in and set the range from 00 to 53.
00 to 53?
But I'd set the DHCP pool to stop at .199, leaving .200 to .253 for YOUR use as static IP's (as stated in my posts #24 & 37). :cool: