From owner-freebsd-questions@freebsd.org Fri Jun 15 21:37:42 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 44403101D929 for ; Fri, 15 Jun 2018 21:37:42 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B037184F91 for ; Fri, 15 Jun 2018 21:37:41 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.97.38]) by mrelayeu.kundenserver.de (mreue105 [212.227.15.183]) with ESMTPA (Nemesis) id 0Mgw8O-1fpzXC11ge-00M6Y4; Fri, 15 Jun 2018 23:37:10 +0200 Date: Fri, 15 Jun 2018 23:37:07 +0200 From: Polytropon To: B J Cc: freebsd@dreamchaser.org, Chris Gordon , freebsd-questions , Erich Dollansky Subject: Re: Problems Connecting Laptop To Modem Message-Id: <20180615233707.8645c246.freebsd@edvax.de> In-Reply-To: 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> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:Bl1VWHZEk9dczOZEJ4A8OCzCIclzhsCqHFDpT8Tk8sciJT/A94f RI9uUjPSGhLcNgFFlYTE2+t3lfEm2mxBCD2Z405RGXre5SLMIqR83ZCsU/S6KCfEVF2seAX xzqJL3zxxSeHuMzePdI6IvCumHfbJEDyQXl3KjttDgUDAVA0LFicUtNRuuLafftosu9Ffmv GFr2kaHjVO7zAbfRS8Ibg== X-UI-Out-Filterresults: notjunk:1;V01:K0:HSYIx7f7jh0=:0k3R7xasxAy+w8vuFJZFNP HEOsKZEwCRIhFGEeKqdyWJo4e36NNiy0qSqJyS2xwrejWJ1+/sPLitN8UHxe+RX7R48mml6Rj lWVJoZMQmJS+t0FwJSYJug82R3HqcGzDHiSfggv69MDXoHWZyorVcJclb2XCSMufyZh/Tw8LX wbChHZg+bhxjTu+mnYOpMJmaEUcYtyok/qgCAcenandDPR6ySsmm4Ga1KJwKeWSCAFlkmauyg 1gYRlwy0Lvsyq4jzCba0Du09a8uCTTqQ3Kn22ZOYudK7C1eoFkN3tnGvlqNwLh8/qRjJJVQg7 0Mb5tiGMwZXAiMeVKWmxIU7zUYoyMyVmSxbf+kZyLe1LOCQKrzXTflEgFEAdv/Jys/OWvrSr0 bzcnler8gHY6DvmuU13Qu3xSMJ5RRb1s64KoN5rywZSemo180rFYQGBo3/eDue/WiT4KIRFZc DNC6PT4STjfMin0vCioGgvU/M8QS74jV8Sfg6zvrp4bDQh1bUemBzowUo07yZJ4Z1wbbqeI6a Y5WkOQ49XKa6e0+Q8QODUapUPMeTDVm/58nRBNAbBYaN8vvB/DZq70AKNlotZHnYLdF8bfxES krzZUyge1C9cZY/N5gpQyNUN57T9Y1rmiF493CGgpVDK4oXNpQGkBkpAjfmLC0K/77lRB1wb+ rjd6Tq/3FT8hNaO2IqLBfguBwcDbb8tpH+KH3HH9jpx9XQOLAkXpZkhfJHf2vF0h7wpQFLxEm /kFrC0/Vn35/4wiW 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: Fri, 15 Jun 2018 21:37:42 -0000 On Fri, 15 Jun 2018 20:49:12 +0000, 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. >From your netstat output (later on), it seems that you connect to 192.168.0.1, 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? > > > > 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 > > Internet6: > Destination Gateway Flags > Netif Expire > ::/96 ::1 UGRS lo0 > ::1 link#2 UH lo0 > ::ffff:0.0.0.0/96 ::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 ifconfig_nfe0="DHCP" in /etc/rc.conf. A variation is ifconfig_nfe0="SYNCDHCP" 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 192.168.0.1, 192.168.1.1, 192.168.178.1, 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! PS. "Trial & error" is not a programming concept. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...