DHCP issues in v3

Matthew Newton mcn4 at leicester.ac.uk
Fri Oct 11 23:23:05 CEST 2013

On Fri, Oct 11, 2013 at 08:31:50AM -0400, Alan DeKok wrote:
> > Next - with as above, and also "interface = br0". This time, no warning about
> > unicast only, but it still didn't see the broadcast packets.  This doesn't
> > surprise me entirely, as I've specifically set an IP address, but there is no
> > warning.
>   IIRC, it's an issue with bridges.  As always, the server is at the
> mercy of the OS.  It asks the OS for broadcast packets.  If the OS
> doesn't send them...

Agreed. Seems a bit surprising though. I'll test with plain eth
device (bridges are common here, VMs all over the place...)

> > Next I have "ipaddr = *" and again commented out the interface option (not
> > expecting it necessarily to work - the warning appears again). This works fine
> > until FR tries to send a reply, and we get a segfault.
>   Arran just committed a fix for that.

Didn't get a segfault in testing just now, but it still didn't
send any data in the outgoing packets.

Will report back when I've done some more testing.



Matthew Newton, Ph.D. <mcn4 at le.ac.uk>

Systems Specialist, Infrastructure Services,
I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom

For IT help contact helpdesk extn. 2253, <ithelp at le.ac.uk>

More information about the Freeradius-Devel mailing list