Solved Some websites unavailable when changing ISP but only on Linux (and only sometimes)

Solved issue
G

Gears

New Member
Joined
Aug 25, 2024
Messages
10
Reaction score
4
Credits
103
Hello,

OS: Linux Mint 21.3 Cinnamon
Cinnamon Version: 6.0.4
Linux Kernel: 5.15.0-101-generic

I am new to posting problems like this, so excuse me if I don't get it right the first time.

I have this strange issue that only started happening when we changed the ISP here at home. For some reason, all other computers (which are using Windows), can easily and without issue access internet services, while my Linux PC, cannot. The issues it's having are very strange in that, sometimes, on very specific websites, such as Google, Youtube, Reddit, or most of anything that requires login, won't load or will load only partially. This did not happen with the previous ISP.

I did some troubleshooting on my own and have confirmed that it is neither the router nor anything else other than the combination of my Linux computer and the ISP. I am not incredibly good with networking things, but from just looking around and trying things, it looks like it could be something to do with either the DNS or certificates. That's all the lead I have though and I am at a dead end at the moment. Any help is appreciated.
 


G'day gears, Welcome to Linux.org

Your post is just fine, all the initial info is there.

things to try....

Unplug the router and then turn it back after 30 seconds ?
Try a different browser?

Open terminal and copy and paste in the following....then hit enter

sudo service network-manager restart

Still no luck?

try...

Code: 
resolvectl status

and paste the result back here...that will give details about the uplink dns servers


and, the below...paste the results back here


Code: 
ping 8.8.8.8

Also,

Code: 
ping www.google.com
......the hit enter


All the above is a bit of a fishing expedition, but it should give us some clue
 
Do you visit streaming / priating sites? Some DNS servers block these sites, try changing you DNS
 
Based on your setup description, you are not connected directly to the internet. If anything you should check your router. Your Linux network setting do not change at all obviously.
 
Never use your ISP for DNS service. ISPs love to spy on their users that way. You might try Cloudflare, 1.1.1.1. They have another one, but I don't remember right off hand what it is. Use ip a as root to see if your computer has both IPv4 and IPv6 addresses. I don't mean one starting with fe80:: either. That's a link local address. You will need a public IPv6 address, if you use one at all. Some websites have both IPv4 and IPv6, while others only have IPv4. If you only have an IPv6 address then you will not be able to reach websites that only use IPv4. Make sure your ca-certificates package is up to date if you're worried about certificate problems. I don't use the NetworkManager service because it keeps disconnecting from my wifi. I use the ifupdown package instead. Are you using wifi or ethernet to connect? Please provide more details about that. You might try ip address show dev wlan0 if using wlan0 or ip address show dev eth0 if using eth0. If you are using wifi you could also try iwconfig wlan0 if using wlan0. Substitute wlan1 for wlan0 if needed. If you don't see a wlan0 or eth0 you can rename your default network device names in /etc/network/interfaces if using ifupdown. If you are using an IPv6 address given to you by your previous ISP you will need to request a new one from your new ISP as their network ID will be different. You might also check your /etc/hosts file to see if you have any addresses or hosts that are no longer current. Your kernel will check that first before asking for help from a DNS server.

Signed,

Matthew Campbell
 
Thanks for all the help, I'll try and respond properly to everyone and give the info requested.

Condobloke said:
Open terminal and copy and paste in the following....then hit enter

sudo service network-manager restart
Click to expand...
Code: 
Failed to restart network-manager.service: Unit network-manager.service not found.

Condobloke said:
Code: 
resolvectl status

and paste the result back here...that will give details about the uplink dns servers
Click to expand...
Code: 
Global
       Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (enp42s0)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 8.8.8.8
       DNS Servers: 8.8.8.8 8.8.4.4 192.168.8.1 fe80::805e:4fff:fec2:9bb3%21867

Link 3 (lxcbr0)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 4 (ztjlht77nl)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported


