Date: Mon, 7 Aug 2023 13:28:11 +0300 From: Oleksandr Kryvulia <shuriku@shurik.kiev.ua> To: freebsd-current@freebsd.org Subject: Re: service routing restart, service dhclient restart (was: Unreliability with DHCP) Message-ID: <06344516-ceb3-4aea-dcdb-720a19dd6e45@shurik.kiev.ua> In-Reply-To: <f1585a70-d3cd-33d6-77b4-b7eed16abb8a@freebsd.org> 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> <f1585a70-d3cd-33d6-77b4-b7eed16abb8a@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
06.08.23 19:23, Graham Perrin пише: > 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? It's my own expirience + reading /etc/rc.d/routing > > >> Another option is to run 'service dhclient restart wlan0' after >> routing restart. … > > Is there, similarly, a need to rush the two commands? I can't answer for sure, you need to try different options and choose the one that works. If you're using typical network configuration, you'll probably be fine with routing restart + dhclient restart only. This works for me in most cases until I configured lagg interface. > > <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?06344516-ceb3-4aea-dcdb-720a19dd6e45>