Date: Sun, 6 Aug 2023 17:23:55 +0100 From: Graham Perrin <grahamperrin@freebsd.org> To: freebsd-current@freebsd.org Subject: service routing restart, service dhclient restart (was: Unreliability with DHCP) Message-ID: <f1585a70-d3cd-33d6-77b4-b7eed16abb8a@freebsd.org> In-Reply-To: <adc80040-3a59-abeb-d92f-f225d16d7171@shurik.kiev.ua> References: <62d300c8-2c3e-58fa-334e-23a17962279a@freebsd.org> <e5e80c42-08c3-140b-b53b-a13ffbf01ff7@freebsd.org> <ceac6410-fcff-8020-ecee-e7953eb29078@shurik.kiev.ua> <753f3990-9903-3718-445c-49fc01f960a7@freebsd.org> <354756c9-29e0-db1f-269e-3c219b5d9ac8@freebsd.org> <adc80040-3a59-abeb-d92f-f225d16d7171@shurik.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks, On 06/08/2023 08:36, Oleksandr Kryvulia wrote: > … In my case default route is assigned by dhclient, so 'service > routing restart' must be run quickly after 'service netif restart' - > before we receive dhcp offer. Is this documented and explained somewhere, or did you learn through trial and error? > Another option is to run 'service dhclient restart wlan0' after > routing restart. … Is there, similarly, a need to rush the two commands? <https://reviews.freebsd.org/P602$27>; no route; <https://reviews.freebsd.org/P602$28-33>; /etc/rc.d/dhclient: WARNING: failed to start dhclient
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f1585a70-d3cd-33d6-77b4-b7eed16abb8a>