New Reolink Wired POE Doorbell Cam ?

Are you setting the DB cam up with a static IP in the 2.X range before you move it over to the other switch? If the DB cam is defaulting to DHCP (which it sounds like it is considering the 50.127 address) then when it moves to the new LAN it won't get an IP and it won't be connectable.

Maybe try the reolink app on the NUC with the camera on the 2.X lan and see if that picks it up.

I just saw the edit to your original comment, are you actually using vlan or just physically separated lans, ie two NIC's in the NUC, one NIC connected to the router through a switch and one NIC connected to the 8 port POE switch with the cameras on it?
Okay, that worked. I can not believe I forgot to try this before. That's how I setup my other cams.

LOL. I am just going to blame it on getting older and forgetful.
 
  • Like
Reactions: David L
When I first was looking into setting up my network I read about adding a second NIC to my BI PC, which I did. But also ended up buying Managed Switches and created a VLAN network with pfSense as my Router.

Having two separate Subnets on the PC works, Except if the PC is hacked, they will have access to both Subnets. What I do on my BI PC is keep the PC totally Off the Internet. One NIC is connected to my CAMERA VLAN on one of my Managed Layer 2/3 switches, which that VLAN does not have Internet access via my pfSense Router Rules...the router blocks the "outside world" your quote :)

My second NIC is also connected to a Managed Switch which 'Can' have Internet access, but Only to update BI. I control this at the managed switch by turning On the gateway. So my switch would have to get hacked in order for someone to get to my BI PC and the Cameras.

I know this is an extra step, but only takes a minute for me to turn On/Off, plus how often do we update anyway? I will also update Windows too when I do this every few months.

I allow Home Assistant access to the BI PC to get notifications of triggered events, which I get on my Home Assistant Phone App. Again just another Rule set in the pfSense Router. I can see Live fed also through Home Assistant.

The above works for me...if anyone has a better way, please chime in, I am all ears...
Yeah I had a managed switch before. But they are to expensive, take up space and over kill for what I need.
My Asus 88 pro helps to stop the hacking.
Besides there is not any info of interest on my pc for anyone.

Now if you hack my phone and app passwords, you are in like flint
 
  • Like
Reactions: David L
^^^ Glad you got her going...

I am old school, rarely use DHCP, well use is for some of my WiFi devices. I have a spreadsheet of my static IPs...
 
  • Like
Reactions: vandyman
Yeah I had a managed switch before. But they are to expensive, take up space and over kill for what I need.
My Asus 88 pro helps to stop the hacking.
Besides there is not any info of interest on my pc for anyone.

Now if you hack my phone and app passwords, you are in like flint
So true, so many people don't realize they are walking around with a very hackable Portable PC in their pockets/hands. Amazing how ignorant and trustworthy everyone is with their phones.
 
  • Like
Reactions: vandyman
^^^ Glad you got her going...

I am old school, rarely use DHCP, well use is for some of my WiFi devices. I have a spreadsheet of my static IPs...
DHCP reservations is exactly what your spreadsheet with static IP's is doing, but instead of having to wrangle each device manually the router does it for you. Of course this only works if you allow the cameras access to a router and don't have them physically separate on a non-routed network.
 
DHCP reservations is exactly what your spreadsheet with static IP's is doing, but instead of having to wrangle each device manually the router does it for you. Of course this only works if you allow the cameras access to a router and don't have them physically separate on a non-routed network.
Difference is, the manual Static devices still work when router goes down...they are not dependent on a Router's DCHP Server Static Mapping...

Don't get me wrong, I use Static Mapping on several of my WiFi devices that cannot set Static IPs. Those IPs also go in my IP Spreadsheet.

Again, I am old school, ran several LANs for work. Only problem with Static IPed devices is when someone plugs in a retired device that has a Static IP and causes a conflict. Searching for that device can be alot of fun on a large network...

My home network is small and easily manageable...I have 5 level 2/3 managed switches, 6 VLANs Even though I don't use level 3 routing on my switches, I could which would allow me to route even if my main router went down.