[Solved]No network access after latest update- Fedora

Everything seems fine, but I have no network access 😅 happened after I restarted for a System update. Can't figure out what is wrong - help please 😊 Wired connection.

Enabled Wifi, but same problem; connect but cannot reach gateway. (other computers and pads are connected, and they work fine).

16 points · 7 comments · view on lemmy.world

7 Comments

oyzmo@lemmy.world · 13 pts · 1y

Solved! Latest Mullvad VPN update caused it. Removed Mullvad VPN (was not loaded and not enabled), and everything is back to normal.

Thanks for suggestions though :)

wildbus8979@sh.itjust.works · 2 pts · 1y

Can you show us the ip route show ?

ogeist@lemmy.world · 1 pts · 1y (3 replies)

Check this solved issue: https://forums.linuxmint.com/viewtopic.php?t=402315

Given the symptoms I suspect some bad IP6 config, thus the link.

Also try "ping 8.8.8.8", you are testing locally.

sxan@midwest.social · 3 pts · 1y (2 replies)

I want to use IPv6 so badly, but every time I try I'm thwarted, have occasionally lost network connection as a result, and frequently just get a really unreliable connection.

At first, in our last house, I tracked it down to the network provider (Verizon, a decade ago). This time, I don't know what it is; theoretically Comcast supports it, as does Mullvad, and OpenWRT certainly does, so I have no idea where the issue is. But a couple of months ago I did a system upgrade and v6 got re-enabled in sysconfig and I lost internet, and it took me forever to track it down.

At this point, I'm starting to believe there's a conspiracy keeping IPv6 from succeeding (in becoming common), because when I read stuff like this I realize it's not just my curse.

ogeist@lemmy.world · 2 pts · 1y (1 reply)

Don't sweat it, it will come eventually.

sxan@midwest.social · 2 pts · 1y

I've been heating that got, like, 15 years.

jrredho@mastodon.world · 1 pts · 1y

@oyzmo

It's not this issue, is it? https://discussion.fedoraproject.org/t/lenovo-t14s-amd-gen-6-wi-fi-not-working-after-the-latest-update-f42/153486

If so, as you can see, it's a known problem, and there's a temporary workaround.

Good luck!