where does latest dhcp options store?
chengy.fan at gmail.com
Mon Mar 19 19:37:49 UTC 2012
Since dhclient file name can depend on many variables , if I want to use
the private options, which is provided by the dhcp server, in my program, I
think the best way is to specify the lease file in the command line...
Another question is my dhclient does not use the config file
"/etc/dhcp/dhclient.conf", it will never request the private option in
dhclient.conf unless I specify it in the command line. I think it is
default config file, isn't it?
On Mon, Mar 19, 2012 at 1:15 PM, Edward DeLargy <eddelargy at gmail.com> wrote:
> The dhclient file name can depend on many variables. The most
> important is the DHCP version and operating system. The eth is showing that
> is the port the lease is binding to. It is supposed to help admins trouble
> shoot. There could be something in the DHCP server sending out serial
> numbers if you have anything else in the lease file other than port name or
> it could be something about the OS ( I am not sure). The file is not named
> dhclient leases due to it being specifically assign to a port. If your
> using Network Manager or Yast it would have the dhclient name, but it you
> assign with the dhclient ethX command it will have the port name.
> Hope that helped.
> Ed DeLargy
> On Mon, Mar 19, 2012 at 1:03 PM, Chengyu Fan <chengy.fan at gmail.com> wrote:
>> Thanks for the help.
>> I did as what you told me. When I restart the network service, I find the
>> new lease file appeared in the folder is dhclient-xxx...xxx-eth0.lease, I
>> don't know what the "xxx" means. (the xxx is a string contains digit, char
>> and -). Also I am wondering why the file name is not dhclient.leases.
>> Another question is that the file in '/var/lib/dhcp' seems not the result
>> of the config file '/etc/dhcp/dhclient.conf', because I added one private
>> option in the config file, but it does not show in the leases file. If I
>> designated in the command line, the result leases file contains the private
>> option information.
>> By the way, I downloaded the DHCP source code and installed it.
>> On Mon, Mar 19, 2012 at 7:40 AM, Edward DeLargy <eddelargy at gmail.com>wrote:
>>> Hope this helps:
>>> The dhclient lease information should only be stored in the
>>> var/lib/dhclient folder. You should rm -rf * inside that folder to totally
>>> clear old info. Also, depending on your dhcp config you may find traces
>>> inside the network-scripts for the particular interface. A service network
>>> restart should clear anything out after you remove all old files. Those are
>>> the only two places I can think of that cache dhclient lease information.
>>> If you don't remove the old options eventually the old address could pop
>>> back in due to the TTL set in your primary dhcp.conf file.
>>> On Sat, Mar 17, 2012 at 12:09 AM, Chengyu Fan <chengy.fan at gmail.com>wrote:
>>>> Does anyone know that where does the latest dhcp options store?
>>>> I released the old lease using "dhclient -r", and then request a new
>>>> lease (I add a new option in the config file) using "dhclient ". The option
>>>> I mentioned is a private option numbered 246. According to the packets I
>>>> captured, the request and response is all OK, but I don't know where does
>>>> the dhclient store this option.
>>>> I searched the file /var/lib/dhcp/dhclient.leases, but it is not
>>>> Chengyu Fan
>>>> dhcp-users mailing list
>>>> dhcp-users at lists.isc.org
>>> dhcp-users mailing list
>>> dhcp-users at lists.isc.org
>> Chengyu Fan
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
> dhcp-users mailing list
> dhcp-users at lists.isc.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dhcp-users