On 2023-07-18 11:05, Daniel Bauer wrote:
Thanks a lot everybody for the very valued input!
Am 18.07.23 um 02:10 schrieb Lew Wolfgang:
Daniel said he configured the cameras for static IP. IIRC. I've got mine (same brand) for DHCP from my Zyxel router.
But there's also a setting there for DNS. It can be "Auto" or "Static". Mine is auto, how about yours, Daniel?
Hm. So I went again to the cameras web-interface. In fact there is a fixed IP-adress, BUT also DHCP was activated (this is only visible if you click a button, so I haven't seen it before).
Ohhh.
I changed this to "static" and rebooted the camera: success.
:-))
Just to be sure, connected from the mini-pc I changed back to DHCP - reboot did /not/ work. Changed again to "static" - reboot works.
Did the same on the laptop - camera reboot worked no matter if that camera setting was DHCP or static...
Maybe you have a dhcp server running in the laptop for some forgotten reason ;-)
So now I changed that in all cameras to static and hope my problem is solved...
What I still don't understand is why it works on the laptop with that camera-setting to DHCP, but not on the mini-PC. With my extremely limited knowledge I just typed "DHCP" in Yast software search, and see that laptop and pc have the same packages installed. They must be with default values because I never changed anything in these things...
Well, I'll see next Sunday what happens. If it didn't solve the problem I'll annoy you with another message here :-)
as root in a terminal: systemctl status dhcp[tab][tab] Also, dnsmasq can do it.
Thanks again for all the help!
Welcome. An intriguing problem. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)