From owner-freebsd-net@freebsd.org Thu May 25 17:10:12 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 814E7D82C29 for ; Thu, 25 May 2017 17:10:12 +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 5C15C1B71 for ; Thu, 25 May 2017 17:10:12 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id v4PHA4eU017413 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 25 May 2017 10:10:05 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me To: "freebsd-net@freebsd.org" From: Yuri Subject: dhclient vs. dhcpcd Message-ID: <97050ce3-ad75-c3dc-c106-3bd608e7aa8e@rawbw.com> Date: Thu, 25 May 2017 10:10:03 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2017 17:10:12 -0000 I came across the WiFi router through which dhclient fails to obtain the IP address. It sets 0.0.0.0 and it stays this way, On the other hand, dhcpcd obtains the IP address almost instantly. Other routers mostly don't have such problem. Is dhclient not as robust, or outdated as compared to dhcpcd? Yuri