Re: Which DHCP client
> NOTE that unlike the WIDE client, the ISC client defaults to overwriting > your /etc/resolv.conf file. In my case, an action that pisses me off > because I now have to write a messy /etc/dhclient.conf file to stop this > nonsence. On the flip side, you'll be able to set things the way you want (and make them *very* easy to find, versus the man page). There are sites that need/should to pick up DNS off the dhcp server. Especially when the campus moves the name servers around without telling the dhcp users :-). They'll have the knob it takes to turn that (back) on. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
OK, I've decided to import the ISC client. I am not pleased with this choice, but I believe the FreeBSD community in general seems to prefer this choice. Swaying arguments: 1. OpenBSD uses the ISC client and keep a careful eye on it for software engineering issues. (which is really all that buffov problems are) 2. Mike Smith's emails (priv and public) show that the ISC client offers us more options in configuring a system than the WIDE client. Issues include sysinstall bootstrapping support and /etc/rc* hooks. For the record, version 2 of the ISC client *DOES* in fact require an /etc/dhclient.conf file: # dhclient fxp0 Can't open /etc/dhclient.conf: No such file or directory exiting. this is stupid and I have a mind to change it to: Can't open /etc/dhclient.conf: using built-in defaults continuing. Also, /etc/dhclient-script *IS* required: # dhclient fxp0 /tmp/dcsFoU405: /etc/dhclient-script: not found /tmp/dcsWOk405: /etc/dhclient-script: not found fxp0: not found exiting. NOTE that unlike the WIDE client, the ISC client defaults to overwriting your /etc/resolv.conf file. In my case, an action that pisses me off because I now have to write a messy /etc/dhclient.conf file to stop this nonsence. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
> May I suggest looking at the OpenBSD dhcp client/server? I'm not sure > which one they're derived from, but the CHANGES file lists a bunch of > bug and security fixes. It looks like they're using the ISC dhcp client (and server). Dan Eischen eisc...@vigrid.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
May I suggest looking at the OpenBSD dhcp client/server? I'm not sure which one they're derived from, but the CHANGES file lists a bunch of bug and security fixes. -- Parag Patel To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
> Wackerbarth wrote: > > > I object to the idea that the selection of which dhcp client is > > being made on the basis that David has commit privledges and I do > > not. > > It's not. It's being made on the basis that David took the initiative > and did the work, and you did not. I think, he did. But his requests to get the thing reviewed/committed went unanswered. This is getting ugly... -mi To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
At 9:25 AM -0800 2/9/99, David O'Brien wrote: > I already have a bmaked ISC v2 dhclient. I bmaked both so I would > more informated about how easy either would be to add to the tree. > > I will spend some time today and reflect on which client I still > prefer in import. Does anyone have a good feel for which dhcp client would be better from a security standpoint? (me, I don't have a clue, but maybe that's something to consider) I'd also note that I have no particular preference which DHCP client is used, but I do very much like the idea that some DHCP capability will be available at installation time for net-installs. --- Garance Alistair Drosehn = g...@eclipse.its.rpi.edu Senior Systems Programmer or dro...@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
In article , Richard Wackerbarth wrote: > I object to the idea that the selection of which dhcp client is > being made on the basis that David has commit privledges and I do > not. It's not. It's being made on the basis that David took the initiative and did the work, and you did not. -- John Polstra j...@polstra.com John D. Polstra & Co., Inc.Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
On Tue, Feb 09, 1999 at 09:59:52AM -0600, Charlie ROOT wrote: > If someone will agree to commit the files, I'd be happy to supply > the pieces for the ISC DHCP2 client to drop in. I already have a bmaked ISC v2 dhclient. I bmaked both so I would more informated about how easy either would be to add to the tree. I will spend some time today and reflect on which client I still prefer in import. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
I do not dispute that he "likes" the WIDE client. However, his choice seems to be based on familarity rather than CURRENT technical evaluation. I have (recently) tried both clients. For the simple case, both work satisfactorily. The ISC client/server (pl10) builds right out of the box. I prefer it because of the additional flexability it provides for the non-trivial case. On Tue, 9 Feb 1999, Jordan K. Hubbard wrote: > I personally am ambivalent about which client is chosen just so > long as *a* client is chosen. I agree that this is the important issue. If someone will agree to commit the files, I'd be happy to supply the pieces for the ISC DHCP2 client to drop in. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
> I object to the idea that the selection of which dhcp client > is being made on the basis that David has commit privledges > and I do not. Further, it is clear that David has not used a > recent release of the isc client and is biasing his opinion > with false assertions. H. From where I'm sitting, it looked more to me like he was selecting it based on the fact that he liked the WIDE client a lot more. I personally am ambivalent about which client is chosen just so long as *a* client is chosen. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Which DHCP client
Jordan, I object to the idea that the selection of which dhcp client is being made on the basis that David has commit privledges and I do not. Further, it is clear that David has not used a recent release of the isc client and is biasing his opinion with false assertions. It is my opinion that we should not use this criteria to decide which client will become a part of the base system. I have been "bmake"ing the isc client for almost a year. Requests to get assistance in comitting it went unanswered. I believe the isc client to be a better choice. If size is a real concern, perhaps we should treat this client as we do the shell in PicoBSD. I'm not convinced that the differences are that great. However, the flexability is :-) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
