Hi,

 

i'm trying to use Matter server on docker with Home assistant but event after enable IPV6 it's doesn't work

 

For informations Ha with matter in a VM perfectly work, but i want a docker container not a VM.

 

This is my configuration :

 

- Unraid 6.12.14

- Unifi udm pro with IPV6 Enabled

 

I already execute this command :

 

sysctl -w net.ipv6.conf.br0.accept_ra=2
sysctl -w net.ipv6.conf.br0.accept_ra_rt_info_max_plen=64

ip6tables -A FORWARD -i br0 -o br0 -j ACCEPT

 

Interface :

 

 

Routing table :

 

 

Docker :

 

 

Unifi Network :

 

 

Matter server container :

 

 

Thanks for the help

Matter server must in Network mode : host.

Your HA in VM or docker ?

Nop the matter server need to be in br0 and in Host it’s doesn’t work.

 

and i dont use a vm, read my post…

Edited December 14, 20241 yr by JamesAdams

Need to know your setup and what your tryign to acomplish?

HA a VM or Docker

Matter a VM or Docker.

since Mater is a Dokcer did you folow there support adn infor in the overview?

 

more info on the github page as well:
https://github.com/home-assistant-libs/python-matter-server

what is the ouput of systemctl -p

root@BMM-Unraid:~# sysctl -p
kernel.pid_max = 4194304
fs.inotify.max_user_watches = 524288
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 65536 16777216
net.ipv4.ip_forward = 1
net.netfilter.nf_conntrack_max = 131072
root@BMM-Unraid:~# 

^-Example.

as ipv6 forwariding is required to fix some things.
as it apears your figiting vlan bridgiin and ip routes on unraid where that vlan trunking needs to be done at a physical switch side.

ip6tables -A FORWARD -i br0 -o br0 -j ACCEPT

not supriosed thoese comands didn't work due to vlans.

sysctl -w net.ipv6.conf.br0.accept_ra=2
sysctl -w net.ipv6.conf.br0.accept_ra_rt_info_max_plen=64

https://github.com/home-assistant/core/issues/115361

Quote

