Hi Team,

I'm hoping to get some help RE some Ipv6 which I'm wanting to start getting spun up on my Unraid,

I have configured my Firewall

Enabled IPv6 in Networking (IPv4+IPv6)

I have enabled IPv4 and IPv6 in the Vlans

I have enabled IPv6 Custom Networks on the Docker Interface

However.....

For some reason the Ipv6 option isnt showing for my 101 network but its showing for all others,

So when I'm using a Docker for 101 I see

But any of the others which show Ipv6 I see

Did I miss a step which would prevent me from allocating the IP on the specific Docker Network under 101? I dont know why one would show when the others do not,

I have also attached my Diagnosticglados-diagnostics-20260102-1252.zip if needed

does you dchp server for ipv6 ...

using slacc and RA?

DHCP is turned on however I typically allocate the IP's manually when I set things up so I can reserve the IP's vs having them shift around

I have SLAAC disabled on all of them

Currently unraid uses Slacc for ipv6 networks this is why even when statically set your unraid doesn't see the ipv6 in the vlan/docker settings.

Unraid is not seeing the ipv6 dhcp server.

Edited January 2Jan 2 by bmartino1

But they all have the same settings and SLAAC is disabled on all of them why would 101 be any different?

it has to do with unraid networking and how they are setting up and interrupting ipv6.

you esential made a ipv6 ad hock on the urnaid interface when you staticaly assinged the ipv6 address... where unraid now atampts to make a dhcp ipv6 slack ra call and it gets nothing in resopnose over the ipv6 interface. thus it clsoes ipv6 for further networking dhcp and vlan stuff later per the rc inet script....

see feature request:
https://forums.unraid.net/topic/194716-make-multiple-addresses-for-ipv6-possible/#comment-1587770

with out a lot of workarounds and scripting to flush interfaces and staticaly asiging ipv6 address to multiple vlan networks based on the data presented...

as you needs ipv6 dhcp mode in slacc and use ra. Unriad script for their inet and network setup are not seeing nor communicating to make the ipv6 connections. unriad prefers ipv4 due to a networking stabilty bug...

Its just odd when I checked, the 113 network (which is showing with the IPv6) actually had it disabled on the firewall but it shows up,

So the quick fix is to enable SLAAC and then I can select the IPv6 for that vlan?

Just now, brent3000 said:

Its just odd when I checked, the 113 network (which is showing with the IPv6) actually had it disabled on the firewall but it shows up,

So the quick fix is to enable SLAAC and then I can select the IPv6 for that vlan?

that is my understading of it when testing with unfi network settings and ipv6 for unraid.

Ok I can enable it for that VLAN and see,

You mentioned about scripts etc once I make the change did I need to run something to make the interface refresh or re-check the IPv6? I'm running in Mode4

no, that just power users commands. as a workaround.

Example:
https://forums.unraid.net/topic/178033-bmartino1-user-scripts/#findComment-1492333

we can run similar to bring down a interface and let dhcp reactive it or set an ip on the interface.

we would work around this by manually setting the ip to the vlan interface in unraid similar with how I fix the unifi dhcp snooping issues with 2 sides of the same bridge with 2 different macs getting the same ip address.

Edited January 2Jan 2 by bmartino1

example script:

#!/bin/bash

# Configure br0.101 with IPv4 + IPv6

# Run: At First Array Start (Docker must be stopped/starting)

sleep 20

IFACE="br0.101"

# Bring interface down

ip link set "$IFACE" down || true

# Flush existing addresses

ip addr flush dev "$IFACE"

# ---- IPv4 (static) ---------------------------------------------------------

ip addr add 192.168.1.25/24 dev "$IFACE"

# ---- IPv6 (static) ---------------------------------------------------------

ip -6 addr add 2001:db8:101::25/64 dev "$IFACE"

# Enable IPv6 on interface explicitly

sysctl -w net.ipv6.conf."$IFACE".disable_ipv6=0

# Bring interface up

ip link set "$IFACE" up

and

docker network create \

-d ipvlan \

--subnet=192.168.1.0/24 \

--gateway=192.168.1.1 \

--ipv6 \

--subnet=2001:db8:101:100::/64 \

--gateway=2001:db8:101:100::1 \

-o parent=br0.101 \

br0.101-ipv6

Ive made the change but still not seeing any IPv6 details in my dockers on that VLAN

Or would I be able to just add , [IPv6 address] and tyest it?

you would see the ipv6 subnet there as well, this just set the --ip=#### line in the extra parm.
while in theory you could set a ipv6 address there it would be using ipv6 to ipv4 tap to tunnel over ip4 in that state based on the picture.

since you have preserver user defined on. I would remove docker setting checmark for br.101

and create my own docker network to have ipv6 enabled.


docker network create \

-d ipvlan \

--subnet=192.168.1.0/24 \

--gateway=192.168.1.1 \

--ipv6 \

--subnet=2001:db8:101:100::/64 \

--gateway=2001:db8:101:100::1 \

-o parent=br0.101 \

br0.101-ipv6

*without knowing the ipv6 delegation and data I used a semi default from my own...

as essentially the docker network done't have ipv6 enabled.

Check with docker inspect commands

