ot-br-posix
ot-br-posix copied to clipboard
openthread
OTBR add "On-Mesh Prefix" on OpenWRT Luci
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is.
The Form function of the native OT Border Router WEB GUI can directly set the default ON-Mesh Prefix, while OpenWrt's Luci Form does not have this option.
This results in devices connected to the OpenWrt Thread network being unable to get the Mesh Local IP from the OTBR.
Luci form: no fd11:22 ip
OTBR WEB form: ok
Describe the solution you'd like A clear and concise description of what you want to happen. a. Add the setonmeshprefix(to set) and onmeshprefix(to get) functions to the Ubus, then call the ubus command on the Luci Web. b. Add the setonMeshPrefix and onmeshPrefix functions to ot-ctl, then Call the ot-ctl command on the Luci Web. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.
@IHIDCHAOS In fact, Thread can have multiple prefixes. Instead of adding setonmeshprefix, I think it better to add UI support full functionality of https://github.com/openthread/openthread/tree/master/src/cli#prefix. That is, OpenWRT should be able to manage multiple prefixes with different flags. Thoughts?
Hi @bukepo,
Thanks for your reply.
I noticed that in your link there are some Prefix flag features only work on Thread 1.2. But right now on the official OTBR Web GUI there is only one box for setonmeshprefix. I wonder is this a preparation for the new Thread version? If so, may be it would be better to start with Raspberry Pi? If not, then add setonmeshprefix input box on OpenWrt platform is great complement for now.
In addition, are there any cases where multiple prefixes need to be added to one end device? Any example links are much appreciated!
Best, Yicong
I agree that Raspberry Pi should also allow configuration of multiple on-mesh prefixes.