Condobloke said:
Code: 
ping 8.8.8.8
Click to expand...
Code: 
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=46.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=44.2 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=118 time=42.6 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=118 time=50.6 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=118 time=54.0 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=118 time=46.6 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=118 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=118 time=32.6 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=118 time=46.0 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=118 time=60.7 ms
^C
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9015ms
rtt min/avg/max/mdev = 32.587/45.910/60.696/7.878 ms
Condobloke said:
Code: 
ping www.google.com
......the hit enter
Click to expand...
Code: 
PING www.google.com(arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004)) 56 data bytes
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=1 ttl=118 time=36.7 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=2 ttl=118 time=49.4 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=3 ttl=118 time=59.4 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=4 ttl=118 time=47.5 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=5 ttl=118 time=41.5 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=6 ttl=118 time=74.5 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=7 ttl=118 time=40.6 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=8 ttl=118 time=51.7 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=9 ttl=118 time=60.3 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=10 ttl=118 time=53.8 ms
^C
--- www.google.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
rtt min/avg/max/mdev = 36.716/51.542/74.464/10.627 ms
tinfoil-hat said:
Do you visit streaming / priating sites? Some DNS servers block these sites, try changing you DNS
Click to expand...
I don't generally do that, and I haven't recently either. I did try to change my DNS several times with no luck sadly.
Aristarchus said:
Based on your setup description, you are not connected directly to the internet. If anything you should check your router. Your Linux network setting do not change at all obviously.
Click to expand...
I changed back my ISP after noticing that the current one was causing problems, since I have both plans currently ongoing. When I did, everything worked fine again, which then I would assume means the router isn't the problem. We have those SIM-cards that we put into the router to change the ISP btw.

Trenix25 said:
Never use your ISP for DNS service. ISPs love to spy on their users that way. You might try Cloudflare, 1.1.1.1. They have another one, but I don't remember right off hand what it is. Use ip a as root to see if your computer has both IPv4 and IPv6 addresses. I don't mean one starting with fe80:: either. That's a link local address. You will need a public IPv6 address, if you use one at all. Some websites have both IPv4 and IPv6, while others only have IPv4. If you only have an IPv6 address then you will not be able to reach websites that only use IPv4. Make sure your ca-certificates package is up to date if you're worried about certificate problems. I don't use the NetworkManager service because it keeps disconnecting from my wifi. I use the ifupdown package instead. Are you using wifi or ethernet to connect? Please provide more details about that. You might try ip address show dev wlan0 if using wlan0 or ip address show dev eth0 if using eth0. If you are using wifi you could also try iwconfig wlan0 if using wlan0. Substitute wlan1 for wlan0 if needed. If you don't see a wlan0 or eth0 you can rename your default network device names in /etc/network/interfaces if using ifupdown. If you are using an IPv6 address given to you by your previous ISP you will need to request a new one from your new ISP as their network ID will be different. You might also check your /etc/hosts file to see if you have any addresses or hosts that are no longer current. Your kernel will check that first before asking for help from a DNS server.

Signed,

Matthew Campbell
Click to expand...
Honestly not entirely how all of this works, but I did change my DNS, to both Cloudflare and to Google on multiple occasions hoping it would help it, but sadly not. Not sure what you mean by "Use ip a as root to see if your computer has both IPv4 and IPv6 addresses.", I'll try to see if I can figure that one out. I'm not sure if my ca-certificates packages are up to date, but I have no reason to think otherwise. I am using Ethernet to connect, my PC doesn't have the ability to use Wifi.

Doing "ip address show dev enp42s0" gives this:
Code: 
2: enp42s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 04:7c:16:c8:4e:03 brd ff:ff:ff:ff:ff:ff
    inet 192.168.8.116/24 brd 192.168.8.255 scope global dynamic noprefixroute enp42s0
       valid_lft 85879sec preferred_lft 85879sec
    inet6 2a02:920:1fc6:d0db:825e:4fc2:9bb3:4/128 scope global dynamic noprefixroute
       valid_lft 6681sec preferred_lft 3081sec
    inet6 fd82:5e4f:c29b:b300:6cdc:1ca:496a:dca7/64 scope global temporary dynamic
       valid_lft 7067sec preferred_lft 3467sec
    inet6 fd82:5e4f:c29b:b300:5984:a38:f11e:cf8d/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 7067sec preferred_lft 3467sec
    inet6 2a02:920:1fc6:d0db:1007:173:73aa:372/64 scope global temporary dynamic
       valid_lft 7067sec preferred_lft 3467sec
    inet6 2a02:920:1fc6:d0db:a647:e1cc:f7e9:988f/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 7067sec preferred_lft 3467sec
    inet6 fe80::69d6:6afa:714d:578/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