docker network inspect br0.101

Edited January 2Jan 2 by bmartino1
spelling

2 minutes ago, bmartino1 said:

as essential the docker network done't have ipv6 enabled.

Yes I found that out the hard way that enable of IPv6 in Networking dosnt enable it on Docker until you check the box But thats the funny thing, the Docker page is missing the option for 101 but all others are showing even when SLAAC is disabled,

Just now, brent3000 said:

Yes I found that out the hard way that enable of IPv6 in Networking dosnt enable it on Docker until you check the box But thats the funny thing, the Docker page is missing the option for 101 but all others are showing even when SLAAC is disabled,

the inet script by unriad din't detect ipv6 comunication and thus ran teh compabilty bug patch to force ipv4 for docekr networks.

you have to not let unriad define this and manualy run commands to set the interface ip and make the docker network.

again unraid docekr setting didn't see ipv6 use docker network inspect it will say ipv6 disabled ... this is what your fighitng...

Also I think I just fixed it... Or I broke something else,

I found that my Network settings for 101 was both set to Auto but the rest had None on the interface, switched it and now under Docker I see the option to assign the IP range now, (which oddly enough Unraid only supports /120 not higher)

So to validate I dont enter the IPv6 in the Fixed address box like the example text shows I need an extra para?

Edited January 2Jan 2 by brent3000

correct as now when docker starts unraid will make the network based on setting defiened in the config.



as such with user defined. we can now run terminal comand such as:

docker network create \
-d ipvlan \
--subnet=192.168.1.0/24 \
--gateway=192.168.1.1 \
--ipv6 \
--subnet=2001:db8:101:100::/64 \
--gateway=2001:db8:101:100::1 \
-o parent=br0.101 \
br0.101-ipv6

To make the docker network with the ipv6 data.

Note the parent interface this needs a ipv6 address. you must fill in the ipv data here for the network.

then your dockers in the template can use ipv6

3 minutes ago, bmartino1 said:

correct as now when docker starts unraid will make the network based on setting defiened in the config.

haha Yes I noticed I missed this box Fixed now and has the IP range in it,

3 minutes ago, bmartino1 said:

then your dockers in the template can use ipv6

So using the template, (Sorry I dont use the scripting much I'm a GUI kinda guy ) do I follow the example below and use a , between the IP's or does this support one or the other when setting an IP?

So would it be x.x.x.x, xxxx:xxx:xxx::x or do I always need add a custom config?

Edited January 2Jan 2 by brent3000

12 minutes ago, brent3000 said:

haha Yes I noticed I missed this box Fixed now and has the IP range in it,

So using the template, (Sorry I dont use the scripting much I'm a GUI kinda guy ) do I follow the example below and use a , between the IP's or does this support one or the other when setting an IP?

So would it be x.x.x.x, xxxx:xxx:xxx::x or do I always need add a custom config?

Correct so now in the fixed ip in the docker temple you can comma separate it but add a static ipv6 address here for that docker to be statically assigned to.

as you have user define enabled the docker ipv 6 should be saved across reboots. You apear to be golden and setup corectly now. UNriad and vlans can be problematic. it usualy statis withteh ipv6 dhcp server and slacc based on the default shiped inet script.

So I thought I was on a roll but when I went to test it the command did split the IP's correctly it seems

However all my dockers pre-setup work, any new one (I Was trying Firefox to test it and it keeps failing)

Would this be that command you mentioned I need to run to fix this? Its all entered in the GUI but is something 'not' configured and still needs that CLI run for any new IPv6 vlan I added?

22 minutes ago, bmartino1 said:

docker network create \
-d ipvlan \
--subnet=192.168.1.0/24 \
--gateway=192.168.1.1 \
--ipv6 \
--subnet=2001:db8:101:100::/64 \
--gateway=2001:db8:101:100::1 \
-o parent=br0.101 \
br0.101-ipv6

Edited January 2Jan 2 by brent3000

un checking hte box and saving then rechecing the box enbled it with slaccc and the interface having a ipv6

that checkbox esetal runs this script to make teh defautl dcoker netwrok br0.101

docker network create \ -d ipvlan \ --subnet=192.168.1.0/24 \ --gateway=192.168.1.1 \ --ipv6 \ --subnet=2001:db8:101:100::/64 \ --gateway=2001:db8:101:100::1 \ -o parent=br0.101 \ br0.101-ipv6

to much back and forth

the forum can't keep up and I don't know what your referencing. seeing @ mame here wanting to jump in?

Images fixed in edit now

the error say it all. this tells me the br0.101 doesn't have a ip route and may not have a ipv4 address added to it to communicate to the 10.x address you have.

IDK why that is.

if you run ip a
does teh br0.101 have a ipv4 address as well?

if you run iproute

do you see a route for that subnet 10.x network for br0.101 ?

that would be the networking gotcha at this point.

5 minutes ago, bmartino1 said:

if you run ip a
does teh br0.101 have a ipv4 address as well?

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

6 minutes ago, bmartino1 said:

iproute

Command not found?

Now its giving me a more generic error

Can confirm my other docker's which was done before and already installed, working fine no internet issues

Edited January 2Jan 2 by brent3000