Re networking being an issue, my router is slightly older at this point (it's a D-link DIR-882), could that be a potential issue?

HA is running in host mode. Is there particular configuration you're meant to do on unraid to prepare it for thread? I googled those two settings (haven't heard of them before), and ran sysctl -a on both the unraid machine and the raspberry pi. Unraid has net.ipv6.conf.wg0.accept_ra = 1
net.ipv6.conf.wg0.accept_ra_rt_info_max_plen = 0
(it doesn't have wlan0)

The raspberry pi has
net.ipv6.conf.wlan0.accept_ra = 0
net.ipv6.conf.wlan0.accept_ra_rt_info_max_plen = 0

And no, no vlans on my network anywhere.

 

I need to know what your docker setings are as we may too to run other command to allow ipv6 on unifi for matter docker
unraid settings?


Please post a unraid diag...

since this is a mdns issue, I've recently made a docker template for avahi that should be in CA later tonight/tomorrow.
Running avahi docker as host should fix most of the these issues.

since you have vlan if they need to cross net. you can add to the extra parameter

 

--opt parent=br0.2

for vlan support. This will mdns redirect and use mdns traffic over the network

 

 

this is more or less a work around, as unraid runs a premade avahi config. since we can't easily edit avahi conif on unraid. I thought it best to add a docker.

 

Quote

root@BMM-Unraid:~# cd /etc/avahi/
root@BMM-Unraid:/etc/avahi# ls
avahi-daemon.conf  avahi-dnsconfd.action*  hosts  services/
root@BMM-Unraid:/etc/avahi# cat avahi-daemon.conf 
# This file is part of avahi.
#
# avahi is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as
# published by the Free Software Foundation; either version 2 of the
# License, or (at your option) any later version.
#
# avahi is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
# or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public
# License for more details.
#
# You should have received a copy of the GNU Lesser General Public
# License along with avahi; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
# USA.

# See avahi-daemon.conf(5) for more information on this configuration
# file!

[server]
#host-name=foo
#domain-name=local
#browse-domains=0pointer.de, zeroconf.org
use-ipv4=yes
use-ipv6=no
allow-interfaces=eth0
#deny-interfaces=eth1
#check-response-ttl=no
#use-iff-running=no
#enable-dbus=yes
#disallow-other-stacks=no
#allow-point-to-point=no
#cache-entries-max=4096
#clients-max=4096
#objects-per-client-max=1024
#entries-per-entry-group-max=32
ratelimit-interval-usec=1000000
ratelimit-burst=1000

[wide-area]
enable-wide-area=yes

[publish]
#disable-publishing=no
#disable-user-service-publishing=no
#add-service-cookie=no
#publish-addresses=yes
publish-hinfo=no
publish-workstation=no
#publish-domain=yes
#publish-dns-servers=192.168.50.1, 192.168.50.2
#publish-resolv-conf-dns-servers=yes
#publish-aaaa-on-ipv4=yes
#publish-a-on-ipv6=no

[reflector]
#enable-reflector=no
#reflect-ipv=no
#reflect-filters=_airplay._tcp.local,_raop._tcp.local

[rlimits]
#rlimit-as=
#rlimit-core=0
#rlimit-data=8388608
#rlimit-fsize=0
#rlimit-nofile=768
#rlimit-stack=8388608
#rlimit-nproc=3
root@BMM-Unraid:/etc/avahi# 

^- Beta 7 RC1 options...

Its recomned to run it as a custom br to have a configurable instance. if you run as host your able to easliy add the br vlan interfaces...

*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

--You may need to add the ipv6 option per the overview...

as the mater server is more a unraid avahi issues that is fixed by other network like tweaks on the unraid host.

given your vlan segment and setup your most likely having a vlan trunking issue.

Edited December 15, 20241 yr by bmartino1
data - typo

15 hours ago, bmartino1 said:

since this is a mdns issue, I've recently made a docker template for avahi that should be in CA later tonight/tomorrow.
Running avahi docker as host should fix most of the these issues.

since you have vlan if they need to cross net. you can add to the extra parameter

 

--opt parent=br0.2

for vlan support. This will mdns redirect and use mdns traffic over the network

 

 

this is more or less a work around, as unraid runs a premade avahi config. since we can't easily edit avahi conif on unraid. I thought it best to add a docker.

 

^- Beta 7 RC1 options...

Its recomned to run it as a custom br to have a configurable instance. if you run as host your able to easliy add the br vlan interfaces...

*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

--You may need to add the ipv6 option per the overview...

as the mater server is more a unraid avahi issues that is fixed by other network like tweaks on the unraid host.

given your vlan segment and setup your most likely having a vlan trunking issue.

 

Completely useless comment

I take it you didn't try the docker. as again no diag. and per your pictures you have vlan segmenting. mater uses mdns...

6 minutes ago, bmartino1 said:

I take it you didn't try the docker. as again no diag. and per your pictures you have vlan segmenting. mater uses mdns...

You send a comment without read mine, so please stop comment my thread

Solution : sysctl -w net.ipv6.conf.all.forwarding=1

and set matter server in Host

Edited December 15, 20241 yr by JamesAdams

Sorry for coming back to this old topic, but I'm in the same situation. With this post I realized that I even had no IPv6 DNS server in unRAID because my router (FritzBox) had IPv6 not correctly enabled. But I have the same problem. I don't get any errors if I run the matter-server container on br0 but on host it won't work. Where or how to set sysctl -w net.ipv6.conf.all.forwarding=1? Didn't work for the container.

My docker settings:

2 hours ago, sasbro97 said:

Sorry for coming back to this old topic, but I'm in the same situation. With this post I realized that I even had no IPv6 DNS server in unRAID because my router (FritzBox) had IPv6 not correctly enabled. But I have the same problem. I don't get any errors if I run the matter-server container on br0 but on host it won't work. Where or how to set sysctl -w net.ipv6.conf.all.forwarding=1? Didn't work for the container.

My docker settings:

you neeed more then just the forwarding you need the ipv6 ra stuff...

sysctl -w net.ipv6.conf.br0.accept_ra=2
sysctl -w net.ipv6.conf.br0.accept_ra_rt_info_max_plen=64

On 8/12/2025 at 11:28 PM, bmartino1 said:

you neeed more then just the forwarding you need the ipv6 ra stuff...

sysctl -w net.ipv6.conf.br0.accept_ra=2
sysctl -w net.ipv6.conf.br0.accept_ra_rt_info_max_plen=64

Sorry please for beginners. Where to add those then? I'm already annoyed because since I activated IPv6 my internal AdGuardHome redirections stopped working properly...

PLEASE MAKE YOUR OWN POST THEN FOR CONTINUED BACK AND FORTH!!!

you will need to terminal run the commands as seen above. or use a plugin like the user script plugin making a script to run at first array start.

here is a linux user batch script to allow ipv6 across docekrs...

#!/bin/bash

# Delay before starting
sleep 10

#Call Funcition script Apply sysctl settings
apply_sysctl_settings()
{

#Termianl Comands ran
echo "Applying sysctl settings..."
sysctl -w net.ipv6.conf.all.forwarding=1
sysctl -w net.ipv6.conf.br0.accept_ra=2
sysctl -w net.ipv6.conf.br0.accept_ra_rt_info_max_plen=64
#Redis Docker set over commit for memory
#sysctl -w vm.overcommit_memory=1

#Check user script log for info
echo "Verifying sysctl settings..."
sysctl net.ipv6.conf.all.forwarding
sysctl net.ipv6.conf.br0.accept_ra
sysctl net.ipv6.conf.br0.accept_ra_rt_info_max_plen
#Redis docker check
#sysctl vm.overcommit_memory

}

#Execute script after delay...
apply_sysctl_settings

Edited August 15, 2025Aug 15 by bmartino1
data