After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 748151 - Network connection established, but unable to access any Internet services.
Network connection established, but unable to access any Internet services.
Status: RESOLVED INCOMPLETE
Product: NetworkManager
Classification: Platform
Component: IP and DNS config
0.9.x
Other Linux
: Normal critical
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-04-19 19:50 UTC by Jan Henke
Modified: 2016-04-22 13:41 UTC
See Also:
GNOME target: ---
GNOME version: 3.13/3.14



Description Jan Henke 2015-04-19 19:50:22 UTC
This bug has been reported in Launchpad: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1434986

As requested there, I file this bug here as well.

The symptoms are an established network connection with correctly assigned IP address, but failure to access any Internet services.

My guess is a failure to resolve a host name, which waits forever to complete. This bug has been confirmed by at least one other user on Launchpad.
Comment 1 yan 2016-04-21 18:24:25 UTC
I'm having a similar issue, but I'm not sure if it's the same:
https://bugs.kde.org/show_bug.cgi?id=361655
Comment 2 Thomas Haller 2016-04-22 13:41:31 UTC
Sorry that this bug didn't get any attention now for one year.



It's not at all clear, what the issue here is.

NetworkManager is only configuring your system, so, if you have no connectivity/DNS, it is either due to a user-misconfiguration, a bug in NetworkManager, or an issue in your network.



Assuming it is failure to configure DNS...

what is the content of /etc/resolv.conf? Can you resolve any names, for example can you `ping www.google.com`?


Please always attach a logfile of NetworkManager with debug logging enabled.

Also show the output of

   nmcli connection
   nmcli device

and possibly show the connection that you want to use:

   nmcli connection show $CONNECTION_ID



I am closing this bug, because it is for a very old version. Please reopen if you still have the problem and can provide the required information.


Thank you.


@yan, it seems you are using a recent version. It is not likely that your issue is the same as the one from the original reporter. Please open a new bug and provide the required information. Thank you.