Re: Major dhclient(8) changes - no more dhclient-script
On Wed, Nov 14, 2012 at 08:35:52AM -0500, Kenneth R Westerback wrote: On Tue, Nov 13, 2012 at 03:14:40PM -0500, sven falempin wrote: 2012/11/9 Kenneth R Westerback kwesterb...@rogers.com Those of you following -current or running very recent snaps may have noticed a lot of changes to dhclient in the last couple of weeks. Aside from some major clean up, these changes revolve around the elimination of the dhclient-script as both detrimental to sanity and our ability to move forward to better network configuration automation. So far a couple of uses for dhclient-script have been reported and workarounds have to be developed for these scenarios. But now that most of the changes are committed we are very interested in making sure that scenarios that lead people to modify dhclient-script are identified sooner rather than later. So please test the new dhclient(8) in as many situations as possible and report both 'noraml' bugs/regressions and problems you have not been able to solve without dhclient-script. Thanks. How to prevent deleting of /etc/resolv.conf by dhclient? I have this: # egrep -v ^#|^[ \t]*$ /etc/dhclient.conf ignore domain-name-servers, domain-name; The goal is to have always my own /etc/resolv.conf. I'm using pdnsd, the best would be to catch offerent dns server and if OK I would like to do someting with that. (I was using that on Ubuntu, caching if offered dns servers are ones from my job, if so and then into pdnsd setup; because internal company's dns server sucked a lot and I was using other public dns for normal recursive queries but going via internal company's ones only for specific domains.) Anway, I don't like to be without /etc/resolv.conf and also have there so stupid dns offered by dhcp. Thanks for tips. jirib
Re: Major dhclient(8) changes - no more dhclient-script
On Fri, Nov 09, 2012 at 09:44:01AM -0500, Kenneth R Westerback wrote: Those of you following -current or running very recent snaps may have noticed a lot of changes to dhclient in the last couple of weeks. Aside from some major clean up, these changes revolve around the elimination of the dhclient-script as both detrimental to sanity and our ability to move forward to better network configuration automation. So far a couple of uses for dhclient-script have been reported and workarounds have to be developed for these scenarios. But now that most of the changes are committed we are very interested in making sure that scenarios that lead people to modify dhclient-script are identified sooner rather than later. So please test the new dhclient(8) in as many situations as possible and report both 'noraml' bugs/regressions and problems you have not been able to solve without dhclient-script. Thanks. Ken Well, resolv.conf(5) has many neat options which one could like to have added into resolv.conf even when using dhcp to get dns servers. One of them could be: family, some options like tcp... I don't want to be nitpick but with personalized dhclient-script one could code whatever to have valid resolv.conf(5) settings in his /etc/resolv.conf. jirib
Re: Major dhclient(8) changes - no more dhclient-script
On 2012/11/15 16:59, Jiri B wrote: On Fri, Nov 09, 2012 at 09:44:01AM -0500, Kenneth R Westerback wrote: Those of you following -current or running very recent snaps may have noticed a lot of changes to dhclient in the last couple of weeks. Aside from some major clean up, these changes revolve around the elimination of the dhclient-script as both detrimental to sanity and our ability to move forward to better network configuration automation. So far a couple of uses for dhclient-script have been reported and workarounds have to be developed for these scenarios. But now that most of the changes are committed we are very interested in making sure that scenarios that lead people to modify dhclient-script are identified sooner rather than later. So please test the new dhclient(8) in as many situations as possible and report both 'noraml' bugs/regressions and problems you have not been able to solve without dhclient-script. Thanks. Ken Well, resolv.conf(5) has many neat options which one could like to have added into resolv.conf even when using dhcp to get dns servers. One of them could be: family, some options like tcp... I use resolv.conf.tail for these.. nameserver 127.0.0.1 search spacehopper.org lookup file bind family inet6 inet4 and skip requesting name-servers in dhclient.conf: request subnet-mask, broadcast-address, routers;
Re: Major dhclient(8) changes - no more dhclient-script
2012/11/9 Kenneth R Westerback kwesterb...@rogers.com Those of you following -current or running very recent snaps may have noticed a lot of changes to dhclient in the last couple of weeks. Aside from some major clean up, these changes revolve around the elimination of the dhclient-script as both detrimental to sanity and our ability to move forward to better network configuration automation. So far a couple of uses for dhclient-script have been reported and workarounds have to be developed for these scenarios. But now that most of the changes are committed we are very interested in making sure that scenarios that lead people to modify dhclient-script are identified sooner rather than later. So please test the new dhclient(8) in as many situations as possible and report both 'noraml' bugs/regressions and problems you have not been able to solve without dhclient-script. Thanks. Ken Is it possible to ignore route pushed by the server ? -- - () ascii ribbon campaign - against html e-mail /\
