On Sun, Feb 11, 2018 at 5:05 AM, Kenneth R Westerback <kwesterb...@gmail.com
> wrote:
> Extraneous "bound to ..." messages are no longer logged on renewal.
>
> So the original "bound to ..." message remains valid until something
> changes.
>
> If you look at the leases file you should see it get a new 'epoch' (the
> time
> the lease was obtained) on renewals.
>
The thing is that when dhclient is doing a renew the ip address doesn't
attach to the interface:
em2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:0d:b9:41:6f:ca
index 3 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (1000baseT full-duplex)
status: active
Remember that this only happens during renew. Running "dhclient em2"
manually works, until the next renew.
This is how /var/db/dhclient.leases.em2 looks like:
lease {
fixed-address 51.174.196.170;
next-server 0.0.0.0;
option subnet-mask 255.255.224.0;
option routers 51.174.192.1;
option domain-name-servers 92.220.228.70,109.247.114.4;
option domain-name "lyse.net";
option broadcast-address 255.255.255.255;
option dhcp-lease-time 14400;
option dhcp-message-type 5;
option dhcp-server-identifier 51.174.112.1;
option bootfile-name "213.167.96.135";
epoch 1518359436;
renew 0 2018/02/11 16:30:36 UTC;
rebind 0 2018/02/11 18:00:36 UTC;
expire 0 2018/02/11 18:30:36 UTC;
}