I did that one because that's the one I'm connected to as far as I know.

I also wasn't given anything from the old ISP for ipv6 or anything, everything from the start to end has been the same, except for the DNS changes I did, and when I decided to reset the ethernet connection settings to see if it helped or not.

Once again thanks for all the help, tell me if I missed anything.
 
In a nutshell, your internet is working.....otherwise those pings would not show as working....for whatever reason it is just not being translated to the browser/various websites.

I am not sufficiently experienced to know why.....but I would suspect the isp....(the new one of course)

Are they approachable?....something to do with the fact that you are running them concurrently..??....maybe ??
 
Condobloke said:
In a nutshell, your internet is working.....otherwise those pings would not show as working....for whatever reason it is just not being translated to the browser/various websites.

I am not sufficiently experienced to know why.....but I would suspect the isp....(the new one of course)

Are they approachable?....something to do with the fact that you are running them concurrently..??....maybe ??
Click to expand...
Honestly not sure, I could contact them I guess, just so strange that it is only a problem on the one PC I have Linux on and nothing else. This is why I finally decided to come here for help, I would have tried dealing with it myself otherwise, however long it would have taken.
 
I forgot to mention something. When I disconnect and reconnect using the ui on the taskbar, I get about a 2 second or so time period where everything works. For example, right now to watch Youtube, I am disconnecting, then reconnecting and then quickly refreshing the video or pressing a link to the video I want to watch, and then it works. Sometimes the video even loads almost forever, meaning I don't need to disconnect->reconnect to have it load constantly. But I always need to do that method for each new video that I try to load.

Thought that might be useful information maybe.
 
Trenix25 said:
Never use your ISP for DNS service. ISPs love to spy on their users that way. You might try Cloudflare, 1.1.1.1. They have another one, but I don't remember right off hand what it is. Use ip a as root to see if your computer has both IPv4 and IPv6 addresses. I don't mean one starting with fe80:: either. That's a link local address. You will need a public IPv6 address, if you use one at all. Some websites have both IPv4 and IPv6, while others only have IPv4. If you only have an IPv6 address then you will not be able to reach websites that only use IPv4. Make sure your ca-certificates package is up to date if you're worried about certificate problems. I don't use the NetworkManager service because it keeps disconnecting from my wifi. I use the ifupdown package instead. Are you using wifi or ethernet to connect? Please provide more details about that. You might try ip address show dev wlan0 if using wlan0 or ip address show dev eth0 if using eth0. If you are using wifi you could also try iwconfig wlan0 if using wlan0. Substitute wlan1 for wlan0 if needed. If you don't see a wlan0 or eth0 you can rename your default network device names in /etc/network/interfaces if using ifupdown. If you are using an IPv6 address given to you by your previous ISP you will need to request a new one from your new ISP as their network ID will be different. You might also check your /etc/hosts file to see if you have any addresses or hosts that are no longer current. Your kernel will check that first before asking for help from a DNS server.

Signed,

Matthew Campbell
Click to expand...
I am not sure why Cloudflare or Google DNS is better than ISP as DNS connections are still logged when using proposed DNS services. Also IPv6 addresd is usually easy to trace as is not changed. There are better options than Cloudflare or Google.

Never connect as root. This is really bad.

To solve router/client question connect linux box to the router with working internet setup for your linux and assign static IP for linux box. Confirm that internet is still working in linux. Now change ISP but keep static IP address for linux and see if linux works with the new ISP (it should).
 
Aristarchus said:
I am not sure why Cloudflare or Google DNS is better than ISP as DNS connections are still logged when using proposed DNS services. Also IPv6 addresd is usually easy to trace as is not changed. There are better options than Cloudflare or Google.

