December 31, 2025Dec 31 Hi, i want to move my Dahua home security cameras from recording to the Dahua NVR to the Unraid Frigate Docker Container.I have installed a second NIC in the server and created an isolated camera subnet 10.1.1.1/24.I am able to ping the cameras from the Unraid main page CLI, but fail to connect to them from Frigate .Below an overview of the setup:i see following errors in the system log:Error opening input file rtsp://:@10.1.1.66:554/rtsp.ERROR : Error opening input files: Server returned 404 Not FoundAttached you can find my frigat system logs.the Frigate container seems to be assigned the IP address of my server on the main VLAN, and hence doesn't seem to have an IP address on the camera subnet:Below my docker settings:and my frigate container settings:My frigate container network type is set to host instead of bridge in order to have access to both eth0 and eth1, maybe i need to also configure something else? Or is this not the right approach and should I create a MACVlan or IPVlan? Not sure how to do this though so if someone could provide some guidance please?I also noticed that in the network type options br1 is not shown as an option which leads me to believe that eth1 (br1) is not passed to docker or its containers. is this observation correct?Can someone guide me please what i should do to have docker, and in partical the frigate container, access to both network interfaces?Also can someone explain me please how i can ping from inside the docker / container environment? frigate-logs (1).txt
January 1Jan 1 Author I think i managed to have the frigate container have access to both eth0 and eth1 by following instructions from gemini which told me to define a macvlan for br1 (eth1).i did this by puting in the cli:docker network create -d macvlan --subnet=10.1.1.0/24 --gateway=10.1.1.1 -o parent=br1 cam_networkthen i added the following to the post arguments in the frigate docker container settings:&& docker network connect cam_network frigateNow frigate seems to have an IP address both on the bridge network and the cam_network.In order to be able to pign my camera, i first had to install the ping utility in the frigate container, as it seemed to not have it by default, i did so by following these instructions i.e. putting following commands in the CLI:docker container exec -it frigate bashapt updateapt install iputils-pingexitthen pinging the camera from frigate via the cli gave the following result:the errors in frigateError opening input file rtsp://:@10.1.1.66:554/rtsp.ERROR : Error opening input files: Server returned 404 Not Foundstill persist though...Anyone has an idea what i might strill be doing wrong? Edited January 1Jan 1 by rernst
January 1Jan 1 Author Solution turned out that the URL structure for my dahua camera needed to be different than was suggested by default by frigate;i had to use:rtsp://admin:password@ip_address:554/cam/realmonitor?channel=1&subtype=0For anyone interested in the full solution / steps by steps to have my cameras work with frigate in a dual NIC setup, see solution
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.