| Summary: | Failure starting the interface ethernet | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Georges Eckenschwiller <paiiou> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | mageia, marja11, nic, thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | journalctl | grep network | ||
Can you please try whether completely removing this interface, or both enp3s0 and eth0 if they both exist, with drakconnect --del or the same tool in MCC http://doc.mageia.org/mcc/5/fr/content/drakconnect--del.html and then readding it with drakconnect http://doc.mageia.org/mcc/5/fr/content/drakconnect.html solves the problem? CC:
(none) =>
marja11, thierry.vignaud Buqzilla is again accessible. For the moment I cannot make the manipulations. I managed to by-pass the problem: A net-install with boot-nonfree.iso of the 13-6-2015 ( mga5 ), but by choosing a mirror of cauldron. Here, no more of eth0 and everything works. It seems good that there is a confusion enter enp0s3 and eth0 @ Thierry This was the report I meant when commenting in https://bugs.mageia.org/show_bug.cgi?id=17928 The order of the renaming was only the other way around than I remembered: mars 07 14:31:55 localhost.localdomain systemd-networkd[785]: enp3s0: Renamed to eth0 mars 07 14:31:55 localhost.localdomain systemd-networkd[785]: eth0: Renamed to enp3s0 CC:
(none) =>
mageia Today, new install boot-nonfree.iso : 3 marcn 2016 mirror : 10 march 2016 delete eth0 with drakconnect --del reconfigure enp3s0 with drakconnect => network OK (In reply to Georges Eckenschwiller from comment #4) > Today, new install > > boot-nonfree.iso : 3 marcn 2016 > mirror : 10 march 2016 > > delete eth0 with drakconnect --del > reconfigure enp3s0 with drakconnect > > => network OK was it, in this new install, not OK before you deleted eth0? had an error message by the boot (relative to the network) and I could not reach the network. (In reply to Marja van Waes from comment #5) > (In reply to Georges Eckenschwiller from comment #4) > > Today, new install > > > > boot-nonfree.iso : 3 marcn 2016 > > mirror : 10 march 2016 > > > > delete eth0 with drakconnect --del > > reconfigure enp3s0 with drakconnect > > > > => network OK > > was it, in this new install, not OK before you deleted eth0? (In reply to Georges Eckenschwiller from comment #6) > had an error message by the boot (relative to the network) and I could not > reach the network. Assignee:
bugsquad =>
thierry.vignaud I think this is a duplicate of https://bugs.mageia.org/show_bug.cgi?id=17683 The issue seems to be that shorewall only has a eth0 interface and some action such as drakconnect which adds the enp3s0 interface and then starts working. CC:
(none) =>
nic (In reply to Nic Baxter from comment #8) > I think this is a duplicate of https://bugs.mageia.org/show_bug.cgi?id=17683 > Thierry thinks it should be closed as duplicate, too, see https://bugs.mageia.org/show_bug.cgi?id=18171#c5 *** This bug has been marked as a duplicate of bug 17683 *** Status:
NEW =>
RESOLVED |
Created attachment 7519 [details] journalctl | grep network For several days, the network interface does not work. In appendix, an extract of the journalctl | grep network