Never connect as root. This is really bad.

To solve router/client question connect linux box to the router with working internet setup for your linux and assign static IP for linux box. Confirm that internet is still working in linux. Now change ISP but keep static IP address for linux and see if linux works with the new ISP (it should).
Click to expand...
I'm not entirely sure how to set it to a static IP, but I'd assume I can do that in the router? In which case I already had done that a while back I think.

Oh and I tried the old ISP again just now, and just like before it works perfectly fine.

If it's some other method do let me know.
 
Gears said:
I'm not entirely sure how to set it to a static IP, but I'd assume I can do that in the router? In which case I already had done that a while back I think.

Oh and I tried the old ISP again just now, and just like before it works perfectly fine.

If it's some other method do let me know.
Click to expand...
Ok, so is IP address assigned on the router corresponding to the one aquired by Linux box? I am asking because based on your description there is some sort of IP conflict.

Assuming that internet on Linux box works only for few seconds then please shut down/disconnect other devices connected to the router and see if network works for Linux.
 
This just popped into my mind: Using the NetworkManager GUI from the panel (after clicking the icon in the panel) you also might want to check if there is a NEW network connection made. If so DELETE the old one and restart your machine.

Yeah I know the DNS part and the fact that a ping would work indeed indicates a DNS issue but the above wouldn't hurt to try anyway.

Strange problem you are having OP.
 
Aristarchus said:
Ok, so is IP address assigned on the router corresponding to the one aquired by Linux box? I am asking because based on your description there is some sort of IP conflict.

Assuming that internet on Linux box works only for few seconds then please shut down/disconnect other devices connected to the router and see if network works for Linux.
Click to expand...
I'll try this tomorrow to see if it works, since the rest of the house will need the internet for the rest of the evening I bet, I did just try to change the IP that my PC was using and it didn't seem to change anything though.

PuppyHome said:
This just popped into my mind: Using the NetworkManager GUI from the panel (after clicking the icon in the panel) you also might want to check if there is a NEW network connection made. If so DELETE the old one and restart your machine.

Yeah I know the DNS part and the fact that a ping would work indeed indicates a DNS issue but the above wouldn't hurt to try anyway.

Strange problem you are having OP.
Click to expand...
In a couple of hours I can hopefully check that one out, but I did remove the connection entirely at one point to see if it helped, and then restarted like you said. Just one of the many random things I tried before asking here.
 
Aristarchus said:
I am not sure why Cloudflare or Google DNS is better than ISP as DNS connections are still logged when using proposed DNS services. Also IPv6 addresd is usually easy to trace as is not changed. There are better options than Cloudflare or Google.

Never connect as root. This is really bad.

To solve router/client question connect linux box to the router with working internet setup for your linux and assign static IP for linux box. Confirm that internet is still working in linux. Now change ISP but keep static IP address for linux and see if linux works with the new ISP (it should).
Click to expand...
I would recommend against using an ISP or Google for DNS service since both will want to keep track of where you go that way. I'm not telling anyone to run their browser as root. Cloudflare is a good DNS provider. Please do chime in with those other DNS options...

Signed,

Matthew Campbell
 
Gears said:
Thanks for all the help, I'll try and respond properly to everyone and give the info requested.


Code: 
Failed to restart network-manager.service: Unit network-manager.service not found.


Code: 
Global
       Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (enp42s0)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 8.8.8.8
       DNS Servers: 8.8.8.8 8.8.4.4 192.168.8.1 fe80::805e:4fff:fec2:9bb3%21867

Link 3 (lxcbr0)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 4 (ztjlht77nl)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported



Code: 
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=46.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=44.2 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=118 time=42.6 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=118 time=50.6 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=118 time=54.0 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=118 time=46.6 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=118 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=118 time=32.6 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=118 time=46.0 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=118 time=60.7 ms
^C
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9015ms
rtt min/avg/max/mdev = 32.587/45.910/60.696/7.878 ms

