Feature #16987
closed
Static arp entry in DHCP should automatically be whitelisted in captive portal
0%
Description
When one adds a static ARP entry in the DHCP configuration, if the captive portal is also active in the same interface, one still has to login in the captive portal. This is not wrong in itself, but I do not think it is the most common user case, i.e. when one adds a static ARP the expected behaviour is that the device connects without human intervention.
The current workaround is to also add the mac address in the whitelist of the captive portal configuration. It would be useful to have an option that causes the captive portal to automatically generates a whitelist of mac addresses from the static ARP DHCP leases.
A side effect is that editing DHCP requires also a reload of the captive portal configuration
Updated by Jim Pingle about 5 hours ago
- Status changed from New to Rejected
The two functionalities are entirely separate and making an assumption such as this violates basic security principles.