From nobody Sat Aug 05 11:39:54 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RJ0xh73Nsz4gwFb for ; Sat, 5 Aug 2023 11:40:08 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.flex-it.com.ua (mail.flex-it.com.ua [193.239.74.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RJ0xb2Mfpz3L3f for ; Sat, 5 Aug 2023 11:40:03 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of shuriku@shurik.kiev.ua designates 193.239.74.7 as permitted sender) smtp.mailfrom=shuriku@shurik.kiev.ua; dmarc=none Received: from 93.183.208.50.ipv4.datagroup.ua ([93.183.208.50] helo=[192.168.200.125]) by mail.flex-it.com.ua with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.96 (FreeBSD)) (envelope-from ) id 1qSFdT-0003hm-0L for freebsd-current@freebsd.org; Sat, 05 Aug 2023 14:39:55 +0300 Message-ID: Date: Sat, 5 Aug 2023 14:39:54 +0300 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: Fwd: Unreliability with DHCP Content-Language: uk-UA To: freebsd-current@freebsd.org References: <62d300c8-2c3e-58fa-334e-23a17962279a@freebsd.org> From: Oleksandr Kryvulia In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ACL-Warn: SPF failed. 93.183.208.50 is not allowed to send mail from shurik.kiev.ua. X-Spamd-Result: default: False [1.41 / 15.00]; NEURAL_SPAM_MEDIUM(1.00)[0.999]; NEURAL_SPAM_SHORT(0.71)[0.710]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:35297, ipnet:193.239.72.0/22, country:UA]; BLOCKLISTDE_FAIL(0.00)[93.183.208.50:query timed out,193.239.74.7:query timed out]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[shurik.kiev.ua]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Spamd-Bar: + X-Rspamd-Queue-Id: 4RJ0xb2Mfpz3L3f 04.08.23 19:07, Graham Perrin пише: > > Can anyone from freebsd-net@ help? > > > -------- Forwarded Message -------- > Subject: Unreliability with DHCP > Date: Sun, 30 Jul 2023 16:17:43 +0100 > From: Graham Perrin > Organisation: FreeBSD > To: FreeBSD CURRENT > > > > 1. Sleep (suspend) whilst connected to one network > > 2. connect to a network elsewhere > > 3. wake (resume). > > Result: > > /etc/resolv.conf frequently contains outdated information. In some > (maybe all) such cases, the IPv4 inet address is outdated; and so on. > > Which /etc/rc.d/ file(s) should I attempt to fix? > > I imagine using the resume keyword, which is currently used by only > one script: > > % rcorder -k resume /etc/rc.d/* > /etc/rc.d/ntpd > % > > > I routinely run the command below to work around the bug (and observe > the states of things) – run _after_ the bug bites. I'd prefer a fix, > to prevent the bites. > > ls /var/run/resolvconf/interfaces/ ; route delete default ; ifconfig > wlan0 down && ifconfig em0 down && sleep 5 ; ls > /var/run/resolvconf/interfaces/ ; ifconfig em0 up && sleep 15 > ; ls /var/run/resolvconf/interfaces/ ; cat /etc/resolv.conf ; ping -c > 2 -4 freshports.org > As dirty workaround I have in my /etc/rc.resume service netif restart service routing restart