From owner-freebsd-questions@freebsd.org Wed Apr 12 02:56:41 2017 Return-Path: Delivered-To: freebsd-questions@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 E04CED3ABF6 for ; Wed, 12 Apr 2017 02:56:41 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay13.qsc.de (mailrelay13.qsc.de [212.99.187.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 67615960 for ; Wed, 12 Apr 2017 02:56:40 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay13.qsc.de; Wed, 12 Apr 2017 04:56:32 +0200 Received: from r56.edvax.de (port-92-195-127-117.dynamic.qsc.de [92.195.127.117]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id AC5FE3CBF9; Wed, 12 Apr 2017 04:56:31 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v3C2uUHj004388; Wed, 12 Apr 2017 04:56:30 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Wed, 12 Apr 2017 04:56:30 +0200 From: Polytropon To: Ernie Luzar Cc: Manish Jain , "freebsd-questions@freebsd.org" Subject: Re: Setting up a minimal KDE Message-Id: <20170412045630.d6515500.freebsd@edvax.de> In-Reply-To: <58ED86C0.9000300@gmail.com> References: <58ED1780.3010603@gmail.com> <58ED86C0.9000300@gmail.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay13.qsc.de with EB6CF6A0201 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1232 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Apr 2017 02:56:42 -0000 On Tue, 11 Apr 2017 21:45:36 -0400, Ernie Luzar wrote: > Manish Jain wrote: > > > > > > On Tue, Apr 11, 2017 at 11:20 PM, Ernie Luzar wrote: > >> Manish Jain wrote: > > [...] > > > > As for the DHCP problem that remains outstanding, this is what my > > rc.conf has : > > > > ifconfig_re0="inet 192.168.1.94 netmask 255.255.255.0" > > defaultrouter="192.168.1.1" > > > > That rc clearly states that I need a static configuration. But dhclient > > still runs at system startup, losing me over a minute each time. > > > > Regards > > Manish Jain > > What makes you think dhclient is running at boot time? > > You previously stated "Because my network interface is statically > configured." What that means is your isp issued you an static ip address > that you purchased and as such there is no auto host configuration offered. That isn't neccessarily the case. The IP 192.168.1.94 suggests that he's behind some kind of router/switch/whatever that has been configured to use static IPs. It's possible to do so even if your ISP hands you a "random" IP every time you connect. If the connection device doesn't offer DHCP services, then of course running dhclient won't bring any success. :-) > I would guess that what you are experiencing is a dns timeout during the > boot process. When you are issued a static ip address from your isp > there is more manual configuration needed than just what you did in > rc.conf. You also have to manually configure the /etc/resolv.conf file > with the isp's two dns ip addresses. Did you do that? Valid point. Without DHCP, this file is usually being maintained manually. A precise check of _when_ during the boot process the delay does occur would be a helpful indicator of _what_ is causing the delay. DNS might be such a thing. > Also 192.168.x.x is reserved for private LAN use. That ip address is not > routeable over the public internet and was never issued by your isp as a > static ip address. I hope you just used that for the post to not expose > your real static ip address other wise you have bigger problems that > what you have posted. Or it's just one of the cases where your ISP makes you use a device to connect that is more than just a simple DSL modem. For example, I'm using a Fritz!Box to connect to my ISP, and behind that box, everything is 192.168.*.*. The box itself contains a DSL modem, a phone "splitter" (so I can connect ye olden POTS phones as well as one ISDN S0 phone), a switch for 4 network sockets, a DHCP server, a router, a WLAN facility, a "port redirector and mapper" and many other more or less useless things maintained in software. I can use both DHCP and (to be precise: or!) static IP configuration for the devices I connect. Therefore, ifconfig_re0="inet 192.168.1.94 netmask 255.255.255.0" could be a totally valid setting. However, such a setting on its own does not cause dhclient to be called, nor does it cause a delay during boot; a different configuration hick-up might, though. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...