7 minutes ago, brent3000 said:

Looks like it has a bunch of things but looks like its just the mac details

275: br0.101: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000

link/ether d0:50:xx:xx:xx:17 brd ff:ff:ff:ff:ff:ff

Command not found?

Apologies its
ip route

this can also be seen in the gui.
via the routing table:

*more somethign to doble check.

??? did the docker still start with ipv6 i wonder...

docker ps. or the ip address is in uses else where. and docker inspect the network will show the ip in use tied to a docker.

Id reboot unraid to double-check and make sure alots changed and it can be hard to pinpoint sometimes..

Just to show as well, this is on the Docker settings page, all values are entered

Edited January 2Jan 2 by brent3000

1 minute ago, bmartino1 said:

Apologies its
ip route

haha no worries

root@GLaDOS:~# ip route
default via 10.xx.xx.1 dev shim-br0 
default via 10.xx.xx.1 dev br0 proto dhcp src 10.xx.xx.3 metric 1274 
10.xx.xx.0/29 dev shim-br0 proto kernel scope link src 10.xx.xx.3 
10.xx.xx.0/29 dev br0 proto dhcp scope link src 10.xx.xx.3 metric 1274 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
172.18.0.0/16 dev br-8aeec5a8250c proto kernel scope link src 172.18.0.1 linkdown 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown 

4 minutes ago, brent3000 said:

Just to show as well, this is on the Docker settings page, all values are entered

IDK not enough to go off of.

to clarify, are you using the same ip range for both br0.101 and br0.112 ? or are they different.

as unraid doesn't handle ip routes when the same ip is used on multiple interfaces.

@JorgeB thoughts?

Apologies. its late for me. I'm off to bed.

Edited January 2Jan 2 by bmartino1
Data - typo

Just now, bmartino1 said:

to clarify are you using the same ip range for both br0.101 and br0.112 ? or are they different.

They are each different subnets so there is no double ups, this was all working in its Ipv4 world, trying to add the v6 is where its coming un-stuck >_< hahah

My routing table does look abit bare but its been working with v4 so I assume its ok to be abit light on the numbers

Just now, brent3000 said:

They are each different subnets so there is no double ups, this was all working in its Ipv4 world, trying to add the v6 is where its coming un-stuck >_< hahah

My routing table does look abit bare but its been working with v4 so I assume its ok to be abit light on the numbers

defaults are fine, but we may need to add a ip route for the ipv6 subnets.

this can be done via the gui

double check that the vlans have routs to br0 and or to the subnets for traffic. good luck. maybe another mod will be here to assit further.

Well this is odd, rebooted, firefox started no issues, however its being assigned a random Ipv6

Add an IPv6 to the docker,

Load it up and it still gets the same random IPv6 address

Is there a way to validate within the docker the Ip6 is assigned correctly?

Ok more progress, my router had a combined policy and it was using NAT for both v4 and v6 my system is now showing the correct IP, more testing inbound, still cant load it directly using the IP in the address bar as it has a connection problem when it loads the ipv6 directly.

I would assume if it has an IPv6 assigned I can access it from the web UI without a port or is that not the case typically?

Edited January 2Jan 2 by brent3000

10 hours ago, brent3000 said:

Well this is odd, rebooted, firefox started no issues, however its being assigned a random Ipv6

Add an IPv6 to the docker,

Load it up and it still gets the same random IPv6 address

Is there a way to validate within the docker the Ip6 is assigned correctly?

docker inspect command...

docker inspect network br0.101

look for the container name and the ipv4 / ipv6 address