Freeradius 3.2.8 on Debian 12 not responding to requests via Relay Agent

Alan DeKok aland at deployingradius.com
Thu Jul 17 16:07:24 UTC 2025


On Jul 17, 2025, at 10:56 AM, David Lake via Freeradius-Users <freeradius-users at lists.freeradius.org> wrote:
> I can server hosts locally on 192.168.1.0 and everything works fine.

  That's good.

> However, I’m seeing zero traffic incoming to radius -X even though tcpdump shows that traffic is being received on the eth0 interface (192.168.1.1).  Pcap attached taken on the DHCP server machine.

  This is almost always an SELinux issue, or another permissions issue.  But if the server didn't have permissions to listen on port 67, it would just get an error, and fail to start.

  Which means it's likely an SELinux issue.

  i.e. if the server is listening on the correct port, then the permissions / UID / GID are all correct.  But some magic "security" thing is preventing the server from receiving the packets.

> Is there a config step I am missing?   ss -lunp shows that radiusd is listening on port 67.
> 
> My files/dhcp is configured as follows:

  The module configuration doesn't affect how the server receives packets.

  Failure to read packets from the network is pretty much always an OS issue, not a configuration issue.

  Alan DeKok.



More information about the Freeradius-Users mailing list