-
-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 Route Advertisements Not Accepted #1919
Comments
This seems like a reasonable thing to add support for in openHABian as it's a dependency for a major advertised feature in the upcoming openHAB release. @mstormi what do you think about adding this to openHABian? I can probably look into adding it if you agree. |
Further update... If using DHCP to assign an IP address to the Raspberry Pi then the /etc/dhcpcd.conf also needs to be updated to append
Otherwise dhcpcd will always override the accept_ra option everytime the interface is restarted and the accept_ra configuration will be lost |
okay for me but you need to ensure it's compatible with Raspi OS and potential package upgrades. |
Fixes openhab#1919 Signed-off-by: Ethan Dye <mrtops03@gmail.com>
Fixes openhab#1919 Signed-off-by: Ethan Dye <mrtops03@gmail.com>
Issue information:
A Matter binding is under development/testing, written by digitaldan, which can integrate Matter Thread based devices using an external Thread Border Router into openHAB. However, by default an openhabian build does not allow for the IPv6 route advertisments to be accepted which stops the binding discovery process from working when the openHAB server is connected wired and the Thread Border Router is connected wirelessly.
Debug information:
The following parameters need to be added to /etc/sysctl.conf to allow IPv6 Route Advertisments
Where eth0 is the relevant ethernet interface name that is being used.
System information:
OS: Raspberry Pi OS
HW: Raspberry Pi 3 Model B you are running on (Raspberry Pi, amd64). Also include the output of
cat /etc/os-release
anduname -m
.The text was updated successfully, but these errors were encountered: