Finally all my devices works, but it is *against* warning from logs. I have had: --8<---------------cut here---------------start------------->8--- listen { type = dhcp ipaddr = * src_ipaddr = 192.168.200.200 port = 67 interface = lan broadcast = yes } --8<---------------cut here---------------end--------------->8--- I commented out "interface = " line, and now everything works, regardless of --8<---------------cut here---------------start------------->8--- Sat Nov 12 20:28:28 2016 : Warning: You MUST set "interface" if you have "broadcast = yes" Sat Nov 12 20:28:28 2016 : Debug: (7) DHCP: Reply will be broadcast as no interface was defined --8<---------------cut here---------------end--------------->8--- in logs. With "interface = lan" there were no "DHCP-ACK" for some devices (and it was my fault when sending previous mail) I am still not sure if it is freeradius issue or my routing, arp or sth. Alan asks about system: --8<---------------cut here---------------start------------->8--- uname -a Linux alfa 4.4.0-1-amd64 #1 SMP Debian 4.4.6-1 (2016-03-17) x86_64 GNU/Linux sudo getcap -v /usr/sbin/freeradius /usr/sbin/freeradius = cap_net_bind_service,cap_net_admin,cap_net_raw+ei --8<---------------cut here---------------end--------------->8--- " cap_net_bind_service" and "cap_net_raw" is probably unneccessary. KJ kjonca@o2.pl (Kamil Jońca) writes:
After a "some" time (I have to go to sleep ) and setting "ipaddr = *" [1] radius starts received and reply to broadcasts.
Now I have another problem:
some older androids don't like server messages, they 'waits for IP' infinitely.
dhcpdump shows that only difference between isc-dhcp and freeradius dhcp is presence
OPTION: 57 ( 2) Maximum DHCP message size 1500 in radius reply.
How can I turn it off to test my suspicions?
kjonca@o2.pl (Kamil Jońca) writes:
[...]
[1] - I'm pretty sure, i have test it also previously.
-- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html A guy has to get fresh once in a while so a girl doesn't lose her confidence.