Adding network interface control over REST API in the implementation of a joiner REST API

[OmegaRelay]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is.

Hello, I would like to expand the current REST API by adding an interface to control the border router's joiner to securely join a new network. However, this requires the network interface to be up and the thread protocol to be disabled. As far as I can tell it is not currently possible to control these two independent of each other through the current REST API.

Describe the solution you'd like A clear and concise description of what you want to happen.

• Am I missing something; is it possible to control the network interface independently via the REST API?
• Advice on the most preferable way to facilitate this.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

The solutions I can think of are:

• Add another endpoint /node/iface, /node/interface, or /node/network which accepts PUT and GET requests to set the interface up/down or to get the interface state respectively.
• A PUT request on the new /node/joiner/state endpoint to start the joiner, will automatically set the network interface up if not already.

I'm open to alternative solutions.

Additional context Add any other context or screenshots about the feature request here.

[wgtdkp]

Hello, I would like to expand the current REST API by adding an interface to control the border router's joiner to securely join a new network.

I don't get it, could you provide more context about what you want to support?

[theisHafele]

Hi @wgtdkp I want to support being able to join a new border router to a pre-existing network (without having to manually provide the dataset), through the commissioning protocol using the REST API. Basically bringing the ot-ctl functionality of joiner start <pskd> into the REST interface.

[wgtdkp]

Hi @wgtdkp I want to support being able to join a new border router to a pre-existing network (without having to manually provide the dataset), through the commissioning protocol using the REST API. Basically bringing the ot-ctl functionality of joiner start <pskd> into the REST interface.

Thanks for the info, I got it!

A PUT request on the new /node/joiner/state endpoint to start the joiner, will automatically set the network interface up if not already.

This looks more reasonable to me.