LINUX LITE 7.4 FINAL RELEASED - SEE RELEASE ANNOUNCEMENTS SECTION FOR DETAILS


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Lost internet connection
#1
I am pushing 80 so I am writing this offline because I am concerned it makes sense and I want it to reread it before posting.
First of all. I have an older laptop that I use, it has 2 partition, one is Windows 7 and it seems to be OK. The other is Linux Lite. It is an older version but I can't find a version number, I would say a couple years old.
A couple of years ago I began to have cognitive difficulties and modified Linux Lite desktop so there would as few icons in other words I change the program icons by removing the icon and making the title something meaningful to me.
At some point I realized that I had lost my connection to the internet. In working on that I realized that I have a connection to the local router and I can see all of the other computers in my comcast community.
However, I cannot go to the browser and put in a URL and get a connection. I do have a simple website on my personal network.  That I connect with.
It sound to me as if I have problem connecting with a DNS server. I have tried several URL's for DNS servers.
None of which worked.
If you want to help me keep in mind that I have to read and reply on one partition and test on another.
Thanks to anyone who can provide any help I would prefer step by step instructions.
Jim
Reply
#2
Jim,
Can you run some commands from a terminal window ?
Press the three keys 'Ctrl' 'Alt' and 'T' simultaneously to open a terminal window.

To check your Linux Lite version enter this command followed by enter

Code:
cat /etc/llver

Versions 4.x, 5.x and 6.x are currently supported, although version 4.x is end of support in April 2023.
Version 3.x and earlier are out of support and should not be used to connect to the Internet.

To test basic internet connection and DNS function, run some commands in the terminal window.
Copy the commands carefully.

Code:
ping 8.8.8.8
followed by enter

Allow this to run for about 5 seconds, then terminate command by pressing 'Ctrl' and 'C' together

You should see something like

Quote:PING 8.8.8.8 (8.8.8.8 ) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=118 time=18.2 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=18.2 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=118 time=18.0 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=118 time=18.4 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=118 time=18.5 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=118 time=18.0 ms
^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 17.963/18.210/18.499/0.208 ms

If the number of packets transmitted = packets received, then you have a basic connection and can  test DNS with this.

Code:
ping google.com
followed by enter.

If you get results similar to the text below, DNS is working, so allow it to run for about 5 seconds, then use Ctrl and C as before.

Quote:PING google.com (142.250.180.14) 56(84) bytes of data.
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=1 ttl=118 time=16.5 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=2 ttl=118 time=17.3 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=3 ttl=118 time=16.6 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=4 ttl=118 time=17.2 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=5 ttl=118 time=16.7 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=6 ttl=118 time=17.0 ms
^C
--- google.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 16.496/16.869/17.299/0.307 ms

But if you get something like

Code:
ping: google.com: Temporary failure in name resolution
It indicates DNS is not working.

If you report the results of the above the next steps can be determined.
stevef
clueless
Reply
#3
Responses:
"cat/etc/llver"
'Linux Lite 5.6'

"ping 8.8.8.8"
'Destination host unreachable'

"Ping google.com"
'Temporary failure in name resolution'

That is it so far, next.
Reply
#4
Looks like you may have a problem getting off your local network. The following commands show the interface configuration, the routing table, local devices and test connection to the router.
Please can you run them and post the results ?

Code:
ifconfig -a

Code:
route

Code:
arp -a

Code:
ping _gateway
Allow this one to run for 5 seconds and terminate command with 'ctrl c' as before'
stevef
clueless
Reply
#5
Here is the latest out put. I have a local wifi and an ethernet connection running at the same time.  the machine name is "K501D"

"ifconfig -a"

enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.0.1  netmask 255.255.255.0  broadcast 10.0.0.255
        inet6 fe80::acc8:5f3a:3602:c537  prefixlen 64  scopeid 0x20<link>
        inet6 2601:1c2:4b00:16c0::7a24  prefixlen 128  scopeid 0x0<global>
        inet6 2601:1c2:4b00:16c0:57ae:ef7c:6d22:6e35  prefixlen 64  scopeid 0x0<global>
        ether e0:cb:4e:82:1a:c1  txqueuelen 1000  (Ethernet)
        RX packets 105  bytes 37420 (37.4 KB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 83  bytes 12002 (12.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ipv6leakintrf0: flags=195<UP,BROADCAST,RUNNING,NOARP>  mtu 1500
        inet6 fe80::87d0:9149:5c28:374c  prefixlen 64  scopeid 0x20<link>
        inet6 fdeb:446c:912d:8da::  prefixlen 64  scopeid 0x0<global>
        ether 2a:74:4c:90:fc:95  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 7  bytes 2060 (2.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 2630  bytes 370116 (370.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2630  bytes 370116 (370.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.0.194  netmask 255.255.255.0  broadcast 10.0.0.255
        inet6 2601:1c2:4b00:16c0::1be8  prefixlen 128  scopeid 0x0<global>
        inet6 2601:1c2:4b00:16c0:18c4:6cfa:e0c4:3c7  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::2a69:3f3c:9efc:1bba  prefixlen 64  scopeid 0x20<link>
        ether 00:25:d3:f7:7e:15  txqueuelen 1000  (Ethernet)
        RX packets 150  bytes 44091 (44.0 KB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 106  bytes 17985 (17.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


'route'

Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
default        jim-K50ID      0.0.0.0        UG    100    0        0 enp3s0
default        jim-K50ID      0.0.0.0        UG    600    0        0 wlp4s0
10.0.0.0        0.0.0.0        255.255.255.0  U    100    0        0 enp3s0
10.0.0.0        0.0.0.0        255.255.255.0  U    600    0        0 wlp4s0
link-local      0.0.0.0        255.255.0.0    U    1000  0        0 wlp4s0


'arp -a'
? (66.203.127.14) at <incomplete> on enp3s0
? (10.0.0.238) at 64:e0:03:81:39:e7 [ether] on enp3s0
jim-K50ID (10.0.0.1) at e0:cb:4e:82:1a:c1 [ether] on wlp4s0
? (66.203.127.16) at <incomplete> on enp3s0
? (10.0.0.100) at 90:fb:a6:2b:2f:6d [ether] on enp3s0
? (89.44.169.141) at <incomplete> on enp3s0
? (89.44.169.136) at <incomplete> on enp3s0
? (10.0.0.130) at 00:1d:fe:e8:17:cc [ether] on enp3s0

'

ping _gateway;
PING _gateway(_gateway (fdeb:446c:912d:8da::1)) 56 data bytes
ACCEPTED COMMAND BUT NEVER RETURNED TO THE COMMAND LINE








Reply
#6
A few questions arise from that.

Do you set your network parameters manually (for example through the GUI or by editing system files) or are you on DHCP ?
If you set manually, how have you done this ?
If you have a DHCP server, is it your router or another system on your local network?

What is the IP address of the router you would expect your machine to be using to get to the Internet?
stevef
clueless
Reply
#7
(03-20-2023, 05:51 AM)stevef link Wrote: A few questions arise from that.

Do you set your network parameters manually (for example through the GUI or by editing system files) or are you on DHCP ?

I have tried both ways.  With the same result.

If you set manually, how have you done this ?

I edited it manually with text editor.

If you have a DHCP server, is it your router or another system on your local network?

It used to be on my router but I have tried to shift to one online because the router is COMCAST and I don't trust them.

What is the IP address of the router you would expect your machine to be using to get to the Internet?
1.1.1.1
Reply
#8
Jim,

Quote:It used to be on my router but I have tried to shift to one online because the router is COMCAST and I don't trust them.

I can't for the moment think how a remote online DHCP server would work for a typical home network as DHCP is a local protocol used to allocate valid IP addresses to a system on a LAN.  Perhaps you are confusing DHCP and DNS ?

Quote:1.1.1.1

Are you sure about this ?  If this is really the address used by the router, then your Linux system cannot communicate with the router as they appear to be on different subnets.  This would explain your symptoms.

Quote:I have tried both ways.  With the same result.
Quote:I edited it manually with text editor.

Would you be prepared to undo all the manual changes you've made and set your ethernet port to use DHCP to pick up an address from the router ?  If you cannot recall all the manual changes you've made, switching to DHCP may be enough by itself, but cannot be sure.

Just for comparison, are you doing similar changes when you boot the system as Windows ?
Please run Windows, open a terminal and post the results of
Code:
ipconfig
Code:
route print
Code:
arp -a
stevef
clueless
Reply
#9

Interface: 10.0.0.172 --- 0xa
  Internet Address      Physical Address      Type
  10.0.0.1              bc-d1-65-a0-b4-0f    dynamic 
  10.0.0.100            90-fb-a6-2b-2f-6d    dynamic 
  10.0.0.254            00-05-04-03-02-01    dynamic 
  10.0.0.255            ff-ff-ff-ff-ff-ff    static   
  224.0.0.22            01-00-5e-00-00-16    static   
  224.0.0.252          01-00-5e-00-00-fc    static   
  239.255.255.250      01-00-5e-7f-ff-fa    static   
  255.255.255.255      ff-ff-ff-ff-ff-ff    static   

Interface: 10.0.0.194 --- 0xb
  Internet Address      Physical Address      Type
  10.0.0.1              bc-d1-65-a0-b4-0f    dynamic 
  10.0.0.100            90-fb-a6-2b-2f-6d    dynamic 
  10.0.0.254            00-05-04-03-02-01    dynamic 
  10.0.0.255            ff-ff-ff-ff-ff-ff    static   
  224.0.0.22            01-00-5e-00-00-16    static   
  224.0.0.252          01-00-5e-00-00-fc    static   
  239.255.255.250      01-00-5e-7f-ff-fa    static   
  255.255.255.255      ff-ff-ff-ff-ff-ff    static   

Interface: 192.168.56.1 --- 0x17
  Internet Address      Physical Address      Type
  192.168.56.255        ff-ff-ff-ff-ff-ff    static   
  224.0.0.22            01-00-5e-00-00-16    static   
  224.0.0.252          01-00-5e-00-00-fc    static   
  239.255.255.250      01-00-5e-7f-ff-fa    static   
Reply
#10
Jim,

Is that your Windows arp cache (arp -a)?

It looks like  a conventional network set up.
stevef
clueless
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)