Date: Mon, 11 Aug 2003 21:07:33 +0200 (CEST) From: Martin Blapp <mb@imp.ch> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-audit@freebsd.org Subject: Re: pccard_ether and dhcp handling - please decide ... Message-ID: <20030811205500.M2686@cvs.imp.ch> In-Reply-To: <20030811.102336.72710224.imp@bsdimp.com> References: <20030811173926.R2686@cvs.imp.ch> <20030811.102336.72710224.imp@bsdimp.com>
index | next in thread | previous in thread | raw e-mail
Hi, > Sometimes I think we need to rewrite a BSD-friendly licensed > dhclient... Ah, so many projects, so little time. At ImproWare, we have a our own dhcpd server for our DOCIS cable modem suite, because ISC dhcpd sucked a lot and it was too difficult to add database support to it. So Patg did rewrite it from scratch, with mysql support and unsupported additions which were needed to support cable modems properly. A client would be easy to write based on the server code. Our server is written in C++ and is very efficient and small. It would also rock if one could define the options in a configfile, that means you could say what the dhcp client should do if it gets a option "time-servers", "nis-servers" etc. etc. Like this, our dhcp client would be very open. >interfaces that it is listening to (I'm talking about having dhclient >do this directly, and not via OMAPI or whatever it uses). I think there should still be a way to talk to the server, a easy way would be via RPC, or just direct via local unix domain socket. I like your idea, but it should also be possible to send commands to the server. Martinhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030811205500.M2686>