Having fought for several days with this, I'd thought it would be worth sharing while it's still fresh in what's left of my mind:
Problem:
- OpenWRT router running latest available version (25.12) and Luci UI.
- IP cam that I want hardwired-only (Ethernet).
- Cam must have no access to internet or rest of LAN.
- Cam must only be accessed directly by the NVR software.
- Software (NVR and reverse proxy) run as docker containers on server PC.
- Any other LAN device (laptop, phone) must be able to access the NVR only via the reverse proxy.
Network topology:
- Cam is plugged physically in lan1 port on router.
- Server is plugged physically in lan3 port on router.
- The problem above basically means we need two tagged VLANs, one for regular LAN devices, and one just for NVR and camera.
Configuring the VLANs in OpenWRT:
Before anything else: try doing the next batch of configs from wireless if possible not Ethernet, in case you mess up and lose wired connectivity to the router.
- Go to Network > Interfaces > Devices and press "Configure" for the bridge that holds your router ports. This will typically be called "br-lan".
- Go to the "Bridge VLAN filtering" tab and check "enable Vlan filtering".
- Press the "Add" button twice to get two VLANs.
- First VLAN: set id=1, check "local", mark lan1=off (not member), lan2=untagged, lan3=tagged (also primary), lan4=untagged. You can use any ID but "1" is traditional for the base LAN network.
- Second VLAN: set id=100, check "local", mark lan1=untagged, lan2=off, lan3=tagged, lan4=off. Again, you can use any ID, but it's traditional to avoid numbers under 10 because they're typically used for core VLANs.
- Case in point, please note that my router has two physical NICs, one for LAN ports 1-4 and one for WAN, so I have a separate br-wan device just for wan. But some routers only have one physical NIC so they only have one bridge that covers both lan1-4 and wan ports. On these routers when you get to the filtering tab you will find two VLANs (1 and 2, typically) already set up. If this is the case add the VLAN 100 and modify VLAN 1 as above and mark wan as off in 100.
- After you press "save" you will notice two new virtual devices called "br-lan.1" and "br-lan.100" type VLAN 802.1q have appeared in the device list.
- Do not apply modifications yet. First go to Network > Interfaces, edit the "lan" interface and switch it from device "br-lan" to device "br-lan.1", otherwise you may lose connectivity to router if you're on Ethernet.
- If you've applied changes early and lose connectivity, don't panic, just wait. In recent OpenWRT versions after 90s without confirmation from the UI the router will automatically rollback the last changes.
If all went well and you're on wireless or one of the untagged Ethernet ports (lan2 or lan4) you should have retained connectivity to the router and wireless devices.
Configuring the NVR network in OpenWRT:
- Go to Network > Interfaces, click "Add new interface".
- Call it "NVR", protocol "static address", device "br-lan.100".
- Next, edit it and set up your desired IPv4 address and netmask.
- You MUST go to "firewall settings" and use the "custom" field to add a new "NVR" zone. alternatively you can go to Network > Fireall, create the NVR zone there, and choose it here.
- Enable DHCP if you want.
- If you do, please note that some routers bind dnsmasq only explicitly to select interfaces. Please check under Network > DHCP > dnsmasq > Devices & Ports and if "non-wildcard" is checked you will have to add "NVR" to the "Listen interfaces" to actually get DHCP services on that network.
- Under Network > Firewall you should have a zone called "NVR". Set input/output/forward to accept/accept/reject.
- Under Network > Firewall > Traffic rules you have to add a new rule, calld it "NVR DHCP", that says that protocol UDP, source zone "NVR", destination "device (input)", destination port 67, action "accept", and under advanced restrict address family to IPv4. Traffic rules have priority over zone configuration so DHCP will work no matter how you fuck up your zone access.
- We will be skipping DNS because we don't want the NVR network to benefit from any. But if we did we'd be doing the same we did for DHCP (got to Network > DNS to enable explicitly on NVR interface, and add a traffic rule for it).
Configuring the camera:
- Plug the camera into port lan1, it should pick up a DHCP address on the network you've defined for interface "NVR".
- In order to be able to access that IP from your regular LAN to configure the camera with your phone you'll have to temporarily add the "NVR" zone to the list of forward zonez of the "lan" zone.
- Would probably be a good idea to either configure the camera to a static IP or give it a static DHCP assignment based on the Ethernet MAC, so you know where to reach it from the NVR software.
- Remember to remove the "NVR" zone from the lan's zone forwards when you're done.
Configuring the server for tagged VLAN connectivity:
- Your server (port lan3) was marked for tagged VLAN connectivity in OpenWRT but it doesn't (yet) actually use tagged connections. We have to fix that or it won't be reachable.
- Feel free to mark lan3 as "untagged" on VLAN 1 to connect to it while you change the settings, but keep in mind that direct console access may be needed if you fuck up.
- My server runs Debian so configuration basically runs down to loading module 8021q (and adding it to /etc/modules just in case, although this should be largely automated), and editing /etc/network/interfaces. Feel free to adjust the example below to your needs:
# this will bring up eth0 but leave it unconfigured, merely as a support carrier for the VLANs
auto eth0
iface eth0 inet manual
# this will set up VLAN ID 1 and tell it to use DHCP
auto eth0.1
iface eth0.1 inet dhcp
# this will set up VLAN ID 100 with a static address
auto eth0.100
iface eth0.100 inet static
address 10.234.100.2/24
Configuring docker networks and containers:
- Remember I said the proxy and the NVR are running in docker containers. If you haven't done anything fancy with them before, you were probably using
ports: to expose a port for the proxy and one for the NVR on the host's LAN IP, and pointing the proxy to the NVR.
- First, we will want to make an ipvlan or macvlan docker network that will use the eth0.100 interface. Containers that use this network will be placed in the NVR network/zone, and have their communications tagged with VLAN ID 100. Feel free to customize the network range. You can use either ipvlan or macvlan, the latter is not very useful since docker can't do DHCP. Note the use of
aux-address to reserve the IP you've assigned the camera, in case there's potential overlap with the range you choose for automatic allocation. It's essential that you use the eth0.100 interface as parent.
docker network create --driver ipvlan \
--ip-range=10.234.100.97/27 --subnet=10.234.100.0/24 --gateway=10.234.100.1 \
--aux-address 'cam1=10.234.100.10' \
-o parent=eth0.100 nvr-vlan
- We also need a bridge network that will allow the proxy to see the NVR container, because once the NVR container is placed on the NVR network on the VLAN ID 100 it won't be reachable directly by the proxy.
docker network create --driver bridge \
--opt com.docker.network.bridge.name=br-docker-proxy \
--ipv4 --subnet=172.23.1.0/24 --gateway=172.23.1.1 \
proxy-bridge
- Next, in the NVR container compose, join both proxy-bridge and nvr-lan:
services:
nvr:
networks:
nvr-vlan:
proxy-bridge:
hostname: nvr
networks:
nvr-vlan:
external: true
proxy-bridge:
external: true
- Also in the proxy container compose you will want to join the proxy-bridge network.
- Remove the
ports: directive from the NVR container, it doesn't serve any purpose now. Containers on ipvlan/macvlan are reachable by their native port assignments on the networks they've joined.
- Please note the
hostname: nvr in the NVR compose, that's the name you will have to use in the proxy configuration to reach the NVR. Docker will supply a DNS resolve for this automatically.
- The proxy doesn't need to be on
nvr-vlan. I mean you can, but you need to keep the proxy accessible from the main network so it will keep using ports: as usual.
Bibliography: