[Bug 1188949] New: The wired connection stops connecting the next day after installation
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949 Bug ID: 1188949 Summary: The wired connection stops connecting the next day after installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: vladislavmil@mail.ru QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 851456 --> http://bugzilla.opensuse.org/attachment.cgi?id=851456&action=edit NetworkManager logs, inxi-Fxz output, video and photo with error demonstration After installation, the wired connection works correctly. The next day, it stops connecting. There is a network connection that lasts indefinitely. Creating new connections does not lead to any result, as does trying to reconnect to an existing connection. It only helps to roll back the system to the backup created immediately after installation. The bug manifests itself on all DE and the next day after installation. During installation, the system configures the wired connection itself and the installation takes place without any errors. The problem manifests itself in openSUSE Leap and Tumbleweed, the wired connection works correctly on other distributions. I tried to install the r8168 driver, and add r8169 to the blacklist, but this does not help. Installing a third-party custom kernel also does not fix the problem. IPv4, IPv6, DNS and the default route disappear from the connection settings. I looked at the Network Manager configs, but there is nothing suspicious there, because of which the problem could manifest itself. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c2
--- Comment #2 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c3
--- Comment #3 from Jonathan Kang
Created attachment 851677 [details] journalctl -b -u NetworkManager
Here is the NetworkManager log for today. It was not possible to connect the first time, but it turned out the second time. Sometimes it is possible to randomly establish a connection. The DHCP must be configured correctly. Before that, I worked on Linux Mint for a year, I never had such a problem.
Do you mind uploading the content of "journalctl -b" instead of journal only from NetworkManager? You mentioned creating a new connection doesn't help either. Could you show the output of "nmcli connection show $newly-created-connection-name" as well? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c8
--- Comment #8 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c9
--- Comment #9 from Jonathan Kang
Created attachment 852086 [details] journalctl -b -u NetworkManager from a third-party repository
Yes, I noticed that I installed this package incorrectly. I installed it for the second time, but this time correctly. Even in the config, NetworkManager replaced dhcp=dhclient to dhcp=internal. I noticed a very strange behavior of the network. The network was connected to the Internet normally for two days, but this morning it refused to connect again. I had to use the phone as a USB modem. In the afternoon, I turned it on again and the network was already connected normally. The strange thing is that I noticed that if you connect the Internet via your phone as a USB modem, then after disconnecting it from the computer, the network sometimes connects correctly for some time.
The logs indicates that during the phase of DHCPDISCOVER, the ethernet link was disconnected somehow and your system cannot get DHCPOFFER from the dhcp server. But without the whole "journalctl -b" for the system, I'm unable to tell exactly why the link was disconnected and no carrier was available for the ethernet interface. Could you please attach the output of "journalctl -b" here? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c10
--- Comment #10 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c13
--- Comment #13 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c14
--- Comment #14 from Vladislav Milenin
(In reply to Vladislav Milenin from comment #11)
Created attachment 852201 [details] Logs of dhcp=dhclient
After replacing dhcp=dhclient to dhcp=internal, the Internet was connected correctly for these few days. But it was worth changing these values back, as the same problem reappeared. In a non-working state, I took the logs again and returned them back to dhcp=internal, since it works better with it.
Can you install NetworkManager from the repo mentioned in comment#5 and provide logs again? More verbose messages are needed to debug dhclient.
Thanks.
I conducted additional testing. It seems that changing the parameter in the NM config to dhcp=internal solves the problem, because after that the Internet began to connect normally. But I still did not understand why such an error is obtained with the parameter dhcp=dhclient. You asked to install NM from comment#5, which I did. YaST notified about the correct installation, then restarted the computer and took the logs. But you write that NM is still installed from the standard openSUSE repositories. I checked again and left a screenshot of YaST in comment#13, where it is clear that NM is installed from the GNOME repository:Factory, which was added after installing the package. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c15
--- Comment #15 from Jonathan Kang
(In reply to Jonathan Kang from comment #12)
(In reply to Vladislav Milenin from comment #11)
Created attachment 852201 [details] Logs of dhcp=dhclient
After replacing dhcp=dhclient to dhcp=internal, the Internet was connected correctly for these few days. But it was worth changing these values back, as the same problem reappeared. In a non-working state, I took the logs again and returned them back to dhcp=internal, since it works better with it.
Can you install NetworkManager from the repo mentioned in comment#5 and provide logs again? More verbose messages are needed to debug dhclient.
Thanks.
I conducted additional testing. It seems that changing the parameter in the NM config to dhcp=internal solves the problem, because after that the Internet began to connect normally.
I suspect that it's a dhclient issue, so I enabled verbose in the package provided in comment#5.
But I still did not understand why such an error is obtained with the parameter dhcp=dhclient. You asked to install NM from comment#5, which I did. YaST notified about the correct installation, then restarted the computer and took the logs. But you write that NM is still installed from the standard openSUSE repositories. I checked again and left a screenshot of YaST in comment#13, where it is clear that NM is installed from the GNOME repository:Factory, which was added after installing the package.
You should be installing NetworkManager from home:JonathanKang:braches:GNOME:Factory instead of GNOME:Factory. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c16
--- Comment #16 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c17
--- Comment #17 from Jonathan Kang
Created attachment 852384 [details] Logs NM of JonathanKang braches GNOME Factory
I changed the NM repository to home:Jonathan Kang:branches:GNOME:Factory and took the logs again.
dhclient never receives an DHCPACK after sending DHCPREQUEST message. But I have no idea exactly why. I guess you're using a router, so it won't be possible to get dhcp related logs from the dhcp server side. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c18
--- Comment #18 from Vladislav Milenin
(In reply to Vladislav Milenin from comment #16)
Created attachment 852384 [details] Logs NM of JonathanKang braches GNOME Factory
I changed the NM repository to home:Jonathan Kang:branches:GNOME:Factory and took the logs again.
dhclient never receives an DHCPACK after sending DHCPREQUEST message. But I have no idea exactly why. I guess you're using a router, so it won't be possible to get dhcp related logs from the dhcp server side.
Yes, I use a Zyxel keenetic lite III router. The router was configured by the master once, during installation. For all the time of operation, not a single device had any connection errors via a wired connection and Wi-Fi. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c19
Jonathan Kang
������ 08 18:26:56 localhost dhclient[1047]: Internet Systems Consortium DHCP Client 4.4.2-P1 ������ 08 18:26:56 localhost dhclient[1047]: Copyright 2004-2021 Internet Systems Consortium. ������ 08 18:26:56 localhost dhclient[1047]: All rights reserved. ������ 08 18:26:56 localhost dhclient[1047]: For info, please visit https://www.isc.org/software/dhcp/ ������ 08 18:26:56 localhost dhclient[1047]: ������ 08 18:26:56 localhost dhclient[1047]: Listening on LPF/enp2s0/70:8b:cd:9e:5b:b2 ������ 08 18:26:56 localhost dhclient[1047]: Sending on LPF/enp2s0/70:8b:cd:9e:5b:b2 ������ 08 18:26:56 localhost dhclient[1047]: Sending on Socket/fallback ������ 08 18:26:56 localhost dhclient[1047]: DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 5 (xid=0x1b7bdecb) ������ 08 18:26:56 localhost dhclient[1047]: DHCPOFFER of 192.168.1.43 from 192.168.1.1 ������ 08 18:27:01 localhost dhclient[1047]: DHCPREQUEST for 192.168.1.43 on enp2s0 to 255.255.255.255 port 67 (xid=0x1b7bdecb) ������ 08 18:27:05 localhost dhclient[1047]: DHCPREQUEST for 192.168.1.43 on enp2s0 to 255.255.255.255 port 67 (xid=0x1b7bdecb) ������ 08 18:27:11 localhost dhclient[1047]: DHCPREQUEST for 192.168.1.43 on enp2s0 to 255.255.255.255 port 67 (xid=0x1b7bdecb)
Complete version of these logs are in comment#16. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c20
Reinhard Max
I guess you're the maintainer of dhclient.
yes, I am the maintainer of the dhcp package, but not a deep expert in DHCP.
Do you have any idea about what could go wrong here?
I discussed this with Marius, but we couldn't find a possible reason within dhclient that would explain this. To narrow this further down we want to see if the missing DHCPACK packages are not being sent by the router, being filtered by the kernel, or being silently ignored by dhclient, because it thinks they are invalid. For that, please disable your firewall (if it is active) and change some settings: # sysctl -w net.ipv4.conf.all.log_martians=1 # sysctl -w sysctl -w net.ipv4.conf.all.rp_filter=0 Then record all DHCP packages over at least one occurance of dhclient sending a request and seemingly getting no ack: # tcpdump -W /tmp/dhcp4.pcapng -s 65535 -Uvnfi any 'port 67 or port 68' Interrupt tcpdump with Ctrl-C when done and upload /tmp/dhcp4.pcapng as an attachment. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c21
--- Comment #21 from Vladislav Milenin
(In reply to Jonathan Kang from comment #19)
I guess you're the maintainer of dhclient.
yes, I am the maintainer of the dhcp package, but not a deep expert in DHCP.
Do you have any idea about what could go wrong here?
I discussed this with Marius, but we couldn't find a possible reason within dhclient that would explain this. To narrow this further down we want to see if the missing DHCPACK packages are not being sent by the router, being filtered by the kernel, or being silently ignored by dhclient, because it thinks they are invalid.
For that, please disable your firewall (if it is active) and change some settings:
# sysctl -w net.ipv4.conf.all.log_martians=1 # sysctl -w sysctl -w net.ipv4.conf.all.rp_filter=0
Then record all DHCP packages over at least one occurance of dhclient sending a request and seemingly getting no ack:
# tcpdump -W /tmp/dhcp4.pcapng -s 65535 -Uvnfi any 'port 67 or port 68'
Interrupt tcpdump with Ctrl-C when done and upload /tmp/dhcp4.pcapng as an attachment.
I have a few questions. I need to use NetworkManager from the openSUSE repositories or from the home repository:Jonathan Kang:branches:GNOME:Factory. If it is from the openSUSE repositories, is it in working condition or when the Internet stops connecting? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c22
--- Comment #22 from Jonathan Kang
(In reply to Reinhard Max from comment #20)
(In reply to Jonathan Kang from comment #19)
I guess you're the maintainer of dhclient.
yes, I am the maintainer of the dhcp package, but not a deep expert in DHCP.
Do you have any idea about what could go wrong here?
I discussed this with Marius, but we couldn't find a possible reason within dhclient that would explain this. To narrow this further down we want to see if the missing DHCPACK packages are not being sent by the router, being filtered by the kernel, or being silently ignored by dhclient, because it thinks they are invalid.
For that, please disable your firewall (if it is active) and change some settings:
# sysctl -w net.ipv4.conf.all.log_martians=1 # sysctl -w sysctl -w net.ipv4.conf.all.rp_filter=0
Then record all DHCP packages over at least one occurance of dhclient sending a request and seemingly getting no ack:
# tcpdump -W /tmp/dhcp4.pcapng -s 65535 -Uvnfi any 'port 67 or port 68'
Interrupt tcpdump with Ctrl-C when done and upload /tmp/dhcp4.pcapng as an attachment.
I have a few questions. I need to use NetworkManager from the openSUSE repositories or from the home repository:Jonathan Kang:branches:GNOME:Factory.
Either is okay.
If it is from the openSUSE repositories, is it in working condition or when the Internet stops connecting?
This hasn't be fixed. So it's not in proper working condition. We want a bit more information from your system for further debug this issue. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c23
--- Comment #23 from Reinhard Max
If it is from the openSUSE repositories, is it in working condition or when the Internet stops connecting?
We need at least a package dump taken while the problem shows on your system, but if you can also take a sample while things are working, that would be even better. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c24
--- Comment #24 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c25
--- Comment #25 from Reinhard Max
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c26
--- Comment #26 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c27
--- Comment #27 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c28
--- Comment #28 from Jonathan Kang
Created attachment 852545 [details] dhcp4.pcapng file without firewall
I'm very sorry, I forgot to disable the firewall. Here is the new file where I disabled the firewall.
There two are empty file without any package inside. You need to reproduce this issue with tcpdump command running. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c29
--- Comment #29 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c30
--- Comment #30 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c31
--- Comment #31 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c32
--- Comment #32 from Reinhard Max
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c33
--- Comment #33 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c34
--- Comment #34 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c35
--- Comment #35 from Reinhard Max
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c36
--- Comment #36 from Vladislav Milenin
It contains no ACK packets either, so there is nothing new to learn from it.
It turns out that as a solution to the problem it is worth using the dhcp = internal parameter from comment#7, since it was not possible to establish the reason for the incorrect operation of the dhcp = dhclient parameter? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c37
--- Comment #37 from Jonathan Kang
(In reply to Reinhard Max from comment #35)
It contains no ACK packets either, so there is nothing new to learn from it.
It turns out that as a solution to the problem it is worth using the dhcp = internal parameter from comment#7, since it was not possible to establish the reason for the incorrect operation of the dhcp = dhclient parameter?
Yes, you can use "dhcp=internal" as a solution/workaround. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c38
--- Comment #38 from Vladislav Milenin
(In reply to Vladislav Milenin from comment #36)
(In reply to Reinhard Max from comment #35)
It contains no ACK packets either, so there is nothing new to learn from it.
It turns out that as a solution to the problem it is worth using the dhcp = internal parameter from comment#7, since it was not possible to establish the reason for the incorrect operation of the dhcp = dhclient parameter?
Yes, you can use "dhcp=internal" as a solution/workaround.
What then to do with an open bug? I think it shouldn't be closed if new details or ideas appear in the future. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c39
--- Comment #39 from Jonathan Kang
What then to do with an open bug? I think it shouldn't be closed if new details or ideas appear in the future.
This should be kept open until further progress is made and it's fixed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c45
Raija Ruuska
(In reply to Jonathan Kang from comment #42)
(In reply to Vladislav Milenin from comment #41)
Created attachment 854023 [details] dhclient log
When executing the command "dhclient -v -d eth0" nothing happens and "Device "eth0" does not exist." is output. My network is called enp2s0, as the system automatically named it during installation. In the command, I changed "eth0" to "enp2s0" and it was executed correctly.
Yep. Use your ethernet interface name instead.
The log shows that dhclient still cannot get an reply from DHCP server. It didn't even get an DHCPOFFER this time.
I've run out of ideas what it could be. Most likely, this is a unique bug on my configuration, which cannot be reproduced by anyone else. At the moment, as a solution, I use the dhcp=internal parameter from comment#7 and it works fine all the time.
I have a brand new mini PC ASUS ExpertCenter PN52 and I have the same problem. The network disconnects every few days. I have not noticed the same error in another mini PC (Intel� NUC Kit NUC8i7BEH). Both computers have the same software Tumbleweed 20221202. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c46
--- Comment #46 from Raija Ruuska
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c47
--- Comment #47 from Raija Ruuska
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c48
--- Comment #48 from Raija Ruuska
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c49
--- Comment #49 from Raija Ruuska
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c50
--- Comment #50 from Raija Ruuska
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c51
--- Comment #51 from Raija Ruuska
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c52
--- Comment #52 from Raija Ruuska
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c53
--- Comment #53 from Raija Ruuska
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c54
--- Comment #54 from Raija Ruuska
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c55
--- Comment #55 from Reinhard Max
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c56
--- Comment #56 from Vladislav Milenin
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949
http://bugzilla.opensuse.org/show_bug.cgi?id=1188949#c57
--- Comment #57 from Raija Ruuska
participants (1)
-
bugzilla_noreply@suse.com