Help needed to re-connect FreeBSD to internet
bourne.identity at hotmail.com
Wed Mar 9 13:54:36 UTC 2016
On 03/09/16 13:39, chris at bsdjunk.com wrote:
> On 2016-03-09 01:59, Manish Jain wrote:
>> 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
>> ether 50:46:5d:66:fd:10
>> inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
>> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>> media: Ethernet autoselect (100baseTX <full-duplex>)
>> 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 :
>> # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
>> Can someone please point me to what might be the error/changes needed
>> for my FreeBSD box to connect to internet again ? Thank you.
>> Manish Jain
> By the looks of it you changed the IP but forgot to add the default
> 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
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.
More information about the freebsd-questions