Date: Wed, 9 Mar 2016 09:11:34 +0100 From: Polytropon <freebsd@edvax.de> To: Manish Jain <bourne.identity@hotmail.com> Cc: User Questions <freebsd-questions@freebsd.org> Subject: Re: Help needed to re-connect FreeBSD to internet Message-ID: <20160309091134.59049c66.freebsd@edvax.de> In-Reply-To: <BLU436-SMTP85601505A5CD7F34C11CD3F6B30@phx.gbl> References: <BLU436-SMTP85601505A5CD7F34C11CD3F6B30@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
>
> 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
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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160309091134.59049c66.freebsd>