Today NICo allocates DHCP IPs to any requests reaching it and rely on endpoint explorer only exploring BMCs of expected devices to avoid getting on to / ingest unexpected devices. This is fine but risk getting exhausted of dynamic IPs due to buggy devices or attacks, which will result in expected devices not able to get dynamic IPs.
Although large deployments will likely use static or pre-assigned IPs and not really benefit from this improvement, the very fact that NICo's DHCP server can hand out pre-assigned IPs means it will be not too costly to do it in a reversed way, to only hand out dynamic IPs if the MAC is expected.
This behavior should be configurable in case there for other scenarios for handling (or even ingesting) unexpected devices.
Today NICo allocates DHCP IPs to any requests reaching it and rely on endpoint explorer only exploring BMCs of expected devices to avoid getting on to / ingest unexpected devices. This is fine but risk getting exhausted of dynamic IPs due to buggy devices or attacks, which will result in expected devices not able to get dynamic IPs.
Although large deployments will likely use static or pre-assigned IPs and not really benefit from this improvement, the very fact that NICo's DHCP server can hand out pre-assigned IPs means it will be not too costly to do it in a reversed way, to only hand out dynamic IPs if the MAC is expected.
This behavior should be configurable in case there for other scenarios for handling (or even ingesting) unexpected devices.