[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Try this simple fix: https://www.youtube.com/watch?v=wjS4eBnR3q0=PL4fAeCL2jtycl0gPZD8WFPn9caOPidMqs=2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title: No Internet access with default

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Latest update has infact fixed the issue for me! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title: No Internet access with default of Automatic (DHCP) To manage notifications about

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Lubuntu 17.04 is giving me this bug on an Asus EEE 1005HAB netbook, im installing the latest update at the moment, which may fix it. But before the update i could not connect to the internet, we will see if the update fixes it -- You received this bug notification because you are a member of

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

I updated my Ubuntu from 16.10 to 17.04 and the network work as expected. But then I made a fresh install of both systems (Ubuntu 17.04 and Ubuntu Gnome 17.04) and I couldn't connect to the wifi anymore. However the solution that Doug McMahon on the comment #14 works for me. Thanks for the fix.

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

This is fixed with updated systemd package so marking as such. The install image is broken but I guess 4+ months wasn't enough time to get it together... ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux Status: New => Invalid **

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

I'm sorry @hrvooje - it worked for me. But I have now risked upgrading my main laptop from 16.10 to 17.04 and it appears to be working perfectly without the necessity for tweaks or workaronds or alternative of 8.8.8.8 , etc, etc. I guess the latest in-situ upgrade contained its own bugfix. David

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

@David I did what you told and it happend to me again. However, my message from sudo systemd-resolved returned REFUSED error with that domain I tried to open. My systemd is 232-21ubuntu3 and when IP address is set to automatic it why it didn't try different one when first refused? Poettering

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

OK - complete solution/workaround is to be found here... But you must read the whole lot before doing anything at all because the last edit makes the first part redundant... http://www.hecticgeek.com/2017/04/ubuntu-17-04-systemd-dns-issues/ The issue involves systemd within which the developers

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

For me: work-wire OK work-wifi OK home-wifi FAIL I don't use a wire at home so I didn't try Then I do sudo service network-manager restart and I can surf again. In that time while I can't sufr the internet I get ping 8.8.8.8 and other IP's. Torrent dowloading is also working in that time. So,

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

For me: work-wire OK work-wifi OK home-wifi FAIL I don't use a wire at home so I didn't try Then I do sudo service network-manager restart and I can surf again. In that time while I can't sufr the internet I get ping 8.8.8.8 and other IP's. Torrent dowloading is also working in that time. So,

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Temporary workaround which seems to work most of the time (though, 'timing' - as you are suggesting - sometimes is an issue, requiring a couple of 'sudo apt update' attempts in Terminal to successfully resolve all repositories) enter 8.8.8.8 (Google's DNS) into the relevant 'alternate DNS' in

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Regarding my previous post (#24)... Seems that everything is back to abnormal. After logging out and re- logging again bug was back. This time soft disconnecting and reconnecting network (from NManager) helped to regain access to network, but this was not always the remedy. -- You received

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Ubuntu 17.04 on a Dell E6530, fresh install with copying of some networkmanager setup in /etc/ from good old Ubuntu 16.04.01 LTS and using the same home partition. My version of this bug is really miraculous. It was here for a week, today disappeared. For a week I had problems with ONE of the

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Same thing on an upgrade from 16.04 to 17.04. Some internet immediately after the upgrade, same issue as noted above with software updates needing multiple tries to access the repos, currently internet completely dead even with a reboot. Note this was a Software Updater suggested dist upgrade - I

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

All day at work no problems. Neither WiFi or ethernet. At home after a while can't load a website. After restarting service network-manager it works again. It is interesting that in that time torrents download/upload worked and I could ping 8.8.8.8 and other IPs on the Internet. Just couldn't load

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

On second thoughts, despite 'dnsutils' and 'bind9-host' updates 17.04 is still buggy on my two Toshiba laptops (one ancient, one less so). Can take up to three attempts to resolve all repositories with 'sudo apt update' after boot. Alternatively, on first attempts, browsers (Firefox, Chromium) do

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Fortunately I had retained 17.04 full installation on a USB stick. Downloaded new update via Google DNS on IPV4, then deleted 8.8.8.8 and tested. Seems to be working. So far so good Thanks for the heads-up hrvooje! Best David On 18 April 2017 at 07:09, hrvooje <1654...@bugs.launchpad.net>

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

This morning I got dnsutils and bind9-host updates. Could this be the fix? So far so good, no disconecting last hour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title: No Internet access

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Yup... Me, I'm reverting back to 16.10 D On 17 Apr 2017 15:51, "harry brijs" wrote: > i installed from iso file > internet is avail upon goodwill of the system > or whatever. > It comes but most of the time it does not stay. > I did not yet correlate this behaviour > 2 > > --

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

i installed from iso file internet is avail upon goodwill of the system or whatever. It comes but most of the time it does not stay. I did not yet correlate this behaviour 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Actually there seem to be two related or unrelated issues. One seems to be purely DNS and the other Network Manager... Dunno. My original issue was Network Manager. Now ok for no reason i can see. The more sticky one with my latest upgrade was no problem linking to my WiFi but no internet when

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Noting that above suggestion probably doesn't help ethernet.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title: No Internet access with default of Automatic (DHCP) To manage

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Another 'fix' suggested is to Open /etc/NetworkManager/NetworkManager.conf add lines [device] wifi.scan-rand-mac-address=no then sudo service network-manager restart I'm fine with just changing the nameservers as previously mentoned, in any event users shouldn't have to do anything. (even with

Re: [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Regret to inform that an upgrade from 16.04 is also displaying the bug. Reduced to using Google DNS on ipv4 (8.8.8.8) in order to work around it David On 14 Apr 2017 14:11, "David Oser" <1654...@bugs.launchpad.net> wrote: I'm also experiencing this exact bug. Upgrading from 16.10 to 17.04 did

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

How can this be unassigned? So important thing like internet connection and bug is from January? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title: No Internet access with default of

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

I'm also experiencing this exact bug. Upgrading from 16.10 to 17.04 did not display the problem, but fresh install of Ubuntu 17.04 does -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title:

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

It could also be because of DNSsec. I have seen HTTP working, though HTTPS failing. When adding the Google nameservers before the default (127.0.0.53, systemd-resolver) everything works as expected. $ systemd-resolve --status Global DNS Servers: 8.8.8.8 DNSSEC NTA:

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

While much better the 4.11 kernel is reported fail occasionally in this regard. This is in contrast to current kernel in 17.04 (4.10.x) where this happens all the time either right away or after the first reboot or so.. ** Summary changed: - No Internet access with default of Automatic (DHCP) &

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP) & current kernel

also seen in Ubuntu-Gnome install ** Also affects: network-manager Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title: No Internet access with

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Adding linux as also seems resolved using the latest kernel, tested with 4.11.0-041100rc4-generic #201703261831 from mainline ** Also affects: linux Importance: Undecided Status: New ** Summary changed: - No Internet access with default of Automatic (DHCP) + No Internet access with

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

The best fix here for Both wireless & ethernet is to set to google nameservers as in attached screen ** Description changed: Fresh 17.04 install, wireless router connects without any issue but there is no internet connection/access. This continues thru disconnecting, reconnecting, rebooting

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654918

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

I can confirm this bug on ubuntu 17.04 armhf. It seems dhcp client doesn't acquire dns adresses when first time connected. Running dhclient cmd workarounds issue to next reboot. /etc/resolv.conf contains in my case: # Generated by NetworkManager nameserver 127.0.1.1 and after dhclient cmd

[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

Thank you for your bug report, so that's a DNS issue? Do you have libnss-resolve installed? That might have to do with the changes from https://blueprints.launchpad.net/ubuntu/+spec/foundations-y-local- resolver ** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You