On 10/25/2013 05:47 PM, freeradius-users-request@lists.freeradius.org wrote:
The server*thinks* it's sending the packet. Is there a FW rule preventing DHCP from leaving the box?
iptables are empty, i have completely removed ufw and apparmor, no change detected
Can you use gdb to track down what's going on? Maybe the send() call is silently failing?
when using gdb i once got this error: Sending DHCP-Offer of id 406a7a14 from 255.255.255.255:67 to 192.168.0.102:68 (5) Finished request 5. Waking up in 0.3 seconds. Waking up in 1.6 seconds. (3) Cleaning up request packet ID 3771922810 with timestamp +17 Waking up in 0.2 seconds. ASSERT FAILED src/main/process.c[498]: 0 == 1 Program received signal SIGABRT, Aborted. 0x00007ffff674b425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 The error doesn't happen always, so i'm not sure if it's connected to dhcp problem. i have tried different scenarios, direct cable connection, connection via switch, same result.. When I manually set IP on dhcp client machine it was able to ping/ssh the radius server. I have no idea what i could try next