Date: Tue, 19 Jun 2018 11:52:18 +0200 From: Polytropon <freebsd@edvax.de> To: Erich Dollansky <freebsd.ed.lists@sumeritec.com> Cc: B J <va6bmj@gmail.com>, freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Problems Connecting Laptop To Modem Message-ID: <20180619115218.58b3983e.freebsd@edvax.de> In-Reply-To: <20180619095828.26271eea.freebsd.ed.lists@sumeritec.com> References: <CAP7QzkM7QnymxoOz_ZEUebaOMcE%2BwWmpv7sz6-SzjC0BHG6LCA@mail.gmail.com> <CAP7QzkOzK=7u5Vf0FLdiz6f1%2BSbhme3RpF9MpYUoAJLqTH15qw@mail.gmail.com> <3E3890A6-72F9-4D80-A021-837FFDB35A39@theory14.net> <CAP7QzkNK2qfAL=2-og5oyAY9KLuYVXCfbZ_akbWoEP-xwCP%2BJw@mail.gmail.com> <20180614093928.6f39434e.freebsd.ed.lists@sumeritec.com> <CAP7QzkN6jtukm-ieWEaPsuo6bCTJh0xLdJYOdALVUs6fgSJtwg@mail.gmail.com> <20180614161923.5246ae81.freebsd.ed.lists@sumeritec.com> <CAP7QzkPL5732dh3%2BVmbT6mXxkiYGjUOgiHvUwWBJRk2VJK-y2w@mail.gmail.com> <20180615102548.1c686d1b.freebsd.ed.lists@sumeritec.com> <CAP7QzkODpMCy1TNRpC_-oVmatXE7V1h%2BZEds1R%2B2UCFCu76C%2BA@mail.gmail.com> <ef7f1a05-68c7-c787-5d73-c9848e30acf3@dreamchaser.org> <CAP7QzkPg%2BmQCEePf_DVZCuwybL3MLcNXAgfp1yRETk0qR50BhA@mail.gmail.com> <b6413411-b864-01a4-bfd0-ec9ff6f4d11d@dreamchaser.org> <CAP7QzkNRqe1abscB4cmG8yi%2BmL9=jrzzYzVit1Yjew3d57vpmw@mail.gmail.com> <20180619095828.26271eea.freebsd.ed.lists@sumeritec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Jun 2018 09:58:28 +0800, Erich Dollansky wrote: > Hi, > > On Mon, 18 Jun 2018 17:30:59 +0000 > B J <va6bmj@gmail.com> wrote: > > > On 6/18/18, Gary Aitken <freebsd@dreamchaser.org> wrote: > > > > <snip> > > > > >> 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. > > > > I just ran netstat -rn on the FreeBSD tower I'm running now and the > > default address is identical. I checked the ISP's webpage for the > > modem that that's the address it uses as well. > > > > I tinkered with the laptop this past weekend and I found the > > following: > > > > - the machine won't connect with the modem when even when running a > > liveCD version of FreeBSD (both 10 and 11)--all attempts to ping a URL > > failed > > - the machine updates the file: > > > > /var/db/dhclient.leases.nfe0 > > > > but it doesn't add anything > > - as a test, I created a backup of that file, deleted the original, > > and found that the machine will still create and write to it, but > > doesn't add anything > > - the last update of that file roughly corresponds to the time and > > date when I connected that modem > > > > A while ago, I installed FreeBSD 10.x on an old IBM ThinkPad and I was > > successfully send pings to the same URL as before. > > > > This is becoming interesting.... > > > try this: > > route flush > route add 192.168.0.1 > > You can test now. Try to ping "step by step": first your router by IP, then a public IP address which definitely will answer (for example 8.8.8.8), and then something that involves name resolution (for example www.startpage.com). If name resolution is a problem, the ISP's DNS (or the DNS you are using) should be examined (dig / drill). > If it still does not work, set the network configuration to manual. > Check with the router what address range is reserved for manual usage. > If nothing is reserved, reserve a block of 16, 32 or what ever you like > addresses. Enter one of these addresses into your /etc/rc.conf and try > again. It's still not clear (to me) if the router/modem provides DHCP or not. If it doesn't, manual configuration is needed, but if it does provide DHCP, this should be used - and investigated if it doesn't work as expected. > You also could try to run dhclient manually. I still suggest running tcpdump (or Wireshark) in parallel to see the corresponding traffic. If the machine (for unknown reasons) doesn't get the DHCP handshake right - it needs to perform the required network traffic and should also update certain files and interface settings - there is a reason for it. It would sound strange that a defective network card can cause this strange kind of behaviour, but it's still possible... -- 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?20180619115218.58b3983e.freebsd>