[opensuse-factory] Network stopped working after update to Tumbleweed 20170630
![](https://seccdn.libravatar.org/avatar/e1300a36fc6d73d1c31496875817b5f2.jpg?s=120&d=mm&r=g)
Hi there After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written properly by NetworkManager, not even when I reboot. Manually editing /etc/resolv.conf resolved the issue. Regards, Frank -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/dcb1c404b097820117b962bea29922ce.jpg?s=120&d=mm&r=g)
Am 02.07.2017 um 09:51 schrieb Frank Krüger:
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written properly by NetworkManager, not even when I reboot.
Manually editing /etc/resolv.conf resolved the issue.
Regards, Frank
Hi, the same here. The ipv4 name server entry is missing, but the ipv6 name server entry is still written. regards, Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/1cf33eb312eb37b5b5f06364b8dd3d25.jpg?s=120&d=mm&r=g)
Same here, had to configure static IP+address instead of using DHCP.
On 2 July 2017 10:22:02 CEST, Hendrik Woltersdorf
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written
Am 02.07.2017 um 09:51 schrieb Frank Krüger: properly
by NetworkManager, not even when I reboot.
Manually editing /etc/resolv.conf resolved the issue.
Regards, Frank
Hi,
the same here. The ipv4 name server entry is missing, but the ipv6 name server entry is still written.
regards, Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/594ac7e94ed96c0f5b5f3092bea1b204.jpg?s=120&d=mm&r=g)
неділя, 2 липня 2017 р. 11:51:03 EEST Mari Donkers написано:
Same here, had to configure static IP+address instead of using DHCP.
On 2 July 2017 10:22:02 CEST, Hendrik Woltersdorf
wrote: Am 02.07.2017 um 09:51 schrieb Frank Krüger:
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written
properly
by NetworkManager, not even when I reboot.
Manually editing /etc/resolv.conf resolved the issue.
Regards, Frank
Hi,
the same here. The ipv4 name server entry is missing, but the ipv6 name server entry is still written.
regards, Hendrik
There is no need to configure fully static address, setting additional DNS works fine. But anyway that's a workaround and not a fix. -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський
![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
02.07.2017 10:51, Frank Krüger пишет:
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written properly by NetworkManager, not even when I reboot.
Works here.
Manually editing /etc/resolv.conf resolved the issue.
And likely prevented further automatic updates. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/4d3c266297efe1ff677db52775d8f902.jpg?s=120&d=mm&r=g)
On Sunday, 2 July 2017 08:51:34 BST Frank Krüger wrote:
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written properly by NetworkManager, not even when I reboot.
Manually editing /etc/resolv.conf resolved the issue.
Regards, Frank
I had the same issue with previous update. resolv.conf file was not updated. I had to manually insert the entries. After a couple of reboots, the problem resolved itself. Had no issues after the last update. Regards. -- Sudhir Anand -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/4d3c266297efe1ff677db52775d8f902.jpg?s=120&d=mm&r=g)
On Sunday, 2 July 2017 10:28:35 BST Sudhir Anand wrote:
On Sunday, 2 July 2017 08:51:34 BST Frank Krüger wrote:
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written properly by NetworkManager, not even when I reboot.
Manually editing /etc/resolv.conf resolved the issue.
Regards, Frank
I had the same issue with previous update. resolv.conf file was not updated. I had to manually insert the entries. After a couple of reboots, the problem resolved itself.
Had no issues after the last update.
Regards.
Just as a follow up to my previous email, I had a lot of connectivity issues with Network manager with both KDE and Mate. I have switched to Wicked mode and connectivity is better but erratic at times. Up until 13.1, network connectivity was seamless and since then it has been erratic and requires a lot more attention. Without starting a flame war, Opensuse since 13.1 has not been as reliable as far as networks is concerned in my opinion. -- Sudhir Anand -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/022a482927e713146ced675bb5399746.jpg?s=120&d=mm&r=g)
Sudhir Anand wrote:
On Sunday, 2 July 2017 08:51:34 BST Frank Krüger wrote:
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written properly by NetworkManager, not even when I reboot.
Manually editing /etc/resolv.conf resolved the issue.
Regards, Frank
I had the same issue with previous update. resolv.conf file was not updated. I had to manually insert the entries. After a couple of reboots, the problem resolved itself.
This happens every now and then and can be most times fixed by this command (as root): netconfig update -f Ciao, Michael.
![](https://seccdn.libravatar.org/avatar/594ac7e94ed96c0f5b5f3092bea1b204.jpg?s=120&d=mm&r=g)
неділя, 2 липня 2017 р. 13:00:12 EEST Michael Ströder написано:
Sudhir Anand wrote:
On Sunday, 2 July 2017 08:51:34 BST Frank Krüger wrote:
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written properly by NetworkManager, not even when I reboot.
Manually editing /etc/resolv.conf resolved the issue.
Regards, Frank
I had the same issue with previous update. resolv.conf file was not updated. I had to manually insert the entries. After a couple of reboots, the problem resolved itself.
This happens every now and then and can be most times fixed by this command (as root):
netconfig update -f
Ciao, Michael.
Doesn't help for me. /etc/resolv.conf still has no nameserver unless I'm adding additional DNS to NM config. It looks like some NetworkManager problem. -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський
![](https://seccdn.libravatar.org/avatar/ec2e857562f9e94f420a54d9a7ce8d79.jpg?s=120&d=mm&r=g)
Op zondag 2 juli 2017 09:51:34 CEST schreef Frank Krüger:
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written properly by NetworkManager, not even when I reboot.
Manually editing /etc/resolv.conf resolved the issue.
Regards, Frank
Using a static IP address works too. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/ec2e857562f9e94f420a54d9a7ce8d79.jpg?s=120&d=mm&r=g)
Op zondag 2 juli 2017 12:26:56 CEST schreef Knurpht - Gertjan Lettink:
Op zondag 2 juli 2017 09:51:34 CEST schreef Frank Krüger:
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written properly by NetworkManager, not even when I reboot.
Manually editing /etc/resolv.conf resolved the issue.
Regards, Frank
Using a static IP address works too.
Changed back from static IP address to DHCP, connection is made as it should and working. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/dcb1c404b097820117b962bea29922ce.jpg?s=120&d=mm&r=g)
Am 02.07.2017 um 09:51 schrieb Frank Krüger:
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written properly by NetworkManager, not even when I reboot.
Manually editing /etc/resolv.conf resolved the issue.
Regards, Frank
I opened a bugreport: #1046969 Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/e1300a36fc6d73d1c31496875817b5f2.jpg?s=120&d=mm&r=g)
Am 02.07.2017 um 20:12 schrieb Hendrik Woltersdorf:
Am 02.07.2017 um 09:51 schrieb Frank Krüger:
Hi there
After the recent update to Tumbleweed 20170630 my network stopped working. As a matter of fact, /etc/resolv.conf was not written properly by NetworkManager, not even when I reboot.
Manually editing /etc/resolv.conf resolved the issue.
Regards, Frank
I opened a bugreport: #1046969
Hendrik
Thank you. For a possible solution, i.e., /etc/dhclient.conf, please follow the link provided by Andrei Borzenkov in comment 1 of the above-mentioned bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1046969#c:1 Regards, Frank -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Andrei Borzenkov
-
Frank Krüger
-
Hendrik Woltersdorf
-
Knurpht - Gertjan Lettink
-
Mari Donkers
-
Michael Ströder
-
Mykola Krachkovsky
-
Sudhir Anand