Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Jun 2018 23:37:07 +0200
From:      Polytropon <>
To:        B J <>
Cc:, Chris Gordon <>, freebsd-questions <>, Erich Dollansky <>
Subject:   Re: Problems Connecting Laptop To Modem
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Fri, 15 Jun 2018 20:49:12 +0000, B J wrote:
> On 6/15/18, Gary Aitken <> wrote:
> <snip>
> > You can't just add the default router line without a bit of knowledge
> > about what the IP address of the default router actually is.  Do you
> > know what the 192.168.0.* address for the router is?  I suggested
> > because that is often the default, but not necessarily so.
> I eventually found that was the value from one of my tower
> machines.  I tried other values for the last number as well and got
> the same result.

>From your netstat output (later on), it seems that you
connect to, so if this really is the IP of
one of your machines, there's a big problem with your
current configuration.

> >> That might be worth considering, but I don't have to do it with my
> >> other FreeBSD machines.
> >
> > Can you post the result of "netstat -rn" from one of those other
> > machines?
> <snip>
> Routing tables
> Internet:
> Destination        Gateway            Flags     Netif Expire
> default          UGS        fxp0
>          link#2             UH          lo0
>     link#1             U          fxp0
>       link#1             UHS         lo0
> Internet6:
> Destination                       Gateway                       Flags
>    Netif Expire
> ::/96                             ::1                           UGRS        lo0
> ::1                               link#2                        UH          lo0
> ::ffff:                 ::1                           UGRS        lo0
> fe80::/10                         ::1                           UGRS        lo0
> fe80::%fxp0/64                    link#1                        U          fxp0
> fe80::21a:92ff:fe10:ce8b%fxp0     link#1                        UHS         lo0
> fe80::%lo0/64                     link#2                        U           lo0
> fe80::1%lo0                       link#2                        UHS         lo0
> ff02::/16                         ::1                           UGRS        lo0
> I've had no problem with the machine where this came from.  I just
> checked the laptop using a live version of Ubuntu and I was able to
> connect to the Internet with it.  The hardware, it would seem, doesn't
> appear to be the main problem.

At the moment, it doesn't look like a hardware issue.

My suggestion:

Take a machine that properly connects to your modem/router and
gains Internet access this way as desired. Collect information
about which values exist on your network. Don't guess values. :-)

The following commands should work on FreeBSD and Linux:

	# arp -a

	# netstat -rn

	# ifconfig -a

(depending on Linux, the "ip" program has to be used instead)

Even though it might sound stupid, use pen & paper to make a
small diagram of your network. Write down the IPs and other
elements of the configuration.

If you have a Linux live system connecting without any further
configuration, it's quite possible you have a DHCP server in
your modem/router running. In that case, don't try to configure
things manually, it will just interfere with this mechanism.
Instead, use


in /etc/rc.conf. A variation is


Check /etc/rc.conf for duplicate entries. The _last_ entry
of the same kind will be in effect, as it's basically just
a shell script with assignments to shell variables.

Of course you need to specify the default router address, but
don't guess it - determine it from a different system. If it
is the _default_ address that your modem/router uses (and you
didn't change it), maybe consult its documentation, the address
should be listed there. It can be things like,,, who knows.

Check if HDCP populated /etc/resolv.conf. In many settings,
the modem/router will also be a nameserver (even if it just
"relays" your queries and the replies). This means: The IP
you're seeing there is the IP of your modem/router.

In worst case, don't configure anything in /etc/rc.conf and do
a little experimentation. Run a tcpdump (or maybe Wireshark,
ex Ethereal) on your network interface and then do all the steps
manually: Configure the interface, set default routing, try to
obtain an IP via DHCP (using dhclient), and see it /etc/resolv.conf
gets populated (which DHCP should fill with the correct values).
Then try to ping internally with IP, extermally with IP, try to
resolve a hostname, ping it, open a browser for a HTTP connection,
and so on. Monitor what you're doing as initially mentioned (to
see if you actually _see_ what you expect, like ARP messages,
a DHCP handshake, ICMP pings, and HTTP traffic). If this all
works, make the settings permanent - even if you only verified
that using DHCP was the correct thing to begin with. :-)

Good luck!

"Trial & error" is not a programming concept. ;-)

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Want to link to this message? Use this URL: <>