Bug 26021 - Networking stopped starting automatically on bootup - running "sudo dhclient" fixes networking
Summary: Networking stopped starting automatically on bootup - running "sudo dhclient"...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-05 11:59 CET by Shlomi Fish
Modified: 2020-01-25 17:20 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Shlomi Fish 2020-01-05 11:59:08 CET 
Description of problem:

Networking (IPv4) stopped starting automatically on bootup - running "sudo dhclient" adds networking to mageia 8. The network on boot was OK a few days ago.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Lewis Smith 2020-01-05 20:53:39 CET 
> The network on boot was OK a few days ago.
Can you say what updates you have had since?
 $ rpm -qa --last | less
then paste the latest updates back to when it worked, as best as you can judge. Looking for a relevant update that might have caused the problem.

CC: (none) => lewyssmith

Comment 2 Shlomi Fish 2020-01-25 17:20:43 CET 
Hi!

Seems like the problem fixed itself up after some updates recently (possibly the grep-exit-code-related initscripts bug that was fixed). It also now restores networking after suspending-and-waking up which was also an issue. Marking as WORKSFORME.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.