|
Bugzilla – Full Text Bug Listing |
| Summary: | This device appears to be connected to a network but is unable to reach the internet. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Cosmin Tanczel <cosmin.tanczel> |
| Component: | Network | Assignee: | Jonathan Kang <songchuan.kang> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | cosmin.tanczel, fabian, fvogt |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | Community User | Services Priority: | |
| Business Priority: | Blocker: | No | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Cosmin Tanczel
2022-07-12 14:57:41 UTC
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 *** |