[SOLVED] Network-manager 1.6.2-3+deb9u2 suddenly quit working

Questions about networking.
In the Original Post please also include the output of inxi -FNzxx
ron_widell
Posts: 10
Joined: 04 Nov 2017 20:23

[SOLVED] Network-manager 1.6.2-3+deb9u2 suddenly quit working

Postby ron_widell » 01 Oct 2019 00:32

Code: Select all

# inxi -FNzxx 
System:    Host: htpc Kernel: 4.9.0-11-amd64 x86_64 (64 bit gcc: 6.3.0)
           Console: tty 0 dm: lightdm Distro: SolydK 9 64-bit
Machine:   Device: desktop Mobo: Gigabyte model: GA-78LMT-USB3 6.0 v: x.x
           UEFI: Award v: F2 date: 11/25/2014
CPU:       Octa core AMD FX-8350 Eight-Core (-MCP-) cache: 16384 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 64000
           clock speeds: min/max: 1400/4000 MHz 1: 1400 MHz 2: 1400 MHz
           3: 1400 MHz 4: 1400 MHz 5: 1400 MHz 6: 1400 MHz 7: 1400 MHz
           8: 1400 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Venus LE [Radeon HD 8830M]
           bus-ID: 01:00.0 chip-ID: 1002:682b
           Display Server: X.org 1.19.2 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           tty size: 79x29 Advanced Data: N/A for root out of X                
Audio:     Card-1 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)    
           driver: snd_hda_intel bus-ID: 00:14.2 chip-ID: 1002:4383            
           Card-2 Advanced Micro Devices [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]                                                
           driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 1002:aab0
           Sound: Advanced Linux Sound Architecture v: k4.9.0-11-amd64
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: ce00
           bus-ID: 03:00.0 chip-ID: 10ec:8168
           IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 7161.4GB (24.1% used)
           ID-1: /dev/sdb model: TOSHIBA_HDWD120 size: 2000.4GB
           serial: X6NN2E5GS temp: 40C
           ID-2: /dev/sda model: SAMSUNG_HD160JJ size: 160.0GB
           serial: S08HJ10L473395 temp: 40C
           ID-3: /dev/sdc model: ST3000DM008 size: 3000.6GB
           serial: Z504E97G temp: 40C
           ID-4: /dev/sdd model: ST32000644NS size: 2000.4GB
           serial: 9WM32HE2 temp: 46C
Partition: ID-1: / size: 25G used: 7.1G (31%) fs: ext4 dev: /dev/sda3
           ID-2: /boot size: 976M used: 80M (9%) fs: ext4 dev: /dev/sda2
           ID-3: /opt size: 2.9G used: 30M (2%) fs: ext4 dev: /dev/sda6
           ID-4: /var size: 20G used: 3.0G (16%) fs: ext4 dev: /dev/sda8
           ID-5: /tmp size: 9.8G used: 23M (1%) fs: ext4 dev: /dev/sda4
           ID-6: /home size: 81G used: 496M (1%) fs: ext4 dev: /dev/sda9
           ID-7: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 19.6C mobo: N/A gpu: 43.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 225 Uptime: 3 days Memory: 502.3/16028.3MB
           Init: systemd v: 232 runlevel: 5 default: 2 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.121 running in tty 0) inxi: 2.3.5
A little over a week ago I applied the available updates to this system, which is my HTPC.
Since one of the updates was a new kernel, I rebooted the sysem (probably unnecessary , as the new kernel was already running).
When the system came back up, it would no longer connect to my local lan through the (one & only) wired NIC.
I had other priorities at the time, so I just shut the system down for a couple of days.

In the interim, my file server (a Kubuntu 18.04.3LTS machine) exhibited the same behavior. So I booted both machines up with alternative OS' and confirmed that the issue was NOT hardware related. So I tried rebooting with the previous kernel, but no joy, still no network connection.

Network-manager had previously been configured to set the wired connection up automatically via DHCP, but it was no longer doing that.
I saw, with ifconfig that the connection (enp0s3) was up, but had no IP4 address or netmask. If I manually set a static address and netmask, Network-manager would notice and stop spinning it's wheel, and I could connect to other machines on my local lan.

So I issued:

Code: Select all

#ifdown enp3s0 && ifup enp3s0 && dhclient enp3s0
and I could now connect to the internet as well as the local lan.
Network-manager detected the active connection, but I still couldn't get it to make a VPN connection over the wired connection.

So-- what's going on?
What else do you need to see?

I have a copy of /var/log/apt/history.og as well as the output of

Code: Select all

#journaalctl --no-pager | grep -A 5 -B 5 -n enp3s0 - > enp3s0.log
and I hope that attaching them to this message is the appropriate way to present them.

I'd really like to know how to solve this issue. I see that a new release based on Debian Buster is out, so I'll work on upgrading my system, but I want to solve this first.

Thanks,
ron
Attachments
history.log
(8.61 KiB) Downloaded 7 times

ron_widell
Posts: 10
Joined: 04 Nov 2017 20:23

Re: Network-manager 1.6.2-3+deb9u2 suddenly quit working

Postby ron_widell » 01 Oct 2019 00:35

enp3s0.log
enp3s0.log
(68.38 KiB) Downloaded 8 times

ron_widell
Posts: 10
Joined: 04 Nov 2017 20:23

Re: [SOLVED] Network-manager 1.6.2-3+deb9u2 suddenly quit working

Postby ron_widell » 03 Oct 2019 20:26

It appears that if you have Network-Manager configured to automatically initiate an openVPN connection when a physical connection is established (which I did) AND the openVPN can't be established, THEN Network-Manager will tear down the connection on the underlying physical interface, as well.

I had set my vpn service to automatically renew through @PayPal, which worked fine for a couple of years, until this year. This year @PayPal chose not to honor the automatic renewal, so my vpn service expired on 18 September, without notification from either @PayPal or my VPN service.

When I manually paid for another year of vpn service, the vpn connection configured in Network-Manager would sucessfully connect and Network-Manager would keep the underlying physical connection alive. There may have been error messages posted in one of the logs, but I was unable to find them.

So this is a cautionary tale for anyone trying to automatically connect to a vpn through Network-Manager.

ron

User avatar
ilu
Posts: 2496
Joined: 09 Oct 2013 12:45

Re: [SOLVED] Network-manager 1.6.2-3+deb9u2 suddenly quit working

Postby ilu » 04 Oct 2019 17:24

Thank you for your report. I'm afraid we can*t do much about this network manager behavior. Did you consider to report the problem upstream: https://gitlab.freedesktop.org/NetworkM ... ger/issues?

ron_widell
Posts: 10
Joined: 04 Nov 2017 20:23

Re: [SOLVED] Network-manager 1.6.2-3+deb9u2 suddenly quit working

Postby ron_widell » 05 Oct 2019 02:53

I wasn't expecting you (or anyone else) to do anything about it.

But once I figured out the root cause, I wanted to ensure that anyone else with the same problem would be able to find the cause and know the solution.

But reporting the issue upstream is a goof idea, Thanks.

ron


Return to “Networking”

Who is online

Users browsing this forum: No registered users and 1 guest