DHCPCD [BOOTP proxy] behavior

I was watching processes with top command and noticed that dhcpcd process shows old red connection IPs is this normal behavior?

14008 root      20   0    2.9m   2.2m   0.0   0.0   0:00.01 S      `- dhcpcd: [privileged proxy] red0 [ip4] 
16312 dhcpcd    20   0    2.9m   0.4m   0.0   0.0   0:00.00 S          `- dhcpcd: [BOOTP proxy] xx.xx.xx.x8   <- My first connection with modem bridged
25791 dhcpcd    20   0    2.9m   0.4m   0.0   0.0   0:00.00 S          `- dhcpcd: [BOOTP proxy] 192.168.100.10  <- switched modem to routed mode and restarted it
27252 dhcpcd    20   0    2.9m   0.4m   0.0   0.0   0:00.00 S          `- dhcpcd: [BPF ARP] red0 192.168.100.10 <- switched modem to routed mode  and restarted it
28619 dhcpcd    20   0    2.9m   0.4m   0.0   0.0   0:00.00 S          `- dhcpcd: [BPF ARP] red0 xx.xx.xx.x97 <- current connection after switching modem to bridged mode again
30715 dhcpcd    20   0    2.9m   0.4m   0.0   0.0   0:00.00 S          `- dhcpcd: [BOOTP proxy] xx.xx.xx.x97 <- current connection after switching modem to bridged mode again
14009 dhcpcd    20   0    2.8m   0.3m   0.0   0.0   0:00.00 S      `- dhcpcd: [control proxy] red0 [ip4]

If I release red connection with dhcpcd -k red0 and rebind with dhcpcd -n red0 there are only current addresses visible.

This appears to be normal behavior. The dhcpcd process may temporarily retain instances of previous IP configurations. This happens because dhcpcd does not always instantly clear out old configuration details when a new DHCP lease is obtained. As a result, it might continue to display old addresses as part of its process tree in monitoring tools like top.

2 Likes

Yes this is the normal behavior. The dhcp client tries to reget the old IP before a new one is aquired.

3 Likes

Thanks, thats nice to know.

So they stay there until reboot or release and rebind? Did multiple modem reboots and now there are 6 diffrent ip’s just waiting and they are been there over lease time.

Last year I had lot of problems with my connection and usually rebooting my 4G router fixed it for a while. There must been quite lot of old connections in dhcpcd then since I was using bridged mode. :smile: