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

[Gears]

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.

I tried this now and it did not fix or change anything sadly.

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.

And tried this as well, nothing different.

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

Ran "ip a" and this came up fyi:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
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.120/24 brd 192.168.8.255 scope global dynamic noprefixroute enp42s0
       valid_lft 85511sec preferred_lft 85511sec
    inet6 2a02:920:1fca:8db8:825e:4fc2:9bb3:3/128 scope global dynamic noprefixroute
       valid_lft 6313sec preferred_lft 2713sec
    inet6 fd82:5e4f:c29b:b300:bfbf:e59f:692e:a530/64 scope global temporary dynamic
       valid_lft 6967sec preferred_lft 3367sec
    inet6 fd82:5e4f:c29b:b300:5984:a38:f11e:cf8d/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 6967sec preferred_lft 3367sec
    inet6 2a02:920:1fca:8db8:4f83:a024:376c:23ce/64 scope global temporary dynamic
       valid_lft 6967sec preferred_lft 3367sec
    inet6 2a02:920:1fca:8db8:8c31:5416:5074:d7c7/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 6967sec preferred_lft 3367sec
    inet6 fe80::69d6:6afa:714d:578/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: lxcbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet 10.0.3.1/24 brd 10.0.3.255 scope global lxcbr0
       valid_lft forever preferred_lft forever
4: ztjlht77nl: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2800 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether be:50:af:d3:d0:6b brd ff:ff:ff:ff:ff:ff
    inet 192.168.196.12/24 brd 192.168.196.255 scope global ztjlht77nl
       valid_lft forever preferred_lft forever
    inet6 fe80::bc50:afff:fed3:d06b/64 scope link
       valid_lft forever preferred_lft forever

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?

I can ping Google and get back easily, it just doesn't load properly when I try to access it through any browser. It almost seems like it loads part way through and then stops at a certain point, just infinitely loading.

PING google.com(arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e)) 56 data bytes
64 bytes from arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e): icmp_seq=1 ttl=118 time=41.2 ms
64 bytes from arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e): icmp_seq=2 ttl=118 time=45.5 ms
64 bytes from arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e): icmp_seq=3 ttl=118 time=38.5 ms
64 bytes from arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e): icmp_seq=4 ttl=118 time=44.3 ms
64 bytes from arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e): icmp_seq=5 ttl=118 time=46.4 ms
64 bytes from arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e): icmp_seq=6 ttl=118 time=51.8 ms
64 bytes from arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e): icmp_seq=7 ttl=118 time=42.7 ms
64 bytes from arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e): icmp_seq=8 ttl=118 time=36.8 ms
64 bytes from arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e): icmp_seq=9 ttl=118 time=38.7 ms
64 bytes from arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e): icmp_seq=10 ttl=118 time=52.5 ms
^C
--- google.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 36.751/43.834/52.510/5.116 ms

Additional information I discovered recently by the way, it seems I can't open ports on the network even when it's configured on the router.

I have contacted my ISP and they haven't answered yet, I will come back with what they say when they do.

 

[gvisoc]

@Aristarchus -- It depends on how the network and the subnet is configured. The convention that makes an IP address the Gateway's for a given network is the .1, as in the first IP address for that network.

Mine has always been 192.168.0.1. If their subnetwork is 192.168.8.0, then the gateway would be the .1

 

[MzQ1NjExN2]

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.

Hey I had a similar issue earlier this month. Certain websites would only partially load up and some would work 50% of the time after taking a long time to load. One of the websites that was loading partially was youtube. I had just started to use ProtonVPN and was using it with UDP but after changing it to TCP everything worked. I know your not using VPN but I thought I would share this in case it helps you.

I'm not a network guy either but my understanding after some brief reading on UDP and TCP is that UDP is faster but a bit loose with data transfer (probably why things were not loading up properly) and TCP is slower but more secure and thorough.

I can ping Google and get back easily, it just doesn't load properly when I try to access it through any browser. It almost seems like it loads part way through and then stops at a certain point, just infinitely loading.

This was the same symptom I was having. Changing my VPN connection to TCP fixed it instantly.

 

[MzQ1NjExN2]

"What does a DNS issue look like?​

If your DNS fails entirely then it's likely you'll see timeouts, DNS or other errors with all your internet apps. It might look like your entire internet is dead.

Other DNS failures are partial, though, affecting some websites only. Maybe you'll access sites a, b and c as usual, but x, y and z all seem to be down.

Partial failures can also cause odd-looking page loading issues. What if DNS allows you to access bigsite.com, but not the domain where it hosts its images, scripts or contact forms?

You might see image placeholders, empty spaces where content used to be, or buttons and other site features not working as they should. It's this mix of problems across multiple sites that's one of the tell-tale signs of a DNS problem."

"How to fix DNS problems​

If it looks like your ISP's DNS isn't working, the quickest and most effective solution is to switch to a free public DNS server. Google and Cloudflare offer fast and reliable services which anyone can use, no registration required.

Changing DNS servers normally involves tweaking your device network settings. The Cloudflare support site has guides on setting up Cloudflare DNS for Windows, Mac, Android, iOS, routers, gaming consoles, Linux and more. These are sometimes very basic ('install app X to do it for you'), but Google's equivalent page has more detailed advice if you need it.

Whatever changes you make, be sure to note down your original settings first, just in case you need to switch them back later.

Reboot your device when you're done, and it should now be using your (hopefully) problem-free new DNS server.

If you still have internet connectivity problems, though, it's time to ask your ISPs support team for help. Tell them what you've tried, and that should help them diagnose the issue and get your connection running smoothly again."

From:

How to diagnose and fix DNS problems

Dead websites, page loading issues, web not working as it should? Here's what to do next.

www.techradar.com

Also maybe a quick fix might be to change the dns server through your web browser. For firefox:

"Firefox (desktop version)

Click on the menu button in the top right corner and select Settings.
Click on Privacy & Security in the left column.
Scroll down to the bottom.
Under Enable secure DNS using select Max Protection.
Under Choose provider click on the drop down list and select Custom.
In the text field that appears, paste one of the following, then press Enter on your keyboard to set it.
https://dns.mullvad.net/dns-query
https://adblock.dns.mullvad.net/dns-query
https://base.dns.mullvad.net/dns-query
https://extended.dns.mullvad.net/dns-query
https://family.dns.mullvad.net/dns-query
https://all.dns.mullvad.net/dns-query"

From:

DNS over HTTPS and DNS over TLS

Our public DNS service

mullvad.net

And to test:

Connection check | Mullvad VPN

Check your privacy and security with Mullvad's tool. Verify your VPN, check for DNS and WebRTC leaks, and ensure your connection is secure.

mullvad.net

 

[Aristarchus]

@Aristarchus -- It depends on how the network and the subnet is configured. The convention that makes an IP address the Gateway's for a given network is the .1, as in the first IP address for that network.

Mine has always been 192.168.0.1. If their subnetwork is 192.168.8.0, then the gateway would be the .1

yes, of course. My point was that if DNS IP is set manually and some client has the same IP, then obviously web will not work.

This is pretty strange issue as name resolution works from command line. I would create a new browser profile and try again. This may be browser issue, DNS filtering some sites and so on

 

[Gears]

Hey I had a similar issue earlier this month. Certain websites would only partially load up and some would work 50% of the time after taking a long time to load. One of the websites that was loading partially was youtube. I had just started to use ProtonVPN and was using it with UDP but after changing it to TCP everything worked. I know your not using VPN but I thought I would share this in case it helps you.

I'm not a network guy either but my understanding after some brief reading on UDP and TCP is that UDP is faster but a bit loose with data transfer (probably why things were not loading up properly) and TCP is slower but more secure and thorough.


This was the same symptom I was having. Changing my VPN connection to TCP fixed it instantly.

"What does a DNS issue look like?​

If your DNS fails entirely then it's likely you'll see timeouts, DNS or other errors with all your internet apps. It might look like your entire internet is dead.

Other DNS failures are partial, though, affecting some websites only. Maybe you'll access sites a, b and c as usual, but x, y and z all seem to be down.

Partial failures can also cause odd-looking page loading issues. What if DNS allows you to access bigsite.com, but not the domain where it hosts its images, scripts or contact forms?

