Unable to commission Thread devices through Matter

[fostergorman]

Describe the bug A clear and concise description of what the bug is.

I'm currently working on a Matter hub that uses both WiFi and Thread. The WiFi part is working just fine, but the Thread part has never worked.

I have an open issue with the Matter team already and it seems that the Matter side of things are working as expected.

The problem that we've narrowed it down to is that Matter never receives an ack from the thread end device. I've looked through the logs and see that there are failures, but the information provided doesn't give enough to know if this is from Matter or some other error.

I have noticed that pinging the end devices IP is intermittent and can sometimes stall endlessly.

To Reproduce Information to reproduce the behavior, including:

1. Unsure of the hash (whatever latest is for Docker)
2. nRF52840-dongle
3. Using OTBR docker (see below for how it's run)
4. Single thread leader/router (running in docker on Raspberry Pi) with thread end devices

Docker setup:

docker network create \
	--ipv6 \
	--subnet fd11:db8:1::/64 \
	-o com.docker.network.bridge.name=otbr0 \
	otbr

docker run \
	-d \
	--privileged \
	--name otbr \
	--network otbr \
	--dns 127.0.0.1 \
	-p 8080:80 \
	--sysctl "net.ipv6.conf.all.disable_ipv6=0 net.ipv4.conf.all.forwarding=1 net.ipv6.conf.all.forwarding=1" \
	--volume $device:/dev/radio \
	--volume /run/avahi-daemon/socket:/run/avahi-daemon/socket:ro \
	openthread/otbr \
	--radio-url spinel+hdlc+uart:///dev/radio

sudo ip -6 route add fd11:22::/64 dev otbr0 via fd11:db8:1::2

Using Matter's chip-tool (latest commit) to commission a new device onto the Thread network and Matter fabric.

Expected behavior A clear and concise description of what you expected to happen.

Matter connects to the end device using the IP provided by the Thread network and is able to communicate over Thread.

Console/log output If applicable, add console/log output to help explain your problem.

See attached file: otbr.log