[Support]: Unraid, Frigate Container, and Multiple Networks (VLANs)

[VanGoghComplex]

Describe the problem you are having

I'm trying to migrate my NVR setup from Blue Iris (which requires a Windows VM) to Frigate. I've been able to set up a boilerplate config.yml and launch Frigate without error, visit the web UI, etc.

My problem is that I have a separate VLAN for my cameras, which are PoE IP cameras. My server, a Dell T430, has two NICs. One is connected to my home network (main VLAN) and the other is connected to my camera VLAN in my managed switch. This may be more a Docker question than a Frigate question, but how do I get Frigate to serve its web interface on my Home VLAN and pull camera feeds from the camera VLAN? In my Blue Iris Windows VM, I've just got two virtual NICs, one of which is being passed from the host's physical NIC that's attached to the camera network.

Version

0.13.2-6476F8A

Frigate config file

cameras:
  Front_Door: # <--- this will be changed to your actual camera later
    enabled: True
    ffmpeg:
      inputs:
        - path: rtsp://10.1.2.10:554/rtsp
          roles:
            - detect
    detect:
      enabled: False # <--- disable detection until you have a working camera feed

Relevant log output

2024-03-27 20:26:27.281818297  [2024-03-27 20:26:27] frigate.video                  ERROR   : Front_Door: Unable to read frames from ffmpeg process.
2024-03-27 20:26:27.281971169  [2024-03-27 20:26:27] frigate.video                  ERROR   : Front_Door: ffmpeg process is not running. exiting capture thread...

FFprobe output from your camera

10.1.2.10: No such file or directory

Frigate stats

No response

Operating system

UNRAID

Install method

Docker Compose

Coral version

CPU (no coral)

Network connection

Wired

Camera make and model

Amcrest PoE IP camera

Any other information that may be helpful

I've got my camera network set up as a custom IPV4 network in Unraid's Docker config page, and am able to assign Frigate to that network type when starting. It doesn't seem to be able to see the cameras from there either based on the log, but aside from that, I can't reach the web UI that way either.

[NickM-27]

You'll need to run frigate in docker compose. Assign it to both networks and give it an IP address in the camera vlan and the default network

[VanGoghComplex]

Thank you! I haven't used compose yet but will read up and give it a shot.

[JFalti]

@VanGoghComplex I am asking myself the same question as I also want to set up Frigate on Unraid with this VLAN scenario. The answer sounds reasonable. However, I don't know exactly how it is implemented.
Please give me a hint if you got it working.

[VanGoghComplex]

@JFalti Hey! I finally figured it out with some help from the folks at the Unraid Discord. I needed to create a persistent custom Docker network on my Unraid server with the following command in terminal:

docker network create -d ipvlan --subnet=192.168.0.0/24 --gateway=192.168.0.1 -o parent=br0 cam_net

Your subnet and gateway will be whatever range you've set up on your camera VLAN, and the parent bridge (br0) in the example above will be the bridge you have connected to the NIC physically plugged into that camera VLAN.

After running that command, add the following to Post Arguments in your Frigate container template on Unraid (you'll need to tick the Advanced slider in the top right):

&& docker network connect cam_net Frigate

The normal Network Type and IP settings in the template will be your home network, the one you access Frigate's webpage on. The custom docker network you created and referred to in the post args will be your camera VLAN.

Hope this helps!

[guyank]

Thanks. That was exactly what I needed to do what you've done. One slight change I had to make was to change Frigate to frigate in the post arguments.