June 1, 20251 yr Author What do you mean by this. I don’t know what you mean. you would need to designate a unfi port and allow the PC device to connect to the vlan at the unif level an give the machine a second ip to talk to teh vlan 60 subnet...
June 1, 20251 yr Community Expert Since we/you are igging into a nuanced VLAN and macvlan setup in Unraid with UniFi, and the issue you're facing is expected behavior due to how macvlan isolation works and VLAN segmentation is enforced.Here's a breakdown of the current situation and potential solution:You've removed bonding/bridging — good.You've set static IPs and created a VLAN interface (eth3.60) — good.Containers like NPM and Jellyfin are reachable internally via their 10.10.60.x IPs — great.You've created a macvlan docker network on eth3.60, which isolates containers at Layer 2 — correct setup.What’s not workingPort forwarding from UniFi to 10.10.60.x (NPM) doesn’t work. That’s normal behavior for this setup.Why this happens:Macvlan networks isolate containers from the host (Unraid itself), and unless traffic enters from an external source within the same VLAN subnet, it gets dropped.UniFi cannot forward from another VLAN or subnet into VLAN60 without a proper Layer 3 route or NAT/firewall rule allowing it.Port forwarding in UniFi from the WAN side into VLAN60 (a non-routed internal network) only works if:There's a route from WAN → VLAN60.The NPM container has a reachable gateway and firewall allows it.Time to add unif routes for cross talk(Hate the new forum...)Option 1: Add a VLAN60 interface to UniFi portGo into UniFi Controller:Find the port NPM is connected to.Add VLAN60 as a tagged VLAN to that port (or native depending on your network setup).Make sure UniFi has a gateway/firewall interface in 10.10.60.0/26.Then set up port forwarding inside UniFi, from WAN to a VLAN60 IP.-What I would prefer you do...Option 2: Put NPM in a bridge or host networkThis allows NPM to listen on the Unraid host's IP instead of an isolated VLAN.Less secure but works for basic setups.Requires moving host web ui porst in setting managementOption 3: Use ipvlan instead of macvlanRequires deleing the docker network...ipvlan allows Unraid host communication with the container.Create Docker network with -d ipvlan and test connectivity.use ipvlan - though I'd recomed staing on macvlandocker network create -d ipvlan \--subnet=10.10.60.0/26 \--gateway=10.10.60.1 \-o parent=eth3.60 \vlan60_ipvlan Edited June 1, 20251 yr by bmartino1 forum gltich C/P notes
June 1, 20251 yr Community Expert in unif go to ports:click on the portthen go to vlansyou need to ensure vlan 60 is taged to a port then we can look at nat rules once your device is on a lan port onteh 10.x.60.x subnet adn can login into npm Edited June 1, 20251 yr by bmartino1
June 1, 20251 yr Author 2 minutes ago, bmartino1 said:in unif go to ports:cl;ick onthe portthen go to vlansyou need to ensure vlan 60 is taged to a port then we can look at nat rules once your device is on a lan port onteh 10.x.60.x subnet adn can login into npmI have port 5 on Vlan 60
June 1, 20251 yr Author This is what is in when I do IP A.ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.07: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 48:f1:7f:9f:ff:8d brd ff:ff:ff:ff:ff:ff8: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 70:85:c2:bf:38:06 brd ff:ff:ff:ff:ff:ff inet 10.10.1.43/24 metric 1009 scope global eth0 valid_lft forever preferred_lft forever9: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 70:85:c2:bf:38:08 brd ff:ff:ff:ff:ff:ff inet 10.10.80.4/24 metric 1010 scope global eth1 valid_lft forever preferred_lft forever10: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ff inet 10.10.60.10/26 brd 10.10.60.63 scope global dynamic noprefixroute eth3 valid_lft 73639sec preferred_lft 62839sec11: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether a0:36:9f:89:2c:5e brd ff:ff:ff:ff:ff:ff inet 10.10.50.11/28 brd 10.10.50.15 scope global dynamic noprefixroute eth2 valid_lft 66699sec preferred_lft 55899sec12: vhost0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500 link/ether 02:e1:d6:c9:90:76 brd ff:ff:ff:ff:ff:ff13: vhost1@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500 link/ether 02:31:e6:8a:b7:d7 brd ff:ff:ff:ff:ff:ff14: vhost2@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500 link/ether 02:36:b6:e0:a5:57 brd ff:ff:ff:ff:ff:ff16: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet 10.253.0.1/32 scope global wg0 valid_lft forever preferred_lft forever18: br-afd014fe03db: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:c5:ce:67:66 brd ff:ff:ff:ff:ff:ff inet 172.20.0.1/16 brd 172.20.255.255 scope global br-afd014fe03db valid_lft forever preferred_lft forever inet6 fe80::42:c5ff:fece:6766/64 scope link proto kernel_ll valid_lft forever preferred_lft forever85: br-a156e7716f54: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:ca:d9:2e:dd brd ff:ff:ff:ff:ff:ff inet 172.18.0.1/16 brd 172.18.255.255 scope global br-a156e7716f54 valid_lft forever preferred_lft forever inet6 fe80::42:caff:fed9:2edd/64 scope link proto kernel_ll valid_lft forever preferred_lft forever192: vhost3@eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500 link/ether 02:f1:c8:8c:fb:23 brd ff:ff:ff:ff:ff:ff
June 1, 20251 yr Community Expert 1 minute ago, Tucubanito07 said:I have port 5 on Vlan 60ok and a device conecte to port 5 ios getting a vlan60 IDwith the client device on vlan 60 gettign a 60.x can it ping the npm ip of the docker in that netwrok?
June 1, 20251 yr Author On this picture you can see that the network 10.10.60.1 on the network settings shows the gateway.
June 1, 20251 yr Community Expert 1 minute ago, Tucubanito07 said:On this picture you can see that the network 10.10.60.1 on the network settings shows the gateway.except vlan 60 is untaged...Observations from ip a:eth3 has an IP of 10.10.60.10/26, which is inside VLAN60.No eth3.60 interface is present, which suggests you’ve given eth3 a native (untagged) IP on VLAN60.If that’s intentional, then VLAN60 traffic is coming in untagged on eth3.Docker may still be isolating NPM from the host if it’s using macvlan.To proceed with Option 1 using UniFi:1. UniFi Port ConfigurationGo into the UniFi Controller:Navigate to Devices → Switch → Port used by Unraid (eth3).Set this port’s profile to All (or a custom profile) that includes VLAN 60 as tagged.OR –If eth3 is already untagged in VLAN60:Make sure the port profile is Native VLAN: 60 with No additional tagged VLANs.This assumes eth3 is native VLAN 60, not tagged.2. UniFi Firewall & Port ForwardingGo to UniFi Controller → Settings → Firewall & Security:Create a port forwarding rule:WAN port → 10.10.60.10:<NPM_PORT> (this is the IP of your NPM container assuming you used a macvlan network with IP in 10.10.60.x)Make sure there’s a firewall rule allowing traffic from WAN to that VLAN.If UniFi doesn’t have a Layer 3 interface in 10.10.60.x, forwarding will not work unless a route exists. You'll need:A UniFi gateway interface (like a VLAN interface) in 10.10.60.1/26.OR configure routing on your unifi to reach 10.10.60.0/26.
June 1, 20251 yr Author root@Tower:~# ip routedefault via 10.10.1.1 dev eth0 metric 1009 default via 10.10.60.1 dev eth3 proto dhcp src 10.10.60.10 metric 1010 10.10.1.0/24 dev eth0 proto kernel scope link src 10.10.1.43 metric 1009 10.10.1.50 dev wg0 scope link 10.10.50.0/28 dev eth2 proto dhcp scope link src 10.10.50.11 metric 1011 10.10.60.0/26 dev eth3 proto dhcp scope link src 10.10.60.10 metric 1010 10.10.80.0/24 dev eth1 proto kernel scope link src 10.10.80.4 metric 1010 10.253.0.2 dev wg0 scope link 10.253.0.3 dev wg0 scope link 10.253.0.4 dev wg0 scope link 172.18.0.0/16 dev br-a156e7716f54 proto kernel scope link src 172.18.0.1 linkdown 172.20.0.0/16 dev br-afd014fe03db proto kernel scope link src 172.20.0.1 linkdown root@Tower:~# docker network lsNETWORK ID NAME DRIVER SCOPE36d755fbde00 bridge bridge local8f758b8ca5d2 eth0 macvlan local1f4c213508b7 eth3 macvlan local89a4970b4075 host host local0d26ff397067 none null locala156e7716f54 proxy-network bridge local
June 1, 20251 yr Community Expert I cna't guirantee that unriad is on nor using vlan 60 as eth3.60 done't exisit as a interface that tagets teh eth3 as a tage vlan for eth3.60this means that unraid is using eth3 as a untaded valn and may be using teh default vlan for cros talk and using vlan id 1 over eth3your unriad netork is still in a misconfigured setting...You haveunif > vlan60 > xyz port 5? > ??? > unriad port 3 > untaged eth3 > dokcer network vlan60_macvlan > jellyfin/npmwhen you needunif > vlan60 > xyz port 5? > ??? > unriad port 3 > taged eth3.60 > dokcer network vlan60_macvlan > jellyfin/npm
June 1, 20251 yr Author If I add the Vlan 60 in unraid it get again the 169.254 ip address. Edited June 1, 20251 yr by Tucubanito07
June 1, 20251 yr Author NPM goes back to not working again.app ] [6/1/2025] [12:54:12 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json[app ] [6/1/2025] [12:54:17 PM] [IP Ranges] › ✖ error getaddrinfo EAI_AGAIN ip-ranges.amazonaws.com[app ] [6/1/2025] [12:54:17 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
June 1, 20251 yr Community Expert 1 minute ago, Tucubanito07 said:I now see this.perfect you need to make sure the docker network is using eth 3.60
June 1, 20251 yr Community Expert docker netowrk inspect vlan60_macvlanverify that the parent is teh nriad eth3.60
June 1, 20251 yr Author So when NPM is on the network. I click on the container and open console. In the console of the container I ping Jellyfin on 10.10.60.3 it is reachable. Now, I am not able to get into NPM because when I try to open the webui it goes to the unraid main ip 10.10.1.43 and I close it and then the NPM 10.10.60.2 opens but the username and password load and can't get it.
June 1, 20251 yr Author root@Tower:~# docker network inspect vlan60_macvlan[]Error response from daemon: network vlan60_macvlan not found
June 1, 20251 yr Author root@Tower:~# docker network lsNETWORK ID NAME DRIVER SCOPE4f62636e657b bridge bridge local9789e862fdbc eth0 macvlan local54fd9caf8252 eth3.60 macvlan local89a4970b4075 host host local0d26ff397067 none null locala156e7716f54 proxy-network bridge localroot@Tower:~# ip routedefault via 10.10.1.1 dev eth0 metric 1009 10.10.1.0/24 dev vhost0 proto kernel scope link src 10.10.1.43 10.10.1.0/24 dev eth0 proto kernel scope link src 10.10.1.43 metric 1009 10.10.1.50 dev wg0 scope link 10.10.50.0/28 dev eth2 proto dhcp scope link src 10.10.50.11 metric 1011 10.10.60.0/26 dev eth3 proto dhcp scope link src 10.10.60.10 metric 1010 10.10.60.0/24 dev vhost3.60 proto kernel scope link src 10.10.60.5 10.10.60.0/24 dev eth3.60 proto kernel scope link src 10.10.60.5 metric 1012 10.10.80.0/24 dev eth1 proto kernel scope link src 10.10.80.4 metric 1010 10.253.0.2 dev wg0 scope link 10.253.0.3 dev wg0 scope link 10.253.0.4 dev wg0 scope link 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-a156e7716f54 proto kernel scope link src 172.18.0.1 172.20.0.0/16 dev br-afd014fe03db proto kernel scope link src 172.20.0.1 linkdown root@Tower:~# ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.07: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 48:f1:7f:9f:ff:8d brd ff:ff:ff:ff:ff:ff8: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 70:85:c2:bf:38:06 brd ff:ff:ff:ff:ff:ff inet 10.10.1.43/24 metric 1009 scope global eth0 valid_lft forever preferred_lft forever9: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 70:85:c2:bf:38:08 brd ff:ff:ff:ff:ff:ff inet 10.10.80.4/24 metric 1010 scope global eth1 valid_lft forever preferred_lft forever10: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ff inet 10.10.60.10/26 brd 10.10.60.63 scope global dynamic noprefixroute eth3 valid_lft 85547sec preferred_lft 74747sec11: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether a0:36:9f:89:2c:5e brd ff:ff:ff:ff:ff:ff inet 10.10.50.11/28 brd 10.10.50.15 scope global dynamic noprefixroute eth2 valid_lft 65240sec preferred_lft 54440sec12: vhost0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500 link/ether 02:e1:d6:c9:90:76 brd ff:ff:ff:ff:ff:ff inet 10.10.1.43/24 scope global vhost0 valid_lft forever preferred_lft forever13: vhost1@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500 link/ether 02:31:e6:8a:b7:d7 brd ff:ff:ff:ff:ff:ff14: vhost2@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500 link/ether 02:36:b6:e0:a5:57 brd ff:ff:ff:ff:ff:ff16: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet 10.253.0.1/32 scope global wg0 valid_lft forever preferred_lft forever18: br-afd014fe03db: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:c5:ce:67:66 brd ff:ff:ff:ff:ff:ff inet 172.20.0.1/16 brd 172.20.255.255 scope global br-afd014fe03db valid_lft forever preferred_lft forever inet6 fe80::42:c5ff:fece:6766/64 scope link proto kernel_ll valid_lft forever preferred_lft forever85: br-a156e7716f54: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 02:42:ca:d9:2e:dd brd ff:ff:ff:ff:ff:ff inet 172.18.0.1/16 brd 172.18.255.255 scope global br-a156e7716f54 valid_lft forever preferred_lft forever inet6 fe80::42:caff:fed9:2edd/64 scope link proto kernel_ll valid_lft forever preferred_lft forever298: eth3.60@eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ff inet 10.10.60.5/24 metric 1012 scope global eth3.60 valid_lft forever preferred_lft forever299: vhost3@eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500 link/ether 02:f1:c8:8c:fb:23 brd ff:ff:ff:ff:ff:ff300: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500 link/ether 02:f1:c8:8c:fb:23 brd ff:ff:ff:ff:ff:ff inet 10.10.60.5/24 scope global vhost3.60 valid_lft forever preferred_lft forever301: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:69:a9:fb:7e brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever305: veth9663fdd@if304: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 56:2f:a0:f9:f7:e1 brd ff:ff:ff:ff:ff:ff link-netnsid 1 inet6 fe80::542f:a0ff:fef9:f7e1/64 scope link proto kernel_ll valid_lft forever preferred_lft forever307: veth1d536b0@if306: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether a2:c0:13:1c:5e:ae brd ff:ff:ff:ff:ff:ff link-netnsid 2 inet6 fe80::a0c0:13ff:fe1c:5eae/64 scope link proto kernel_ll valid_lft forever preferred_lft forever310: veth2dfe967@if309: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 8e:86:0a:89:96:fe brd ff:ff:ff:ff:ff:ff link-netnsid 4 inet6 fe80::8c86:aff:fe89:96fe/64 scope link proto kernel_ll valid_lft forever preferred_lft forever312: vethdc0d864@if311: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 7e:dc:17:1d:05:e8 brd ff:ff:ff:ff:ff:ff link-netnsid 5 inet6 fe80::7cdc:17ff:fe1d:5e8/64 scope link proto kernel_ll valid_lft forever preferred_lft forever314: veth572c057@if313: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 4a:f2:c6:a6:5f:9e brd ff:ff:ff:ff:ff:ff link-netnsid 6 inet6 fe80::48f2:c6ff:fea6:5f9e/64 scope link proto kernel_ll valid_lft forever preferred_lft forever319: veth9f5a927@if318: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 5e:3b:c4:ff:c1:eb brd ff:ff:ff:ff:ff:ff link-netnsid 9 inet6 fe80::5c3b:c4ff:feff:c1eb/64 scope link proto kernel_ll valid_lft forever preferred_lft forever321: veth580a9a7@if320: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 8e:f6:44:10:58:0b brd ff:ff:ff:ff:ff:ff link-netnsid 10 inet6 fe80::8cf6:44ff:fe10:580b/64 scope link proto kernel_ll valid_lft forever preferred_lft forever323: veth935dd38@if322: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 26:4a:25:65:6f:45 brd ff:ff:ff:ff:ff:ff link-netnsid 11 inet6 fe80::244a:25ff:fe65:6f45/64 scope link proto kernel_ll valid_lft forever preferred_lft forever325: veth698f40f@if324: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether da:14:a6:bf:93:c8 brd ff:ff:ff:ff:ff:ff link-netnsid 12 inet6 fe80::d814:a6ff:febf:93c8/64 scope link proto kernel_ll valid_lft forever preferred_lft forever327: vethe541498@if326: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether f6:44:54:b7:1f:ba brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fe80::f444:54ff:feb7:1fba/64 scope link proto kernel_ll valid_lft forever preferred_lft forever329: veth7d24461@if328: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 42:2a:48:f3:d0:6e brd ff:ff:ff:ff:ff:ff link-netnsid 13 inet6 fe80::402a:48ff:fef3:d06e/64 scope link proto kernel_ll valid_lft forever preferred_lft forever331: vethc5e33fc@if330: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether f2:4e:12:62:47:54 brd ff:ff:ff:ff:ff:ff link-netnsid 14 inet6 fe80::f04e:12ff:fe62:4754/64 scope link proto kernel_ll valid_lft forever preferred_lft forever333: veth382ab97@if332: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 7e:70:1c:17:c7:4a brd ff:ff:ff:ff:ff:ff link-netnsid 15 inet6 fe80::7c70:1cff:fe17:c74a/64 scope link proto kernel_ll valid_lft forever preferred_lft forever335: vethcd679a1@if334: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 1a:b8:be:87:30:c4 brd ff:ff:ff:ff:ff:ff link-netnsid 16 inet6 fe80::18b8:beff:fe87:30c4/64 scope link proto kernel_ll valid_lft forever preferred_lft forever337: veth89a714c@if336: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 2a:c4:4d:98:c6:8a brd ff:ff:ff:ff:ff:ff link-netnsid 17 inet6 fe80::28c4:4dff:fe98:c68a/64 scope link proto kernel_ll valid_lft forever preferred_lft forever339: vethc8ad13f@if338: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether aa:96:f2:2c:d2:3a brd ff:ff:ff:ff:ff:ff link-netnsid 18 inet6 fe80::a896:f2ff:fe2c:d23a/64 scope link proto kernel_ll valid_lft forever preferred_lft forever341: veth4bd24ad@if340: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 26:07:50:dd:af:6d brd ff:ff:ff:ff:ff:ff link-netnsid 19 inet6 fe80::2407:50ff:fedd:af6d/64 scope link proto kernel_ll valid_lft forever preferred_lft forever343: veth58ed346@if342: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 2e:a2:bc:b3:ea:89 brd ff:ff:ff:ff:ff:ff link-netnsid 20 inet6 fe80::2ca2:bcff:feb3:ea89/64 scope link proto kernel_ll valid_lft forever preferred_lft forever345: veth4abbbcb@if344: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether ce:93:24:d2:c8:ad brd ff:ff:ff:ff:ff:ff link-netnsid 21 inet6 fe80::cc93:24ff:fed2:c8ad/64 scope link proto kernel_ll valid_lft forever preferred_lft forever347: veth3726035@if346: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether 32:cd:a6:50:5c:f5 brd ff:ff:ff:ff:ff:ff link-netnsid 22 inet6 fe80::30cd:a6ff:fe50:5cf5/64 scope link proto kernel_ll valid_lft forever preferred_lft forever349: veth8bdd5e6@if348: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a156e7716f54 state UP group default link/ether de:b4:2d:f2:52:b8 brd ff:ff:ff:ff:ff:ff link-netnsid 23 inet6 fe80::dcb4:2dff:fef2:52b8/64 scope link proto kernel_ll valid_lft forever preferred_lft forever
June 1, 20251 yr Community Expert ITs clear you doing x when y is needed... I Can't clearly explain like this when its really isn't this hard to make a simple netowrk setting...THe data is in the fourm... -This is why I hate unraid with VLANS!Your hitting layer 2 layer 3 adn unraid is not networking equipemnt...SO I can only advise going another route...if your not going to make the correct vlan and docker network as example on the second post.. as Its clear, the docker network is broken and needs to delete Lets go option 2- this still require 3.60 to guarantee the 10.x.60 subnet...This requires using the host unraid docker network to guarantee cross talk...YOU MUST CHANGE UNRAID WEB UI PORTS! and npm need port 80- and 443....Setting > managment
June 1, 20251 yr Community Expert ...https://forums.unraid.net/topic/190501-unraid-in-unifi/page/2/#findComment-1558327
June 1, 20251 yr Author I agree. This is way to complicated for just getting all the containers on the physical network vlan 60 and then proxy from there. Thank you for all your insight and help on this. Edited June 1, 20251 yr by Tucubanito07
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.