Date: Tue, 20 Jun 2023 02:28:32 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 272086] dhclient increase retry delay too high, ignore settings Message-ID: <bug-272086-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272086 Bug ID: 272086 Summary: dhclient increase retry delay too high, ignore settings Product: Base System Version: 13.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: rozhuk.im@gmail.com My config is: timeout 60; retry 4; select-timeout 0; reboot 8; backoff-cutoff 16; initial-interval 16; Log: Jun 19 15:34:56 firewall dhclient[16291]: send_packet: No route to host Jun 19 15:34:56 firewall kernel: [384699] Jun 19 15:34:56 firewall dhclient[16291]: send_packet: No route to host Jun 19 15:35:12 firewall dhclient[16291]: send_packet: No route to host Jun 19 15:35:32 firewall syslogd: last message repeated 1 times Jun 19 15:35:32 firewall kernel: [384734] Jun 19 15:35:32 firewall syslogd: last message repeated 2 times Jun 19 15:35:45 firewall dhclient[16291]: send_packet: No route to host Jun 19 15:36:14 firewall syslogd: last message repeated 1 times Jun 19 15:37:40 firewall syslogd: last message repeated 2 times Jun 19 15:37:40 firewall kernel: [384862] Jun 19 15:37:40 firewall syslogd: last message repeated 4 times Jun 19 15:37:52 firewall dhclient[16291]: send_packet: No route to host Jun 19 15:38:15 firewall syslogd: last message repeated 2 times Jun 19 15:40:21 firewall syslogd: last message repeated 5 times Jun 19 15:45:52 firewall syslogd: last message repeated 3 times Jun 19 15:47:55 firewall kernel: [385477] Jun 19 15:45:52 firewall syslogd: last message repeated 11 times Jun 19 15:49:04 firewall dhclient[16291]: send_packet: No route to host Jun 19 15:55:39 firewall syslogd: last message repeated 1 times Jun 19 15:57:55 firewall kernel: [386077] Jun 19 15:55:39 firewall syslogd: last message repeated 2 times Jun 19 16:04:48 firewall dhclient[16291]: send_packet: No route to host Jun 19 16:07:55 firewall kernel: [386678] Jun 19 16:04:48 firewall syslogd: last message repeated 1 times Jun 19 16:19:52 firewall dhclient[16291]: send_packet: No route to host Jun 19 16:19:52 firewall kernel: [387395] Jun 19 16:19:52 firewall syslogd: last message repeated 1 times Jun 19 16:43:59 firewall dhclient[16291]: send_packet: No route to host Jun 19 16:43:59 firewall kernel: [388842] Jun 19 16:43:59 firewall syslogd: last message repeated 1 times Jun 19 17:52:43 firewall dhclient[16291]: send_packet: No route to host Jun 19 17:52:43 firewall kernel: [392965] Jun 19 17:52:43 firewall syslogd: last message repeated 1 times Jun 19 19:40:21 firewall dhclient[16291]: send_packet: No route to host Jun 19 19:40:21 firewall kernel: [399423] Jun 19 19:40:21 firewall syslogd: last message repeated 1 times Jun 19 23:25:24 firewall dhclient[16291]: send_packet: No route to host Jun 19 23:25:24 firewall kernel: [412926] Jun 19 23:25:24 firewall syslogd: last message repeated 1 times Jun 20 02:26:26 firewall root[4421]: vlan886 ADDR_DEL 176.99.147.0 lease { interface "vlan886"; fixed-address 176.99.147.0; next-server 176.99.128.28; option subnet-mask 255.255.248.0; option routers 176.99.144.1; option domain-name-servers 194.187.204.254,194.187.205.226; option broadcast-address 176.99.151.255; option dhcp-lease-time 86400; option dhcp-message-type 5; option dhcp-server-identifier 10.204.46.1; renew 1 2023/6/19 01:43:28; rebind 1 2023/6/19 10:43:28; expire 1 2023/6/19 13:43:28; } lease { interface "vlan886"; fixed-address 176.99.147.0; next-server 176.99.128.28; option subnet-mask 255.255.248.0; option routers 176.99.144.1; option domain-name-servers 194.187.204.254,194.187.205.226; option broadcast-address 176.99.151.255; option dhcp-lease-time 78177; option dhcp-message-type 5; option dhcp-server-identifier 10.204.46.1; renew 1 2023/6/19 12:34:56; rebind 1 2023/6/19 20:43:32; expire 1 2023/6/19 23:26:25; } After 15:47:55 something goes wrong and client start increase retry timeout. System connected via switch and link was stable, but ISP line outside was d= own for a while. ISP probably drop my DHCP lease and reassing my IP address to some other customer, and possible block all non DHCP DISCOVER requests. I do expect that dhclient will retry at least every 60 seconds, according to max value in config file, but it sleep for hours. Another issue is in case "No route to host" dhclient probably should restart with DISCOVER. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272086-227>