gregoryb wrote: ↑04 Feb 2020, 16:03
But Lynx still works 'without' Internet connection!.. :/
Any browser would work without intertubes connection, so long as you only browse local files, that is.
Usually that is not what folks want with a browser, though.
To make sure if your intertubes work okay, do the following:
Open a terminal window as normal user (usually you will be "guest")
Then do type "ping google.com" and press enter.
You should get something like this:
Code: Select all
$ ping google.com
PING google.com (172.217.22.110) 56(84) bytes of data.
64 bytes from fra15s18-in-f14.1e100.net (172.217.22.110): icmp_seq=1 ttl=53 time=44.6 ms
64 bytes from fra15s18-in-f14.1e100.net (172.217.22.110): icmp_seq=2 ttl=53 time=54.9 ms
64 bytes from fra15s18-in-f14.1e100.net (172.217.22.110): icmp_seq=3 ttl=53 time=49.0 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 44.620/49.515/54.943/4.231 ms
Cave! The ping command would go one forever. Cancel it with Ctrl+C like I did above.
When cancelling it like this it can happen that the very last ping was not successful due to the cancellation. When all other pings prior to the last one report a success then all is well.
When there is s connection issue, e.g. ping telling you to be unable to resolve "google.com", then try the following:
Open a root terminal or go to a normal terminal and type "su -"
You will be asked for the root password.
Type "traceroute google.com" or use the local variant for google, like google.de for Germany:
Code: Select all
# traceroute google.de
[removed first 6 entries]
7 72.14.214.170 (72.14.214.170) 45.424 ms 47.388 ms 50.019 ms
8 * * *
9 209.85.252.208 (209.85.252.208) 68.996 ms 209.85.252.210 (209.85.252.210) 72.577 ms 74.125.244.97 (74.125.244.97) 75.484 ms
10 74.125.244.82 (74.125.244.82) 76.369 ms 47.800 ms 108.170.247.120 (108.170.247.120) 56.770 ms
11 172.253.70.103 (172.253.70.103) 66.850 ms 172.253.70.79 (172.253.70.79) 79.556 ms 172.253.70.103 (172.253.70.103) 76.793 ms
12 209.85.143.222 (209.85.143.222) 51.317 ms 54.882 ms 172.253.79.190 (172.253.79.190) 75.609 ms
13 72.14.239.166 (72.14.239.166) 93.254 ms 209.85.242.78 (209.85.242.78) 93.804 ms 72.14.239.166 (72.14.239.166) 98.951 ms
14 108.170.251.129 (108.170.251.129) 100.291 ms 108.170.252.1 (108.170.252.1) 100.444 ms 102.415 ms
15 72.14.232.33 (72.14.232.33) 112.372 ms 72.14.232.35 (72.14.232.35) 113.048 ms 114.361 ms
16 fra15s17-in-f3.1e100.net (172.217.22.67) 114.315 ms 73.910 ms 105.134 ms
When it looks similar like the above, again all is well.
When it is not able to reach the target then traceroute will tell you so, then post the info here and someone will try to assist you.