#OTBR with Multiple IPv6 ULA Networks Breaks Network Communication

1 messages · Page 1 of 1 (latest)

scenic pivot
#

I'm looking for help fixing some problems with my Open Thread Border Router integration. Everything was working fine, then after several power outages, my original thread devices quit working. I added new devices, and they work fine. The problem is that OTBR started using the IPv6 ULA fd1d which it can't communicate with. It can communicate with devices on the original fd16 network. How do I access the OTBR web interface? How do I access the OTBR container? I'm using a HA Yellow device.

sacred island
#

I find this confusing. You write
"I added new devices, and they work fine." How so, if the new devices, as I conclude from your writing, land on fd1d which the BR cannot communicate with? And if it can communicate with the devices on fd16, why did they stop working?

scenic pivot
#

The new devices are using a FD16 address's and the old devices are attempting to use fd1d. I have no idea why the old devices are trying to use fd1d, that's what I'm trying to resolve.

I also used multi-admin and had pushed the old device to Alexa before this problem came up. What's interesting is that Alexa can still control most of the old devices but HA cannot talk with them at all.

sacred island
#

Is that to say that you are having multiple Thread networks (PANs) using Alexa devices as border routers as well? Or does HA show all your routers in one (preferably your) preferred network?

scenic pivot
#

There are technically 2 thread networks. One from HA and a second from Alexa. HA can’t use the Alexa thread network and all the thread devices were joined to the HA thread network.

#

How do I access the OTBR web interface?

sacred island
scenic pivot
#

So it turns out you have to enable BOTH the web port on port 8080 AND the REST API port