Network stopped working after update to Tumbleweed 20170630

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Network stopped working after update to Tumbleweed 20170630

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
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Hendrik Woltersdorf-2
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: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Mari Donkers (openSUSE)
Same here, had to configure static IP+address instead of using DHCP.

On 2 July 2017 10:22:02 CEST, Hendrik Woltersdorf <[hidden email]> 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
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Andrei Borzenkov
In reply to this post by Frank Krüger
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: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Sudhir Anand
In reply to this post by Frank Krüger
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: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Sudhir Anand
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: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Michael Ströder
In reply to this post by Sudhir Anand
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.


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Knurpht-openSUSE
In reply to this post by Frank Krüger
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: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Knurpht-openSUSE
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: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Mykola Krachkovsky
In reply to this post by Michael Ströder
неділя, 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
--
Найкращі побажання,
Микола Крачковський

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Mykola Krachkovsky
In reply to this post by Mari Donkers (openSUSE)
неділя, 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 <[hidden email]> 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
--
Найкращі побажання,
Микола Крачковський

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Hendrik Woltersdorf-2
In reply to this post by Frank Krüger
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: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Network stopped working after update to Tumbleweed 20170630

Frank Krüger
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: [hidden email]
To contact the owner, e-mail: [hidden email]