rk1234

OVERALL GOALS: unraid server (6.8.0 rc4) accessible on an untagged LAN network numerous containers accessible only on vlan 1010 getting DHCP via pfsense (preferred) or Docker numerous containers accessible only on vlan 1020 getting DHCP via pfsense (preferred) or Docker numerous containers accessible only on vlan 1050 getting DHCP via pfsense (preferred) or Docker several vms on one or more of the above vlans getting DHCP via pfsense numerous appliances/IoT devices/etc on one or more of the abvoe vlans getting DHCP via pfsense pfsense vm on the unraid server managing all traffic (I'm aware of the 'issues' with not running the firewall on separate hardware) SHORT VERSION OF ISSUES: It appears when a docker container (binhex-lidarr for example) is configured on a vlan (bridge.vlan_number, ie. br0.1020) that a gateway is not set. It also seems the port for the application running in that container is not accessible on that vlan, though I can ping it from that vlan. I get the same result if I set the IP in the docker container settings or use the docker DHCP settings to assign an IP. It seems the only time a gateway is set is when it is set to host. When set to bridged it gets an IP on 172.17.0.x (default docker network) and while it has no gateway it can still route out to the internet (I'm assuming through the unraid server's IP). Can I get a docker container to get its IP/etc from the Pfsense VM? If not, how can I get a gateway/routing handled for the various Docker containers on the VLANs? LONG VERSION: Old server is Proxmox 5.x managed on an untagged LAN network. The WAN NIC is attached to the pfsense VM on it. Pfsense VM uses an ovs bridged port to the LAN NIC. Proxmox 5.x / VMs/ containers all work as expected. I have the LAN NIC plugged into a switch that has all ports grouped (so all vlans can talk to all ports). My new server is Unraid 6.8.0 rc4. I have just the LAN nic untagged and plugged into my switch. I've brdiged the LAN NIC to br0. I've created all the VLANs like I have in proxmox/pfsense, but I'm focusing on vlan 1020 for this example. Under 'network settings' I set 'ipv4 address assignment' to 'none' as I don't want the unraid server being attached/accessible on vlan 1020. I've gone into 'settings - docker' and setup all the VLANs with subnet / gateway / DHCP pool information. I can ssh/ping/etc between old and new servers on the untagged LAN network. I have a VM on unraid on vlan 1050 that gets its IP from pfsense and can access/ping internet/LAN/other VLANs without issue. I've created various containers (will focus on binhex-lidarr). When I set its networking type to 'host' or 'bridged' I can access it and it can access the internet no problem. When set to 'custom: br0.1020' I can only get an IP from the Docker DHCP assignment or if I manually assign an IP under the container settings. That said, it can ping other containers on vlan 1020 that are hosted on proxmox. Opening the console for the container I can see no gateway is set, though I can ping the pfsense firewall and other containers on vlan 1020. However, other containers/vms on vlan 1020 cannot access the binhex-lidarr webgui, which I assume is by design. Without a gateway set on the docker container though, I cannot access it from other networks.