wickedd-dhcp4 debugging
My Wicked based network (Tumbleweed 20230213) does not accept new IPv4 addresses from a DHCP server (a cable router) unless I remove the status files in /var/lib/wicked/*. The journalctl log does not show many details in the situation, that wickedd-dhcp4 still uses an outdated IPv4 address (from another LAN), but can not accept the new IPv4 address: Feb 15 11:36:58 mybox systemd[1]: Starting wicked DHCPv4 supplicant service... Feb 15 11:36:58 mybox systemd[1]: Started wicked DHCPv4 supplicant service. Feb 15 11:37:07 mybox wickedd-dhcp4[1736]: br0: Request to acquire DHCPv4 lease with UUID ...-000007000000 Feb 15 11:37:22 mybox wickedd-dhcp4[1736]: br0: defer timeout 15 reached in state REBOOT Feb 15 11:37:23 mybox wickedd-dhcp4[1736]: br0: Committed DHCPv4 lease with address 192.168.12.2 (lease time 32720, renew in 11120 sec, rebind in 27320 sec) Feb 15 11:40:44 mybox systemd[1]: Stopping wicked DHCPv4 supplicant service... Feb 15 11:40:44 mybox systemd[1]: wickedd-dhcp4.service: Deactivated successfully. Feb 15 11:40:44 mybox systemd[1]: Stopped wicked DHCPv4 supplicant service. After deleting /var/lib/wicked/* and restarting wickedd-dhcp4 it works (100.66.111.3 is accepted). Feb 15 11:40:44 mybox systemd[1]: Starting wicked DHCPv4 supplicant service... Feb 15 11:40:44 mybox systemd[1]: Started wicked DHCPv4 supplicant service. Feb 15 11:42:21 mybox wickedd-dhcp4[5621]: br0: Request to acquire DHCPv4 lease with UUID ...-000010000000 Feb 15 11:42:23 mybox wickedd-dhcp4[5621]: br0: Committed DHCPv4 lease with address 100.66.111.3 (lease time 604800, renew in 302400 sec, rebind in 529200 sec) Feb 15 11:56:47 mybox wickedd-dhcp4[5621]: br0: Request to acquire DHCPv4 lease with UUID ...-000010000000 Feb 15 11:57:02 mybox wickedd-dhcp4[5621]: br0: defer timeout 15 reached in state REBOOT Feb 15 11:57:02 mybox wickedd-dhcp4[5621]: br0: Committed DHCPv4 lease with address 100.66.111.3 (lease time 603921, renew in 301521 sec, rebind in 528321 sec) Feb 15 11:57:39 mybox wickedd-dhcp4[5621]: br0: Request to drop DHCPv4 lease with UUID ...-000010000000: starting... Feb 15 11:57:45 mybox systemd[1]: Stopping wicked DHCPv4 supplicant service... Feb 15 11:57:45 mybox systemd[1]: wickedd-dhcp4.service: Deactivated successfully. Feb 15 11:57:45 mybox systemd[1]: Stopped wicked DHCPv4 supplicant service. But how I can configure wickedd-dhcp4 so, that it logs more details? Björn
On 15.02.2023 22:35, Bjoern Voigt wrote:
My Wicked based network (Tumbleweed 20230213) does not accept new IPv4 addresses from a DHCP server (a cable router) unless I remove the status files in /var/lib/wicked/*.
The journalctl log does not show many details in the situation, that wickedd-dhcp4 still uses an outdated IPv4 address (from another LAN), but can not accept the new IPv4 address:
Feb 15 11:36:58 mybox systemd[1]: Starting wicked DHCPv4 supplicant service... Feb 15 11:36:58 mybox systemd[1]: Started wicked DHCPv4 supplicant service. Feb 15 11:37:07 mybox wickedd-dhcp4[1736]: br0: Request to acquire DHCPv4 lease with UUID ...-000007000000 Feb 15 11:37:22 mybox wickedd-dhcp4[1736]: br0: defer timeout 15 reached in state REBOOT
Well, it looks like it does not get any response.
Feb 15 11:37:23 mybox wickedd-dhcp4[1736]: br0: Committed DHCPv4 lease with address 192.168.12.2 (lease time 32720, renew in 11120 sec, rebind in 27320 sec) Feb 15 11:40:44 mybox systemd[1]: Stopping wicked DHCPv4 supplicant service... Feb 15 11:40:44 mybox systemd[1]: wickedd-dhcp4.service: Deactivated successfully. Feb 15 11:40:44 mybox systemd[1]: Stopped wicked DHCPv4 supplicant service.
After deleting /var/lib/wicked/* and restarting wickedd-dhcp4 it works (100.66.111.3 is accepted).
And what happens if you simply restart wicked without removing lease?
Feb 15 11:40:44 mybox systemd[1]: Starting wicked DHCPv4 supplicant service... Feb 15 11:40:44 mybox systemd[1]: Started wicked DHCPv4 supplicant service. Feb 15 11:42:21 mybox wickedd-dhcp4[5621]: br0: Request to acquire DHCPv4 lease with UUID ...-000010000000 Feb 15 11:42:23 mybox wickedd-dhcp4[5621]: br0: Committed DHCPv4 lease with address 100.66.111.3 (lease time 604800, renew in 302400 sec, rebind in 529200 sec) Feb 15 11:56:47 mybox wickedd-dhcp4[5621]: br0: Request to acquire DHCPv4 lease with UUID ...-000010000000 Feb 15 11:57:02 mybox wickedd-dhcp4[5621]: br0: defer timeout 15 reached in state REBOOT Feb 15 11:57:02 mybox wickedd-dhcp4[5621]: br0: Committed DHCPv4 lease with address 100.66.111.3 (lease time 603921, renew in 301521 sec, rebind in 528321 sec) Feb 15 11:57:39 mybox wickedd-dhcp4[5621]: br0: Request to drop DHCPv4 lease with UUID ...-000010000000: starting... Feb 15 11:57:45 mybox systemd[1]: Stopping wicked DHCPv4 supplicant service... Feb 15 11:57:45 mybox systemd[1]: wickedd-dhcp4.service: Deactivated successfully. Feb 15 11:57:45 mybox systemd[1]: Stopped wicked DHCPv4 supplicant service.
But how I can configure wickedd-dhcp4 so, that it logs more details?
You need to to capture network traffic to see what really happens.
participants (2)
-
Andrei Borzenkov
-
Bjoern Voigt