I tried sudo setcap cap_net_admin=ei /usr/sbin/freeradius. Then I checked that it is set up by getcap /usr/sbin/freeradius and it was /usr/sbin/freeradius = cap_net_admin+ei But there is still Failed adding ARP entry: Failed to add entry in ARP cache: Operation not permitted (1) Also I tried to freerad ALL = (root) NOPASSWD: /usr/sbin/arp to sudoers.d file, result is negative. Only launching from root user (commenting user = freerad) helps. But I don' t run it from root. пт, 30 июл. 2021 г. в 02:30, CpServiceSPb <cpservicespb@gmail.com>:
I use Freeradius 3.0.21 on Ubuntu 18.04 x64 LTS.
It is started under freerad:freerad, acts as DHCP as well listen to 0.0.0.0 IP and accept broadcast on one of two interfaces and listen to 192.168.0.254 and not accept broadcast on other one interface.
During DHCP conversation with clients using broadcast accepting (IP 0.0.0.0) interface, the following message is got and DHCP don' t assign to the client: "Failed adding ARP entry: Failed to add entry in ARP cache: Operation not permitted (1)"
I don' t want to launch Freeradius under either root user or root/admin group.
What is the best solution to avoid the error under freerad:freerad and move on ?