3 minutes ago, bmartino1 said:

perfect this tells me that you have a unraid docker network that is using and on vlan 60

Assuming you ran:

docker network create -d macvlan \

--subnet=10.10.60.0/26 \

--gateway=10.10.60.1 \

-o parent=br3.60 \

--ip-range=10.10.60.32/27 \

vlan60_macvlan

Now its on to editing the dockers tempalte to the new docker network in the drop-down list.

Please edit npm and select custom vlan60_maclan

you will need to set a ip statical here as well

you will need to set the same for jellyfin

I am still seeing this. I don't believe is going to work just yet. 169.254.0.0. Should I have both checked mark or just the br3.60?

Edited June 1, 20251 yr by Tucubanito07

7 minutes ago, Tucubanito07 said:

I am still seeing this. I don't believe is going to work just yet. 169.254.0.0. Should I have both checked mark or just the br3.60?

In truth I don't see how you have br3 and how it was created.

We may need to remove teh br3 interface/ and/or eidt the subnets IP and DHCP pool to the coert info that unif is using.

unraid v7 changed teh web UI. thus user scripts and other settings like termainl comadns. may be need to editeh unraid network configurations now.

heres a user scirpt to run (It may need to bbe a user script to run at first arr start...

fix th br3 interface ips

#!/bin/bash

# Wait for network stack to come up
sleep 10

echo "Cleaning up br3 and assigning correct IP to br3.60..."

# Remove IP from br3 if it has one
ip addr flush dev br3

# Optionally take br3 down and up again to be sure
ip link set dev br3 down
ip link set dev br3 up

# Assign static IP to br3.60 (VLAN 60)
ip addr flush dev br3.60
ip addr add 10.10.60.11/26 dev br3.60
ip link set dev br3.60 up

echo "✅ br3.60 now correctly holds IP 10.10.60.11/26"

When I assign NPM to another network I can access it. However, when it is on the newly created docker I can't access it. in NPM I see this.

[app ] [5/31/2025] [8:45:46 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[app ] [5/31/2025] [8:45:51 PM] [IP Ranges] › ✖ error getaddrinfo EAI_AGAIN ip-ranges.amazonaws.com

Just now, Tucubanito07 said:

When I assign NPM to another network I can access it. However, when it is on the newly created docker I can't access it. in NPM I see this.

[app ] [5/31/2025] [8:45:46 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[app ] [5/31/2025] [8:45:51 PM] [IP Ranges] › ✖ error getaddrinfo EAI_AGAIN ip-ranges.amazonaws.com

that normal until you fix unraid network.

br3.60 isn't talking to the unfi vla and getting a dchp address on vlan 60
but br3 is on vlan 1

I aume yo made br3 and asigned it to eth1

given the ip a

pleas runt eh user script to flush br3 adn asing the ip addres to br3.60 the corect interface

2 minutes ago, bmartino1 said:

that normal until you fix unraid network.

br3.60 isn't talking to the unfi vla and getting a dchp address on vlan 60
but br3 is on vlan 1

I aume yo made br3 and asigned it to eth1

given the ip a

pleas runt eh user script to flush br3 adn asing the ip addres to br3.60 the corect interface

I ran it and this is what I got.

ok whats the output of

ip a

docker network ls

ip route

and what does the unraid web UI show

6 minutes ago, bmartino1 said:

ok whats the output of

ip a

docker network ls

ip route

and what does the unraid web UI show

docker network ls

NETWORK ID NAME DRIVER SCOPE

58fd95eefb28 br0 macvlan local

0d9f91b28402 bridge bridge local

bfa58ee9ccb5 host host local

e2b5c5604762 none null local

afd014fe03db proxy-network bridge local

2c0d737c23b6 vlan60_macvlan macvlan local

ip route

default via 10.10.1.1 dev shim-br0

default via 10.10.50.1 dev eth2 proto dhcp src 10.10.50.10 metric 1011

default via 10.10.1.1 dev br0 proto dhcp src 10.10.1.43 metric 1013

default dev br3.60 scope link src 169.254.227.107 metric 1001401

10.10.1.0/24 dev shim-br0 proto kernel scope link src 10.10.1.43

10.10.1.0/24 dev br0 proto dhcp scope link src 10.10.1.43 metric 1013

10.10.1.50 dev wg0 scope link

10.10.50.0/28 dev eth2 proto dhcp scope link src 10.10.50.10 metric 1011

10.10.60.0/26 dev br3.60 proto kernel scope link src 10.10.60.11

10.10.60.0/26 dev shim-br3.60 proto kernel scope link src 10.10.60.11

10.10.60.0/26 dev br3 proto dhcp scope link src 10.10.60.10 metric 1400

10.10.80.0/24 dev eth1 proto kernel scope link src 10.10.80.4 metric 1

10.253.0.2 dev wg0 scope link

10.253.0.3 dev wg0 scope link

10.253.0.4 dev wg0 scope link

169.254.0.0/16 dev br3.60 scope link src 169.254.227.107 metric 1401

172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown

172.20.0.0/16 dev br-afd014fe03db proto kernel scope link src 172.20.0.1

ip a

1: 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 forever

2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000

link/ipip 0.0.0.0 brd 0.0.0.0

7: 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:ff

8: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000

link/ether 70:85:c2:bf:38:06 brd ff:ff:ff:ff:ff:ff

9: 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 1 scope global eth1

valid_lft forever preferred_lft forever

10: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br3 state UP group default qlen 1000

link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ff

11: 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.10/28 brd 10.10.50.15 scope global dynamic noprefixroute eth2

valid_lft 80990sec preferred_lft 66545sec

12: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000

link/ether 70:85:c2:bf:38:06 brd ff:ff:ff:ff:ff:ff

13: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 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 brd 10.10.1.255 scope global dynamic noprefixroute br0

valid_lft 48904sec preferred_lft 35593sec

14: 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:ff

15: 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:ff

17: 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 forever

19: br-afd014fe03db: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default

link/ether 02:42:d3:3b:7b:39 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:d3ff:fe3b:7b39/64 scope link proto kernel_ll

valid_lft forever preferred_lft forever

399: eth3.60@eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br3.60 state UP group default qlen 1000

link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ff

400: br3: <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.10/26 brd 10.10.60.63 scope global dynamic noprefixroute br3

valid_lft 86389sec preferred_lft 75589sec

401: br3.60: <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.11/26 scope global br3.60

valid_lft forever preferred_lft forever

inet 169.254.227.107/16 brd 169.254.255.255 scope global noprefixroute br3.60

valid_lft forever preferred_lft forever

OK how does uraid conect and get back to the unfi device to coenct to valn 60?

is br3 tiedt to eth1 ? eth2

what cord where is conecting to unraid (I will ned more info to define a ip router latter. Esentail we need to rebuild teh br3 interface it is not setup corectly. and shoulnd't exisits (was expecting to do this to br0

You apear to have 2 eth nics and wifi. is only 1 nic connected?

dam.. we have a broken ip route...

default dev br3.60 scope link src 169.254.227.107 metric 1001401

...

169.254.0.0/16 dev br3.60 scope link src 169.254.227.107 metric 1401

please run this script. we will need to manual clean the route and fix the interfaces...

#!/bin/bash

echo "=== CLEANING ROUTES AND FIXING VLAN 60 ==="

# Remove all shim bridges and Docker broken routes
ip link delete shim-br3.60 2>/dev/null
ip link delete shim-br0 2>/dev/null

# Flush IPs and bring up only desired interface
ip addr flush dev br3
ip addr flush dev br3.60
ip link set dev br3 down
ip link set dev br3 up

# Assign IP only to br3.60
ip addr add 10.10.60.11/26 dev br3.60
ip link set dev br3.60 up

# Delete default routes to prevent confusion
ip route del default
ip route add default via 10.10.1.1 dev br0

# Clean up broken auto-assigned 169.254.0.0 route
ip route del 169.254.0.0/16 dev br3.60 2>/dev/null

echo "✅ Routing table fixed. Check with: ip route"

4 minutes ago, bmartino1 said:

OK how does uraid conect and get back to the unfi device to coenct to valn 60?

is br3 tiedt to eth1 ? eth2

what cord where is conecting to unraid (I will ned more info to define a ip router latter. Esentail we need to rebuild teh br3 interface it is not setup corectly. and shoulnd't exisits (was expecting to do this to br0

You apear to have 2 eth nics and wifi. is only 1 nic connected?

dam.. we have a broken ip route...

please run this script. we will need to manual clean the route and fix the interfaces...

#!/bin/bash

echo "=== CLEANING ROUTES AND FIXING VLAN 60 ==="

# Remove all shim bridges and Docker broken routes
ip link delete shim-br3.60 2>/dev/null
ip link delete shim-br0 2>/dev/null

# Flush IPs and bring up only desired interface
ip addr flush dev br3
ip addr flush dev br3.60
ip link set dev br3 down
ip link set dev br3 up

# Assign IP only to br3.60
ip addr add 10.10.60.11/26 dev br3.60
ip link set dev br3.60 up

# Delete default routes to prevent confusion
ip route del default
ip route add default via 10.10.1.1 dev br0

# Clean up broken auto-assigned 169.254.0.0 route
ip route del 169.254.0.0/16 dev br3.60 2>/dev/null

echo "✅ Routing table fixed. Check with: ip route"

root@Tower:~# ip route

default via 10.10.1.1 dev br0

default via 10.10.1.1 dev br0 proto dhcp src 10.10.1.43 metric 1013

default dev br3.60 scope link src 169.254.121.232 metric 1001401

10.10.1.0/24 dev br0 proto dhcp scope link src 10.10.1.43 metric 1013

10.10.1.50 dev wg0 scope link

10.10.50.0/28 dev eth2 proto dhcp scope link src 10.10.50.10 metric 1011

10.10.60.0/26 dev br3.60 proto kernel scope link src 10.10.60.11

10.10.60.0/26 dev br3 proto dhcp scope link src 10.10.60.10 metric 1400

10.10.80.0/24 dev eth1 proto kernel scope link src 10.10.80.4 metric 1

10.253.0.2 dev wg0 scope link

10.253.0.3 dev wg0 scope link

10.253.0.4 dev wg0 scope link

169.254.0.0/16 dev br3.60 scope link src 169.254.121.232 metric 1401

172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown

172.20.0.0/16 dev br-afd014fe03db proto kernel scope link src 172.20.0.1

BR3 is only tied to one eth03.

I'm not sure how to porceded as its mutiple nics.

unifi > vlan 60 > 10.10.60.0/26 > ??? > Unriad ethernet 3 > Br3 > br3.60 > vlan60_macvlan > Docker...

This is What's Still Wrong

1. br3.60 has a valid IP (10.10.60.11) but also an invalid fallback IP (169.254.x.x)

This means:

• The kernel thinks no DHCP server responded on br3.60

• But you statically assigned 10.10.60.11 in the script

• Something is still trying DHCP and failing — probably Docker

You have both:

• br3 with 10.10.60.10 via DHCP

• br3.60 with 10.10.60.11 via static

This is likely wrong — you don’t need IPs on both.

The shim-br* interfaces are gone ✅ — good cleanup there!

First Reboot Unriad to reset fome netowrk configurations.

Let’s confirm what you want this port to do:

• br3 (backed by eth3) is tagged with VLAN 60

• It is physically connected to a Unifi switch that:

  • Tags traffic with VLAN 60

  • Provides DHCP for 10.10.60.0/26

Correct so far?

IF YES:

to fix we need unraid to properly have a ip route and to use br3.60
If so, you should only need:

• br3.60 to have DHCP (if you want dynamic)

  • OR 10.10.60.11/26 (if you want static)

• br3 itself should NOT have any IP (just pass-through for VLANs)

AFTER A REBOOT TO DOBULE CHECK!

otherwise script:

Flush br3 and br3.60 and start fresh

script to kill the interfaces

# Flush both interfaces

ip addr flush dev br3

ip addr flush dev br3.60

# Bring interfaces down and up

ip link set dev br3 down

ip link set dev br3.60 down

ip link set dev br3 up

ip link set dev br3.60 up

Assign IP ONLY to br3.60
I recomend static

DHCP:

dhclient -v br3.60

Static:

ip addr add 10.10.60.2/26 dev br3.60

Prevent 169.254.x.x fallback

user script at first array start

# Disable link-local address assignment

sysctl -w net.ipv4.conf.br3.60.autoconf=0

sysctl -w net.ipv4.conf.br3.60.accept_local=0

sysctl -w net.ipv4.conf.br3.60.use_tempaddr=0

Then remove unwanted defualt routes:

ip route del default dev br3.60 2>/dev/null

ip route del default dev br3 2>/dev/null

ip route should show

default via 10.10.1.1 dev br0

with that we will assing or own IP route.

ip route add 10.10.60.0/26 dev br3.60 proto kernel scope link src 10.10.60.2

verify:

ip a show dev br3.60

ip route | grep br3.60

later we may need a script to run at first array start to fix unraid broken netowrk configuartions..

all in one scirpt for first arry stat IF ABOVE COMANDS ARE SUCESSFULL!!!

# Flush both interfaces

ip addr flush dev br3

ip addr flush dev br3.60

# Bring interfaces down and up

ip link set dev br3 down

ip link set dev br3.60 down

ip addr flush dev br3.60

ip addr add 10.10.60.2/26 dev br3.60

ip link set br3.60 up

ip route add 10.10.60.0/26 dev br3.60 proto kernel scope link src 10.10.60.2

ip link set dev br3 up

ip link set dev br3.60 up

ip a show dev br3.60

ip route | grep br3.60

in unraids web ui for br3 click show vlans do you see vlan 60?

1 minute ago, bmartino1 said:

in unraids web ui for br3 click show vlans do you see vlan 60?

I do see vlan60.

Just now, Tucubanito07 said:

I do see vlan60.

perfect, this is just to confirm that unraid is seing the upstream vlan. a reboot and the comands here
https://forums.unraid.net/topic/190501-unraid-in-unifi/page/2/#findComment-1558303

othwerwise we may need to start some aspect of unraid over to fix unraid networking.
(One of the rason I hate unraid as its not easy nor simple to setup vlans...)

IF this still fails we may need to temp shutdown docker and go voer generaic unraid tab and setting to setup non bridge adn non bond

ths was we call the interface dirctly adn not the unraid bridges that are failing here.

I would p[refer a reboot to bring back the shim br or vhost poer your ipa to make sure general unraids inetrc script runs clean to verify ip routes.

1 minute ago, bmartino1 said:

perfect, this is just to confirm that unraid is seing the upstream vlan. a reboot and the comands here
https://forums.unraid.net/topic/190501-unraid-in-unifi/page/2/#findComment-1558303

othwerwise we may need to start some aspect of unraid over to fix unraid networking.
(One of the rason I hate unraid as its not easy nor simple to setup vlans...)

IF this still fails we may need to temp shutdown docker and go voer generaic unraid tab and setting to setup non bridge adn non bond

ths was we call the interface dirctly adn not the unraid bridges that are failing here.

I would p[refer a reboot to bring back the shim br or vhost poer your ipa to make sure general unraids inetrc script runs clean to verify ip routes.

doing a reboot now.

root@Tower:~# ip a show dev br3.60

18: br3.60: <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.11/26 scope global br3.60

valid_lft forever preferred_lft forever

inet 169.254.121.232/16 brd 169.254.255.255 scope global noprefixroute br3.60

valid_lft forever preferred_lft forever

root@Tower:~# ip route | grep br3.60

10.10.60.0/26 dev br3.60 proto kernel scope link src 10.10.60.11

169.254.0.0/16 dev br3.60 scope link src 169.254.121.232 metric 1018

root@Tower:~#

I followed everything you placed on the earlier message.

Do we even need to tell unraid that vlan 60 and not just pass BR3 to the container? would that be easier? Thank you for all your help on this. I have learned a lot so far. I really appreciate you.

Edited June 1, 20251 yr by Tucubanito07

1 minute ago, Tucubanito07 said:

root@Tower:~# ip a show dev br3.60

18: br3.60: <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.11/26 scope global br3.60

valid_lft forever preferred_lft forever

inet 169.254.121.232/16 brd 169.254.255.255 scope global noprefixroute br3.60

valid_lft forever preferred_lft forever

root@Tower:~# ip route | grep br3.60

10.10.60.0/26 dev br3.60 proto kernel scope link src 10.10.60.11

169.254.0.0/16 dev br3.60 scope link src 169.254.121.232 metric 1018

root@Tower:~#

dam the unraid misconfiguartion bug...

you ran the commadns above?

Thanks — that confirms that br3.60 currently has two IP addresses:

10.10.60.11/26 (likely from DHCP)

169.254.121.232/16 (link-local, fallback when DHCP fails)

example you should have a ip route of
10.10.60.0/26 dev br3.60 proto kernel scope link src 10.10.60.2

...something like that

to switch br3.60 to a static IP (10.10.60.2/26) and avoid link-local fallback

You'll want your User Script to:

1. Flush both IPs from br3.60

2. Assign only the desired static IP

3. Add the appropriate route
   

   #!/bin/bash

   # Log for debugging

   LOG="/tmp/setup-br3.60.log"

   {

   echo "=== Setting static IP for br3.60 ==="

   date

   # Flush existing IPs

   ip addr flush dev br3.60

   # Assign desired static IP

   ip addr add 10.10.60.2/26 dev br3.60

   # Bring interface up (if not already)

   ip link set br3.60 up

   # Add static route (usually automatic from IP assignment)

   ip route add 10.10.60.0/26 dev br3.60 proto kernel scope link src 10.10.60.2 || echo "Route may already exist."

   echo "=== Done setting br3.60 ==="

   } >> $LOG 2>&1

Lets also double check. there shouldn't be...

Check for Duplicate IPs

arping -I br3.60 10.10.60.2

i don't think nmap is install on unraid...

nmap -sn 10.10.60.0/26

if this script fails. then I'm not sure where unraid moved or what is causing the br3 to fail to talk adn bridge the connetion so we can try a few things but this would require a comlete unraid network reset. 9Deleting the unrad netowrk config and killing the docker netwroks...

Edited June 1, 20251 yr by bmartino1

This is what I got from the logs.

cat /tmp/setup-br3.60.log

=== Setting static IP for br3.60 ===

Sat May 31 21:51:53 EDT 2025

RTNETLINK answers: File exists

Route may already exist.

=== Done setting br3.60 ===

ip route | grep br3.60

default dev br3.60 scope link src 169.254.3.7 metric 1001018

10.10.60.0/26 dev br3.60 proto kernel scope link src 10.10.60.2

10.10.60.0/26 dev shim-br3.60 proto kernel scope link src 10.10.60.2

169.254.0.0/16 dev br3.60 scope link src 169.254.3.7 metric 1018

Edited June 1, 20251 yr by Tucubanito07

Do we even need Bridge mode? Can we just take off br3 and leave it at eth3?

Correct that the plan.

The software bridges are getting in the way and causing extra network issues.

in unraid going to /boot is the flash drive.

we want to nuke the netwrok config and rebbot this way we start fresh from a unraid default network config (this has been known to fix the network names and small bugs from v6 to v7 with vhost to shimbr0
This will bring eth1 back to a dhcp IP...

Please turn vms off and docker off until this porcess is complete.

Reset unraid docker netowrk to guranteee defautl configurations.

cd /boot/config

rm network*

reboot

this reset unraids to factory default network configurations.

Then at the reboot. lets edit unraid settings and turn off bridge and turn off bond.
leave eth3 settigns alone set eth1 up for your stati ip and other interface connections.

Edited June 1, 20251 yr by bmartino1

Disable Bridging and Bonding (Post-Reboot)

After reboot, go to Settings → Network Settings in the Unraid web UI:

• Disable bonding.

• Disable bridging.

• Assign eth1 a static IP, e.g., 10.10.80.4/24.

Apply and reboot if prompted.

Configure eth3 + VLAN60

Ensure Unraid has VLANs enabled:

• In Network Settings, enable VLANs on eth3.

• Add a new VLAN (ID 60), name it eth3.60, no IP address (unless you want one for the host too).

Set Up Docker macvlan Network on VLAN60

If Docker already has networks that interfere or you renamed interfaces, clear them with:

docker network prune

*With eth3 setup we can now enable docekrs... docker will need to be enabled to prune adn clear docker data...

then make the docker entwork tied to the interface:

docker network create -d macvlan \

--subnet=10.10.60.0/26 \

--gateway=10.10.60.1 \

-o parent=eth3.60 \

vlan60_macvlan

finaly double check unraid configurations:

ip a show dev eth3.60

ip route

docker network ls

docker network inspect vlan60_macvlan

I removed the network configuration like you said and took off bond and bridge for interfaces. Now, when I open NPM container and Jellyfin again by going to their new ip address, I can get to the containers. But when I setup the correct IP address in NPM and also on Unifi port forwarding, it does not forward the traffic to the container on the same network.

When I switch back to my proxy network in unraid ip network 172.18.x.x and I change the port forwarding in unraid to forward to NPM, then it works. But on the 10.10.60.x network in unifi it does not. This is so annoying. I know what I am doing network wise and still nothing. GGRRR

2 hours ago, Tucubanito07 said:

I removed the network configuration like you said and took off bond and bridge for interfaces. Now, when I open NPM container and Jellyfin again by going to their new ip address, I can get to the containers. But when I setup the correct IP address in NPM and also on Unifi port forwarding, it does not forward the traffic to the container on the same network.

When I switch back to my proxy network in unraid ip network 172.18.x.x and I change the port forwarding in unraid to forward to NPM, then it works. But on the 10.10.60.x network in unifi it does not. This is so annoying. I know what I am doing network wise and still nothing. GGRRR

I believe you. yes, this can be frustration. Thank you for starting the unraid network over to make sure it's back to the base.

I assume ip a shows eth3 and eth3.60 and your docker network ls
and docker network inspect vlan60_macvlan
shows eth3.60 as its parent

running the commands above.

ip route shows a dev route for 10.x.x.x to eth3.60

I removed the network configuration like you said and took off bond and bridge for interfaces. Now, when I open NPM container and Jellyfin again by going to their new ip address, I can get to the containers. But when I setup the correct IP address in NPM and also on Unifi port forwarding, it does not forward the traffic to the container on the same network.

This is expected as only devices in that valn can talk to that npm docker.

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...

THis is good this means unriad and vlan60 are coretly configured. get a device to connect to npm one on the vlan 60 may be a b it challenging.