Thanks Admon for your response. You’re correct curl isn’t the right command.
To further explain what I want to do with this device. Is for it to act as a gateway between the two networks.
I’ll have a computer app / phone app that can send UDP commands to the router (ip:port) and then sends either multicast / unicast packets to the thread network. (IPv6:port)
I still don’t have the device and I’m unsure how to do exactly this.
In addition I would expect to be able to query devices.
From the docs overview, it does look like all of this is possible. But unsure of the exact mechanisms to do so.
Basically I have a handful of thread devices that respond to UDP. I have a USB dongle that can already join a thread network and send and receive commands.
However, I want to try and extend that to a router where a computer on the network can send a UDP packet to the router then the router forwards that to the thread network and then replies as well.
Maybe you want to check homeassistant as frontend. Works with Home Assistant - GL.iNet IoT Docs ... I like to understand everything in the basic as well. But maybe it is easier to understand the basics with a full featured frontend as well...
This device is not exactly what I was looking for. However it is great to see the state of a known network.
Currently can't send command via the rest API. When talking directly with the sales rep, they suggested that I can ssh into the router and then send the commands that way. I wanted to avoid that since I planning to have a phone app that could connect to the device (via wifi) and then send commands via the rest API or something similar.
Maybe future firmware updates can fix these issues. For now It's a good router that can also see a OpenThread network.
Firmware: v4.1.5-0400
If the firmware is updated from there. My comments maybe null / void.