Hudu Radar

When Hudu Radar automatically classifies discovered devices, users have no way to override the assigned device type mapping. Hudu Radar should allow users to manually reclassify devices on a per-device basis, with the override persisting through future scans.

When Hudu Radar discovers a network device (such as a printer, switch, or router), there is currently no way to access that device's HTTPS management interface directly from Hudu. Tools like Domotz support this by proxying the connection through the installed endpoint, allowing technicians to reach a device's web UI even when it isn't directly accessible from their browser. Adding proxied remote access to Hudu Radar would allow users to click through to a device's management page directly from its asset in Hudu, routed through the Radar agent or service on that network. This would significantly reduce the friction of managing devices on remote or segmented networks.

Servers, UPSs, etc. It would be best if we could match discovered devices to any type of configured asset layout.

Please add a way for Radar to distinguish between reserved DHCP addresses (which essentially function as static addresses) and normal dynamic DHCP addresses. For users with DHCP reservation pools for critical infrastructure like servers and firewalls, it would be helpful to be able to input those reservations instead of Radar assuming every IP is DHCP.

Currently, Hudu Radar is limited to being installed on Windows. It would be appreciated to have a native Linux install :)

Currently, Hudu Radar only seems to allow for scanning the currently attached L2 network. It would be of benefit if it was capable of scanning additional L2s accessible via L3, such as VLANs for example. Screenshot attached for reference.

Allow tunneling the web interface from discovered devices like domotz/auvik?

Currently, it seems Hudu Radar requires you to log into the Hudu instance even though it uses a code. This seems counterintuitive to the whole purpose of using an API token if one has to sign in every time. What would resolve this: Making it where Hudu Radar setup does not require signing in and the provided API token is enough.

Basically markers putting next to each device showing whether the IP address is alive or dead.

We would like to request that the Hudu Radar code received from the IPAM section within a company be updated so the expiration timer can be customized.