On 2020-04-27 05:16, Ed Greshko wrote:
On 2020-04-27 18:58, ToddAndMargo via users wrote:
On 2020-04-27 00:11, Ed Greshko wrote:
On 2020-04-27 15:07, Tim via users wrote:
Tim:
If true, I'd call that a bug. It's a ludicrous requirement for users to create *that* file. DHCP is supposed to be a *fully* automatic address assignment system. Have you reported it to bugzilla?
Ed Greshko:
I don't think it is a bug. It would be more about how NetworkManger handles things.
I'd certainly call that a bug (having to manually intervene to get a DHCP client to work). Where it's attributable is another matter (DHCP itself, or NetworkManager).
So far I've not seen any indication of what doesn't work. Have you?
Unless you create the file yourself, it does not get written to. I have seen references to this on google, so I presume it was done on purpose, although I think it is ill advised.
What functionality is lost?
The information in /var/lib/dhclient/dhclient.leases:
lease { interface "br0"; fixed-address 192.168.255.116; option subnet-mask 255.255.255.0; option time-offset 39600; option routers 192.168.255.10; option dhcp-lease-time 10355267; option dhcp-message-type 5; option domain-name-servers 192.168.255.10; option dhcp-server-identifier 192.168.255.10; option broadcast-address 192.168.255.255; option domain-name "rent-a-nerd.local"; renew 2 2020/06/23 01:34:08; rebind 0 2020/08/09 22:11:01; expire 1 2020/08/24 21:44:30; }
And to make matter even worse,
$ ls /var/lib/dhclient dhclient-a056777e-8a75-4da5-9585-6aacf150b862-eno2.lease dhclient.lease dhclient--eno2.lease dhclient.leases
dhclient--eno2.lease deos not get created either until you create /var/lib/dhclient/dhclient.lease
And now dhclient.lease ONLY contains the IP number
I've not seen a reference to dhclient.lease only dhclient.leases. Are you calling dhclient with parameters to create that file?
Typo on my part
Are the connections you reference above being controlled by NetworkManager?
I presume