SO_REUSEADDR for dhcp listener - goog idea?

[Kamil Jońca]

aland at deployingradius.com (Alan DeKok) writes:

[...]

>   FreeRADIUS has been able to bind to a specific interface for ages.  For precisely this reason.


But when dhcp is bind to (say) 192.168.1.200 it do not receive
DHCPDISCOVER messages (like this)

#v+
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f5:6b:72:90 (oui Unknown), length 300, xid 0xc748c5f7, secs 17, Flags [none]
	  Client-Ethernet-Address 00:0a:f5:6b:72:90 (oui Unknown)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether 00:0a:f5:6b:72:90
	    MSZ Option 57, length 2: 1500
	    Vendor-Class Option 60, length 18: "android-dhcp-6.0.1"
	    Hostname Option 12, length 9: "skowronek"
	    Parameter-Request Option 55, length 9: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, Domain-Name
	      MTU, BR, Lease-Time, RN
	      RB
#v-

is it normal?

-- 
http://wolnelektury.pl/wesprzyj/teraz/
What kind of sordid business are you on now?  I mean, man, whither
goest thou?  Whither goest thou, America, in thy shiny car in the night?
		-- Jack Kerouac