Do you think it can be related?

It is shown as connected, but when I ping google.com I get temporary failure in name resolution.

Howevern pinging localhost and 8.8.8.8 works

I think I found the issue. Arch Linux use the AMD GPU as default instead the NVIDIA GPU which works fine. I’m currently trying to switch the default GPU which was Nvidia card before system upgrade.

I changed the nameserver in /etc/resolv.conf from ::1 to 1.1.1.1 and now pinging websites just hangs indefinitely

No, still same error after some time

Does 8.8.8.8 work still?

Yes, and 1.1.1.1

If nothing on the Arch system changed (i.e. package updates) then it’s not an issue with the Arch installation. Perhaps your carrier has detected and blocked your tethering?

The WiFi doesn’t work either, I used tethering just to check after

WiFi and mobile internet (that I use via tethering) are different ISPs

I can’t remember really. I did not upgrade the system

Well, WiFi works on my phone, but I’m gonna check the WiFi admin console

What sort of “doesn’t work” are you talking about here?

Same. Pings 8.8.8.8 but returns failure in name resolution for domain names

It was nameserver ::1 initially, I changed it to 8.8.8.8, 1.1.1.1 and now bakc to initial

Please provide the actual contents so we can check for syntax errors

sarmong 2022-09-27 21:11:10

Oh, you have some VPN anti-leak interface thing. That’ll be what’s causing problems, probably because you’re not connected to the VPN, so it’s actually doing the job it’s supposed to be doing.

jonathn 2022-09-27 21:11:52

Oh, you have some VPN anti-leak interface thing. That’ll be what’s causing problems, probably because you’re not connected to the VPN, so it’s actually doing the job it’s supposed to be doing.

Hm, for work I need to have falcon antivirus (which seems to not be doing anything) and globalprotect VPN. I have been safely turning those on and off for months

jonathn 2022-09-27 21:11:52

Oh, you have some VPN anti-leak interface thing. That’ll be what’s causing problems, probably because you’re not connected to the VPN, so it’s actually doing the job it’s supposed to be doing.

Do you think it can be related? I can’t even turn on the VPN now.
Is there a way to fix it?

jonathn 2022-09-27 21:21:24

Yes, I mentioned it because I think that anti-leak interface is the reason things are broken. I don’t know how you have configured your system so you’ll need to look into that.

I basically didn’t do anything, I don’t even know what the anti-leak interface is. All I did was installing falcon, which runs as a systemd service and a globalprotect

sarmong 2022-09-27 21:22:30

I basically didn’t do anything, I don’t even know what the anti-leak interface is. All I did was installing falcon, which runs as a systemd service and a globalprotect

I suspect you installed something like ProtonVPN and enabled its killswitch.

https://forums.linuxmint.com/viewtopic.php?p=2100913#p2100913

But, if you’re absolutely certain you haven’t done anything like that then I’m at a loss. 😜

Unless, of course, GlobalProtect has this feature…. you’d be better placed to know the answer to that.

jonathn 2022-09-27 21:27:18

I suspect you installed something like ProtonVPN and enabled its killswitch.

https://forums.linuxmint.com/viewtopic.php?p=2100913#p2100913

But, if you’re absolutely certain you haven’t done anything like that then I’m at a loss. 😜

Unless, of course, GlobalProtect has this feature…. you’d be better placed to know the answer to that.

Thank you! It helped I had protonvpn installed and indeed used it today. Couldn’t even think it was the case

jonathn 2022-09-27 21:32:06

So, nothing changed, except installing another piece of VPN software… 😂

I think I used it before without any issues, weird

Cartoon_Dude 2022-09-27 21:38:34

Hmm, a problem with the packages?
:: Import PGP key 493DE21C824E9541, “Chih-Hsuan Yen <yan12125@archlinux.org>”? [Y/n] y
error: key “493DE21C824E9541” could not be looked up remotely
error: required key missing from keyring

Update the pacman keyring.