Comment on How to physically isolate a camera with OpenWRT, tagged VLANs and Docker
possiblylinux127@lemmy.zip 3 weeks ago
This is a bit more complex that it needs to be
Why didn’t you just use the openwrt Firewall? You could’ve just allowed your server to talk to the camera
lemmyvore@feddit.nl 3 weeks ago
I did initially do it with the firewall alone. I created a “br-nvr” device, moved lan1 from br-lan to it, and used br-nvr as the device for the NVR interface and firewall zone, then selectively let my phone and the NVR app from the LAN zone access the camera ports with traffic rules.
Everything else about the interface and zone stayed the same as they are now. (That’s what’s great about the OpenWRT abstractions. )
The one major issue with that approach was that the NVR app is outside the NVR zone and I wanted it in there.
With the NVR app in the same isolated network as the cameras they can do whatever they want in there without needing explicit rules.
But I couldn’t put the NVR docker container into the NVR network, because it lives on a machine on the LAN network, and you can’t have the host machine on one network and a app on it in another network, with a single physical cable… unless you use tagged VLANs.
There are also some potential annoyances in the future if I ever want to move cables around the ports or make more complex setups, the VLAN abstraction makes things easier.
non_burglar@lemmy.world 3 weeks ago
I think you might be misunderstanding the role of a firewall.
Put your camera in another subnet, add rules at the convergence point (the router, in this case), done.
That is effectively what you’re doing with VLANs anyway.
lemmyvore@feddit.nl 3 weeks ago
I want to have a device (the server) present in multiple networks (and multiple different firewall zones) at the same time. I was given to understand I need tagged VLANs for this.
possiblylinux127@lemmy.zip 3 weeks ago
Thanks for the clarification