As the border router is required to always be a router there must be a way built in to force a node to be router.
Background:
We are working on an application that require low latency and rather high throughput at random intervals with one to many communication and have been relying on the router role of the gateway as our "master" and the source of the data distribution.
Since only routers and children of the source will accept data from ff02::2 aka the (logical link local address).
However we would like to drop the raspberry pi and use a embedded mcu for this role. But our application depends on the master having a router role.
a. What does the border router do to stay in router role?
b. Is it possible with a custom build maybe for one node to assume a border router role without the being on a linux system?
Thanks