Bugzilla – Bug 1201425
This device appears to be connected to a network but is unable to reach the internet.
Last modified: 2022-07-18 08:09:32 UTC
Whenever I start my computer I get "This device appears to be connected to a network but is unable to reach the internet", even though the internet is working without issues. It happens on all Linux based computers I use. I also have a PiHole configured as the default DNS server, but I temporary disabled and the result is the same. nslookup looks good, ping works, curl works... (tests were performed also on conncheck.opensuse.org)
Does ping -6 conncheck.opensuse.org work? If not, does it work after sudo rcnetwork restart?
No, for both questions: ping -6 conncheck.opensuse.org ping: connect: Network is unreachable user@host:~> sudo rcnetwork restart [sudo] password for root: user@host:~> ping -6 conncheck.opensuse.org ping: connect: Network is unreachable
(In reply to Cosmin Tanczel from comment #2) > No, for both questions: > > ping -6 conncheck.opensuse.org > ping: connect: Network is unreachable > user@host:~> sudo rcnetwork restart > [sudo] password for root: > user@host:~> ping -6 conncheck.opensuse.org > ping: connect: Network is unreachable Sorry, I meant whether the warning disappeared after rcnetwork restart.
Well, when I first connect the message appears for about 15 seconds and then it disappears. So it's not like it stays there forever. But indeed, when I do a rcnetwork restart, the message does not appear anymore
(In reply to Cosmin Tanczel from comment #4) > Well, when I first connect the message appears for about 15 seconds and then > it disappears. So it's not like it stays there forever. Ok, you didn't write that in the initial description. > But indeed, when I do a rcnetwork restart, the message does not appear > anymore Ok, so definitely an issue in NetworkManager. Reassigning.
Seems to be an duplicate of bug#1199964.
(In reply to Jonathan Kang from comment #6) > Seems to be an duplicate of bug#1199964. *** This bug has been marked as a duplicate of bug 1199964 ***