This is an old revision of the document!
The purpose of new arrivals
- New arrivals are used to make on-boarding smoother.
- New arrivals are used in two places
- RADIUS Clients
- MESHdesk and APdesk (hardware)
Entries in New Arrivals
- Entries to New Arrivals are added by the system.
- When a RADIUS client which has not yet been added but who has the correct shared secret contacts the server (using the RADIUS protocol), it will be added to the New Arrivals for RADIUS under the RADIUS section.
- When hardware like a mesh node or AP with the MESHdesk firmware on, which is configured to point to the RADIUSdesk server contacts the server (using HTTP or HTTPS), and the hardware is not yet managed, it will be added to New Arrivals for Hardware under MESHdesk and APdesk.
Testing New Arrivals
- To confirm that the system add New Arrivals as intended you can test it by mimicking a RADIUS client and MESHdesk enabled hardware.
Mimic a RADIUS Client
- RADIUSdesk has a built-in RADIUS client for your convenience.
- Under the Overview section is a Utilities tab with a RADIUS Client launch button.
- This is the result of your test action
- You can now either delete it, or attach it as a RADIUS Client.
Mimic MESHdesk enabled hardware
- The MESHdesk enabled hardware will to a HTTP GET call to the RADIUSdesk server.
- This can be either using HTTP or HTTPS and is configurable.
- The following can be used as a reference:
- The result when it is not yet managed will look like this
{ "success": false, "error": "MAC Address: 00-3F-5D-00-8F-C5 not defined on system" }
- This is the result of our test action
- You can now either delete it, or attach it as a node to a selected mesh network or AP to an AP Profile.





