From owner-freebsd-net@freebsd.org Sat Mar 23 17:30:38 2019 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20310155716F for ; Sat, 23 Mar 2019 17:30:38 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4BB1F72500 for ; Sat, 23 Mar 2019 17:30:37 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-4-39-254.hsd1.ca.comcast.net [24.4.39.254]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id x2NHUXda014189 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 23 Mar 2019 10:30:35 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-4-39-254.hsd1.ca.comcast.net [24.4.39.254] claimed to be yv.noip.me Subject: Re: dhclient fails to obtain the IP address from some WiFi networks To: Nash Kaminski , Christian Cc: freebsd-net@freebsd.org References: <1718f323-6c12-9a4c-ca70-11bd15cbb7c5@rawbw.com> From: Yuri Message-ID: <16fe29ea-fa8b-2a37-6e3a-4f9ee3edfa29@rawbw.com> Date: Sat, 23 Mar 2019 10:30:32 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4BB1F72500 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of yuri@rawbw.com designates 198.144.192.42 as permitted sender) smtp.mailfrom=yuri@rawbw.com X-Spamd-Result: default: False [-5.76 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[254.39.4.24.zen.spamhaus.org : 127.0.0.10]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:198.144.192.32/27]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; DMARC_NA(0.00)[rawbw.com]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mx.rawbw.net]; NEURAL_HAM_SHORT(-0.81)[-0.811,0]; RCVD_IN_DNSWL_NONE(0.00)[42.192.144.198.list.dnswl.org : 127.0.10.0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-2.74)[ip: (-5.12), ipnet: 198.144.192.0/19(-4.74), asn: 7961(-3.79), country: US(-0.07)]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7961, ipnet:198.144.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Mar 2019 17:30:38 -0000 On 3/23/19 9:42 AM, Nash Kaminski wrote: > It appears that you actually may have had an address assigned, but then > had it removed ~30 seconds later when the interface was brought down by > wpa_supplicant. I also ran dhclient by hand, and it never said that it obtained the lease. It would just say that it requested the lease, again and again after the increasing time interval, and eventually it would just say "Using the recorded lease ...". So dhclient is the process that was failing, I think. Yuri