Re: dhcpcd refreshing lease very often.

[Mike Pumford <mpumford%mudcovered.org.uk@localhost>]

On 11/08/2020 21:14, Mike Pumford wrote:

> Aug 11 21:09:55 trigati dhcpcd[12897]: wm0: sending REQUEST (xid 
> 0xc8152c37), next in 64.3 seconds
> Aug 11 21:11:00 trigati dhcpcd[12897]: wm0: sending REQUEST (xid 
> 0xc8152c37), next in 64.0 seconds
This cycle was finally stopped by this:
Aug 12 11:53:56 trigati dhcpcd[12897]: wm0: failed to renew DHCP, rebinding
Aug 12 11:53:56 trigati dhcpcd[12897]: wm0: expire in 5400 seconds
Aug 12 11:53:56 trigati dhcpcd[12897]: wm0: sending REQUEST (xid 
0x68dace9d), next in 3.0 seconds
Aug 12 11:53:56 trigati dhcpcd[12897]: wm0: acknowledged 192.168.1.2 
from 192.168.1.9
Aug 12 11:53:56 trigati dhcpcd[12897]: wm0: leased 192.168.1.2 for 43200 
seconds
Aug 12 11:53:56 trigati dhcpcd[12897]: wm0: renew in 21600 seconds, 
rebind in 37800 seconds
Aug 12 11:53:56 trigati dhcpcd[12897]: wm0: writing lease 
`/var/db/dhcpcd/wm0.lease'

So it looks like the renew code is not seeing and processing the ack 
from the server in the renew path.

This will happen every renewal cycle so I can capture packet traces and 
share them if that helps.

Just in case its relevent the client interface is configured as follows:
wm0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        capabilities=7ff80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx>
        capabilities=7ff80<TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Rx>
        capabilities=7ff80<TCP6CSUM_Tx,UDP6CSUM_Rx,UDP6CSUM_Tx,TSO6>
        enabled=7ff80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx>
        enabled=7ff80<TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Rx>
        enabled=7ff80<TCP6CSUM_Tx,UDP6CSUM_Rx,UDP6CSUM_Tx,TSO6>
        ec_capabilities=17<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,EEE>
        ec_enabled=2<VLAN_HWTAGGING>
        address: 10:c3:7b:95:20:ed
        media: Ethernet autoselect (1000baseT full-duplex)
        status: active

Mike