Open Hiihtaja77 opened 1 year ago
Typical Iot device might have connectivity to Host and also 2 or more different radio drivers. IPV6 packet can arrive from Host and should be routed to desired radio driver. Packets can arrive from any of network interface and be routed to Host .
Hi @jukkar, @rlubos,
This issue, marked as an Feature Request, was opened a while ago and did not get any traction. It was just assigned to you based on the labels. If you don't consider yourself the right person to address this issue, please re-assing it to the right person.
Please take a moment to review if the issue is still relevant to the project. If it is, please provide feedback and direction on how to move forward. If it is not, has already been addressed, is a duplicate, or is no longer relevant, please close it with a short comment explaining the reason.
@Hiihtaja77 you are also encouraged to help moving this issue forward by providing additional information and confirming this request/issue is still relevant to you.
Thanks!
Am I right in that this is an issue for openthread? Even with a border router, my zephyr-based thread device does not get a GUA, and can't even communicate with other ULAs outside of it's own, because there is no default route.
If that's true, it means that zephyr devices currently can only talk within a thread network and can't really utilize border routers.
@M1cha Not really, these options should not affect OpenThread device capability to reach external networks. If the device doesn't get GUA it may suggest some misconfiguration, please check the following issue where we investigated similar case: https://github.com/zephyrproject-rtos/zephyr/issues/29567#issuecomment-717311081
https://github.com/zephyrproject-rtos/zephyr/blob/45dcc6c5dbfb98944133a7c046959d763021386a/subsys/net/ip/Kconfig#L312
Routing look as hidden capability in Zephyr. Can it be as generic part of Zephyr OS and support at list 3 network interfaces.