UPDATE - It's going back. I just can't deal with it anymore. Brand new camera replace the old one. It STILL won't take it. Put other router in, it's fine. On top of the horrible interface, I'm DONE. Thanks all for reading and pondering. I know it can't happen, but I'm watching it. NEW CAMERA out of box. Set as static IP before install. Now DHCP.

New to the TP-Link router world. Installed a new AXE4500 this week. I have about 100 devices. Among them are about 10 cameras. I am using 192.168.1.* addressing because the cameras all had static addresses in that range. I start my DHCP at 192.168.1.50. My Reolink cameras were all assigned static IP/DNS addresses of from 192.168.1.10 and up. That's where my software was looking for them. Plugged them into my AXE and fired everything up. EVERY ONE OF THEM was back to DHCP with random addresses. I went in and set them back again. Save. Exit. They work for 15 secs and then they are gone. Back to their DHCP addresses. Plugged the switch with all the cameras into my old router and reset all the IPs again. Static. Save. Exit. login with static ID. Good. Plug them back into my AXE and poof, back to DHCP. I've never seen anything like it. SO, I reserved the IP addresses and tried to move on. ONE CAMERA will not come up. It has a gateway of 0.0.0.0 which is odd. I can logon briefly, but then it dumps me. A ping test and it drops about every 15 secs and then comes back, but never long enough to register with my software.

So, I go back to my old router. No internet, just the router. Set static ips again. Works fine. Can't load software off-line, but ping test is smooth. AXE hates this one camera, but how can a router change static IP settings.

Thanks all. Has made me nuts.