| Summary: | dhcpd starts before LAN interface is up | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bjarne Thomsen <bjarne.thomsen> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | Not sure. initscripts? | CVE: | |
| Status comment: | |||
|
Description
Bjarne Thomsen
2015-01-02 11:19:09 CET
Some further experiments show that connecting a PC via dhcp on the local net works after a re-configuration. Also, in mga4 "systemctl status dhcpd.service" shows that the server continues re-starting after the message receive_packet failed on eth1: Network is down Furthermore, dhcpd is running after a re-boot. The dead firewalle monitor mandi is not caused by the re-configuration: it never came up during the boot process. The alarming message "receive_packet failed on enp2s0: Network is down" is appearently not a problem, so I am closing it. Status:
NEW =>
RESOLVED |