From owner-freebsd-questions@freebsd.org Mon Jun 18 15:24:00 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80C7B100E0C9 for ; Mon, 18 Jun 2018 15:24:00 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (ns.dreamchaser.org [66.109.141.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dreamchaser.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB15C840D5 for ; Mon, 18 Jun 2018 15:23:59 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from breakaway.dreamchaser.org (breakaway [192.168.151.122]) by nightmare.dreamchaser.org (8.15.2/8.15.2) with ESMTP id w5IFNo41029247; Mon, 18 Jun 2018 09:23:51 -0600 (MDT) (envelope-from freebsd@dreamchaser.org) Reply-To: freebsd@dreamchaser.org Subject: Re: Problems Connecting Laptop To Modem To: B J Cc: Erich Dollansky , Chris Gordon , freebsd-questions References: <20180613102426.3874c581.freebsd.ed.lists@sumeritec.com> <20180613162137.5cc6794a.freebsd.ed.lists@sumeritec.com> <3E3890A6-72F9-4D80-A021-837FFDB35A39@theory14.net> <20180614093928.6f39434e.freebsd.ed.lists@sumeritec.com> <20180614161923.5246ae81.freebsd.ed.lists@sumeritec.com> <20180615102548.1c686d1b.freebsd.ed.lists@sumeritec.com> From: Gary Aitken Message-ID: Date: Mon, 18 Jun 2018 09:23:07 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (nightmare.dreamchaser.org [192.168.151.101]); Mon, 18 Jun 2018 09:23:51 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2018 15:24:00 -0000 On 06/15/18 14:49, B J wrote: > On 6/15/18, Gary Aitken wrote: >> 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 >> 192.168.0.1 because that is often the default, but not necessarily so. > > I eventually found that 192.168.0.1 was the value from one of my tower > machines. I tried other values for the last number as well and got > the same result. > >> >>> 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? > > > > Routing tables > > Internet: > Destination Gateway Flags Netif Expire > default 192.168.0.1 UGS fxp0 > 127.0.0.1 link#2 UH lo0 > 192.168.0.0/24 link#1 U fxp0 > 192.168.0.12 link#1 UHS lo0 This looks like the routing table for the machine which is not working, with the default set to 192.168.0.1. If you run "netstat -rn" from one of the machines which *is* working (as suggested above), it should show a default route with the IP address of the actual router. That is the IP address you need to use on the machine which is not working. Gary