Changing output from error to info

[Leigh Porter]

I agree, these seem like good changes to make. The ability to tell dhcpd to listen for requests without being associated with a local subnet would be very good. I’d then be able to use iptables or other mechanisms to limit the scope of just what can send requests.

If dhcpd can include a mechanism to limit requests to certain source IP addresses then all the better.

Like Bob’s scenario, DHCP then becomes a network function much like DNS where you don’t care about such issues, just that you can send a request and expect a response.

--
Leigh



From: dhcp-users-bounces at lists.isc.org [mailto:dhcp-users-bounces at lists.isc.org] On Behalf Of Bob Harold
Sent: 11 November 2014 15:23
To: Users of ISC DHCP
Subject: Re: Changing output from error to info

Please consider this scenario:
I manage DHCP servers in a large environment.  The DHCP server is either in a Data Center server subnet, or a core router subnet, neither of which use DHCP.  They serve many client subnets, using DHCP forwarding on the routers.  So I have no need to configure DHCP for the local subnet other than to make DHCP happy.  It is likely in the future that the DHCP servers might be handled like my DNS servers - the server is managed by the Server group, and DNS or DHCP is just my "application" that runs on that server.  And if they decide to add another interface for monitoring, or backups, or whatever, I should not have to update by DHCP configuration.  I want to be able to tell DHCP either "only listen to interfaces I tell you about and ignore the others" or "listen to regular packets from any interface".   I have no need for the raw packet handling in my environment.

Unfortunately, I cannot sponsor the changes needed, nor make them myself, so I understand if no one makes them.  But I hope you understand why I think these changes are reasonable and would be happy if someone could make them.

--
Bob Harold
University of Michigan


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20141111/6026e009/attachment.html>