Replies: 6 comments 10 replies
-
|
We use the node.js options to gather all relevant interfaces and all IPv6 addresses. If we do not publish it that means that the node.js process is not getting this address. if you like try entering the conteiner (or whereever the nodejs is executed) and execute Post the output here. |
Beta Was this translation helpful? Give feedback.
-
|
Here you go. Thank you so much. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry. I changed the Global IPv6 ULA-Prefix to fd81:b82:c83::/48 and restarted everything while troubleshooting. The fd81 ending with 20 is the one assigned to the eth0 of the host. The docker container is in host networking mode if that helps. |
Beta Was this translation helpful? Give feedback.
-
|
The matterbridge does not provide the ability to announce on a specific interface. Is there a way to do so when starting the library (I don't know enough about these things but I'm willing to learn)? Perhaps it would be better if the matter.js would prefer the global address i..e fd81 over the local one i.e. fe80. I wonder if it is just picking the first IPv6 address attached to the interface eth0 and advertises on that! |
Beta Was this translation helpful? Give feedback.
-
|
@Apollon77 . Thank you very much indeed for the extensive checks. I will try configuring the interface limitation and update the post accordingly. Once again, thank you very much for taking the time to help with this. |
Beta Was this translation helpful? Give feedback.
-
|
Today I found #2189 which lead to invalifd encoding of specil IPv6 adresses sometimes, might be easiely related that ... would be cool to retry after this got merged |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm not a developer so please bear with me.
I'm using "Home Assistant Matter Hub" which uses matter.js.
The container is attached to the host network and it seems to start and only advertises the Link Local Address IPv6 address (fe80:xxxx:xxxx) of the host not the ULAs one which should be (fd82:xxxx:xxxx:).
Is this something that can be modified or fixed somehow?
I tested this by stopping the container, publishing the fd82 address using avahi-publish-address xxxxsdfsf.local fd82:xxxx:xxxx and it works but when I start the container running avahi-resolve-host-name xxxxsdfsf.local returns the fe80:xxxx:xxxx address.
Thank you in advance
Beta Was this translation helpful? Give feedback.
All reactions