Date: Sun, 6 Aug 2023 10:36:42 +0300 From: Oleksandr Kryvulia <shuriku@shurik.kiev.ua> To: freebsd-current@freebsd.org Subject: Re: service routing restart (was: Unreliability with DHCP) Message-ID: <adc80040-3a59-abeb-d92f-f225d16d7171@shurik.kiev.ua> In-Reply-To: <354756c9-29e0-db1f-269e-3c219b5d9ac8@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>
next in thread | previous in thread | raw e-mail | index | archive | help
06.08.23 01:35, Graham Perrin пише: > On 05/08/2023 23:16, Graham Perrin wrote: >> On 05/08/2023 12:39, Oleksandr Kryvulia wrote: >>> 04.08.23 19:07, Graham Perrin пише: >>>> >>>> … >>>> >>> >>> As dirty workaround I have in my /etc/rc.resume >>> >>> service netif restart >>> service routing restart >> >> … 'service routing restart' can be problematic. Please, see, for >> example, <https://pastebin.com/raw/mXmVPruq>; I had something similar >> a few minutes ago. >> > After 'service routing restart' (alone), should 'route show default' > find a route? > Only if you have static route configuration. 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. Another option is to run 'service dhclient restart wlan0' after routing restart. I have lagg with em0 and wlan0 - thats why I need 'service netif restart' instead.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?adc80040-3a59-abeb-d92f-f225d16d7171>