From owner-freebsd-questions@freebsd.org Wed Mar 9 08:11:44 2016 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 A948E9DB58B for ; Wed, 9 Mar 2016 08:11:44 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7323CF82 for ; Wed, 9 Mar 2016 08:11:43 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-185-40.dynamic.qsc.de [92.195.185.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id A2E4B254AE; Wed, 9 Mar 2016 09:11:34 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u298BYZg002923; Wed, 9 Mar 2016 09:11:34 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Wed, 9 Mar 2016 09:11:34 +0100 From: Polytropon To: Manish Jain Cc: User Questions Subject: Re: Help needed to re-connect FreeBSD to internet Message-Id: <20160309091134.59049c66.freebsd@edvax.de> In-Reply-To: References: 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-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 08:11:44 -0000 On Wed, 9 Mar 2016 13:29:10 +0530, Manish Jain wrote: > Help from the service provider got the Windows system working again. I > enabled Internet Connection Sharing and replaced DHCP with 192.168.10.3 > for the PC and 192.168.10.1 for the Wi-Fi modem (default_router). While > the Windows connects to the internet now, the FreeBSD box remains stuck > with roughly those same settings. You should now reproduce the change of settings that made "Windows" connect again with FreeBSD. Probably you have wrong configuration there. > ifconfig re0 : > re0: flags=8843 metric 0 mtu 1500 > options=8209b > > ether 50:46:5d:66:fd:10 > inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > nd6 options=29 > media: Ethernet autoselect (100baseTX ) > status: active You don't have an IP associated with the netword interface. As you stated above, 192.168.10.3 is now to be used for the PC. Adjust /etc/rc.conf accordingly: ifconfig_re0="inet 192.168.10.3 netmask 0xffffff00" That should bring the desired functionality back. Also check with the provider if there was any change regarding name servers or default gateway. > pinging 192.168.1.1 produces 'no route to host' and 100.0% packet loss. Expected. > At boot-time, the system seems to attempt getting a DHCP lease multiple > times without success. Obviously, there is no "DHCP server" in the modem anymore, and as you've configured a static IP for "Windows", doing the same for FreeBSD should work. Remove ifconfig_re0="DHCP" from /etc/rc.conf (or put a # infront of it). > cat /etc/resolv.conf : > > nameserver 192.168.1.1 Hmmm... that's outside of your subnet (which is 192.168.10.*). > cat /etc/rc.conf : > > hostname="freebsd10dot2.amd64.local" > ifconfig_re0="DHCP" ^^^^ This is the problem. FreeBSD expects a DHCP server to assign it an IP address, but there is none (as you had to manually configure a static IP for the client). > Can someone please point me to what might be the error/changes needed > for my FreeBSD box to connect to internet again ? Thank you. The same change as in "Windows". You might even be able to check (maybe required) different settings for gateway and NS from the running (working) "Windows" instance. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...