From owner-freebsd-questions@freebsd.org Wed Mar 9 13:54:36 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 EBA82AC97AB for ; Wed, 9 Mar 2016 13:54:35 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU004-OMC2S11.hotmail.com (blu004-omc2s11.hotmail.com [65.55.111.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B60167C3 for ; Wed, 9 Mar 2016 13:54:35 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from BLU436-SMTP98 ([65.55.111.71]) by BLU004-OMC2S11.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 9 Mar 2016 05:54:34 -0800 X-TMN: [vm3aM9leFOPwRDWC0gqyK90e35+zT1aF] X-Originating-Email: [bourne.identity@hotmail.com] Message-ID: Subject: Re: Help needed to re-connect FreeBSD to internet To: chris@bsdjunk.com, Polytropon , freebsd-questions@freebsd.org References: From: Manish Jain Date: Wed, 9 Mar 2016 19:24:18 +0530 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Mar 2016 13:54:31.0531 (UTC) FILETIME=[348C8BB0:01D17A0B] 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 13:54:36 -0000 On 03/09/16 13:39, chris@bsdjunk.com wrote: > On 2016-03-09 01:59, Manish Jain wrote: >> Hi, >> >> I am using a dual-boot machine Windows XP SP3 and FreeBSD 10.2 amd64, >> using a Wi-Fi modem connected to the PC with a LAN cable. Till a >> couple of days back, the systems had no issue connecting to internet >> and the world seemed rosy. All of a sudden, yesterday disaster struck >> and neither was able open up any site in the web browser. >> >> 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. >> >> 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 >> >> pinging 192.168.1.1 produces 'no route to host' and 100.0% packet >> loss. At boot-time, the system seems to attempt getting a DHCP lease >> multiple times without success. >> >> cat /etc/resolv.conf : >> >> nameserver 192.168.1.1 >> >> cat /etc/rc.conf : >> >> hostname="freebsd10dot2.amd64.local" >> ifconfig_re0="DHCP" >> sshd_enable="YES" >> # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable >> dumpdev="AUTO" >> keyrate="fast" >> apcupsd_enable="YES" >> dbus_enable="YES" >> hald_enable="YES" >> gnome_enable="YES" >> linux_enable="YES" >> mysql_enable="YES" >> fusefs_enable="YES" >> atapicam_load="YES" >> cupsd_enable="NO" >> >> >> Can someone please point me to what might be the error/changes needed >> for my FreeBSD box to connect to internet again ? Thank you. >> >> -- >> Regards, >> >> Manish Jain > Hi, > > By the looks of it you changed the IP but forgot to add the default > route. > > http://handbook.bsdjunk.com/network-routing.html > > When using a static IP you're required to add in a infconfig_nic0="" > and defaultroute="" or else it has no where to route the packets. > > once you do that you can test using service netif restart && service > routing restart > > Chris > > Hi Chris/Polytropon, It worked ! The error I was making was using 'default_router' instead of 'defaultrouter' in rc.conf. Using 'bsdconfig networking' sorted that out. I still can't figure though why DHCP was working till the day before. Anyways, thanks a lot. Regards Manish Jain