Code: 
PING www.google.com(arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004)) 56 data bytes
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=1 ttl=118 time=36.7 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=2 ttl=118 time=49.4 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=3 ttl=118 time=59.4 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=4 ttl=118 time=47.5 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=5 ttl=118 time=41.5 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=6 ttl=118 time=74.5 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=7 ttl=118 time=40.6 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=8 ttl=118 time=51.7 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=9 ttl=118 time=60.3 ms
64 bytes from arn09s20-in-x04.1e100.net (2a00:1450:400f:80d::2004): icmp_seq=10 ttl=118 time=53.8 ms
^C
--- www.google.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
rtt min/avg/max/mdev = 36.716/51.542/74.464/10.627 ms

I don't generally do that, and I haven't recently either. I did try to change my DNS several times with no luck sadly.

I changed back my ISP after noticing that the current one was causing problems, since I have both plans currently ongoing. When I did, everything worked fine again, which then I would assume means the router isn't the problem. We have those SIM-cards that we put into the router to change the ISP btw.


Honestly not entirely how all of this works, but I did change my DNS, to both Cloudflare and to Google on multiple occasions hoping it would help it, but sadly not. Not sure what you mean by "Use ip a as root to see if your computer has both IPv4 and IPv6 addresses.", I'll try to see if I can figure that one out. I'm not sure if my ca-certificates packages are up to date, but I have no reason to think otherwise. I am using Ethernet to connect, my PC doesn't have the ability to use Wifi.

Doing "ip address show dev enp42s0" gives this:
Code: 
2: enp42s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 04:7c:16:c8:4e:03 brd ff:ff:ff:ff:ff:ff
    inet 192.168.8.116/24 brd 192.168.8.255 scope global dynamic noprefixroute enp42s0
       valid_lft 85879sec preferred_lft 85879sec
    inet6 2a02:920:1fc6:d0db:825e:4fc2:9bb3:4/128 scope global dynamic noprefixroute
       valid_lft 6681sec preferred_lft 3081sec
    inet6 fd82:5e4f:c29b:b300:6cdc:1ca:496a:dca7/64 scope global temporary dynamic
       valid_lft 7067sec preferred_lft 3467sec
    inet6 fd82:5e4f:c29b:b300:5984:a38:f11e:cf8d/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 7067sec preferred_lft 3467sec
    inet6 2a02:920:1fc6:d0db:1007:173:73aa:372/64 scope global temporary dynamic
       valid_lft 7067sec preferred_lft 3467sec
    inet6 2a02:920:1fc6:d0db:a647:e1cc:f7e9:988f/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 7067sec preferred_lft 3467sec
    inet6 fe80::69d6:6afa:714d:578/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
I did that one because that's the one I'm connected to as far as I know.

I also wasn't given anything from the old ISP for ipv6 or anything, everything from the start to end has been the same, except for the DNS changes I did, and when I decided to reset the ethernet connection settings to see if it helped or not.

Once again thanks for all the help, tell me if I missed anything.
Click to expand...
It looks like you have quite a few IPv6 addresses associated with your ethernet device. You really only need one. You can set this up in /etc/network/interfaces. Your computer will have a nice man page that gives detailed information about this. Use man 5 interfaces to access it. That ip a means to run /usr/sbin/ip address as root. It is root's job to perform setup and maintenance. You'll need to open a terminal as root and run it, though it looks like you already did. The # is the command prompt that your command shell provides.

Signed,

Matthew Campbell
 
Quad9 no logging, Mullvad no logging, there is quite a few . Obviously assumption is that DOT/DOH are disabled otherwise these options defies any reason of configuring specific DNS (unless specified custom DNS, not default).

OP: Try to ping sites that your Linux fail to connect.
This:
DNS Servers: 8.8.8.8 8.8.4.4 192.168.8.1 fe80::805e:4fff:fec2:9bb3%21867
192.168.8.1 as DNS server?
 
Last edited:
Probably that is because the router is configured to provide itself as a DNS Server through DHCP, and in turn has its own configured DNS Servers.
 
You must log in or register to reply here.

Members online

Total: 569 (members: 8, guests: 561)

Latest posts

Top