You might see image placeholders, empty spaces where content used to be, or buttons and other site features not working as they should. It's this mix of problems across multiple sites that's one of the tell-tale signs of a DNS problem."

"How to fix DNS problems​

If it looks like your ISP's DNS isn't working, the quickest and most effective solution is to switch to a free public DNS server. Google and Cloudflare offer fast and reliable services which anyone can use, no registration required.

Changing DNS servers normally involves tweaking your device network settings. The Cloudflare support site has guides on setting up Cloudflare DNS for Windows, Mac, Android, iOS, routers, gaming consoles, Linux and more. These are sometimes very basic ('install app X to do it for you'), but Google's equivalent page has more detailed advice if you need it.

Whatever changes you make, be sure to note down your original settings first, just in case you need to switch them back later.

Reboot your device when you're done, and it should now be using your (hopefully) problem-free new DNS server.

If you still have internet connectivity problems, though, it's time to ask your ISPs support team for help. Tell them what you've tried, and that should help them diagnose the issue and get your connection running smoothly again."

From:

How to diagnose and fix DNS problems

Dead websites, page loading issues, web not working as it should? Here's what to do next.

www.techradar.com

Also maybe a quick fix might be to change the dns server through your web browser. For firefox:

"Firefox (desktop version)

Click on the menu button in the top right corner and select Settings.
Click on Privacy & Security in the left column.
Scroll down to the bottom.
Under Enable secure DNS using select Max Protection.
Under Choose provider click on the drop down list and select Custom.
In the text field that appears, paste one of the following, then press Enter on your keyboard to set it.
https://dns.mullvad.net/dns-query
https://adblock.dns.mullvad.net/dns-query
https://base.dns.mullvad.net/dns-query
https://extended.dns.mullvad.net/dns-query
https://family.dns.mullvad.net/dns-query
https://all.dns.mullvad.net/dns-query"

From:

DNS over HTTPS and DNS over TLS

Our public DNS service

mullvad.net

And to test:

Connection check | Mullvad VPN

Check your privacy and security with Mullvad's tool. Verify your VPN, check for DNS and WebRTC leaks, and ensure your connection is secure.

mullvad.net

I'm happy I'm not the only one with the issue, had been looking around for ages seemingly being the only one with it. I did try the DNS you provided and unfortunately it didn't seem to change anything. I am heavily suspecting it is simply just on the ISP's side and I'll have to contact them today once I have gotten the information they requested.

I'll update once I have gotten everything sorted with the ISP. Thanks for all the help so far, it's been very insightful.

 

[Gears]

So update on the issue, the ISP wasn't very helpful, stating that they couldn't fix issues related to individual machines connected to their network. So as a final resort I decided to use a VPN, which has fixed my issues. This however makes it so I can only access my routers admin page if I turn the VPN off, which is a fine compromise. It also seems like I can't use port forwarding either, so I'll have to find a workaround for that.

Thanks for all the help people, I'll just have to accept this as a solution for now.

 

[f33dm3bits]

This however makes it so I can only access my routers admin page if I turn the VPN off, which is a fine compromise. It also seems like I can't use port forwarding either, so I'll have to find a workaround for that.

Most vpn apps have a feature called "local network sharing", it is described like this for my vpn app.

This feature allows access to other devices on the local network, such as for sharing, printing, streaming etc. It does this by allowing network communication outside of the tunnel to local multicast and broadcast ranges as well as to and from these private ranges.

That should allow you to access that admin page of your router as well, because I can access my router's admin page with my vpn turned on, I'm using Mullvad. Look if your vpn provider's app has that feature as well or a similar feature.

 

[Gears]

Most vpn apps have a feature called "local network sharing", it is described like this for my vpn app.

That should allow you to access that admin page of your router as well, because I can access my router's admin page with my vpn turned on, I'm using Mullvad. Look if your vpn provider's app has that feature as well or a similar feature.

Yeah found it, thanks for the info. Now all that's left is port forwarding or anything similar really, I'll keep working on it, I'll add it here for anyones interest if I do find a fix for at least NordVPN.

 

[Terminal Velocity]

ISPs log the sites you visit even if you don't use their DNS. Also if you use DNS over HTTPS they log the IPs that you visit and they can find the sites with reverse IP lookup