FS#7165 - dhcpcd not run on network restart (no resolution of name)

Attached to Project: Arch Linux
Opened by Paul Robson (paulr) - Monday, 14 May 2007, 21:06 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 25 October 2007, 08:57 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture i686
Severity Medium
Priority Normal
Reported Version 0.8 Voodoo
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Fix for executing /etc/rc.d/network restart so it kills dhcpcd works ; however it now doesn't restart it.

[root@myhost paulr]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:76:81:C2:AF
inet6 addr: fe80::20c:76ff:fe81:c2af/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:264216 errors:0 dropped:0 overruns:0 frame:0
TX packets:219554 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:311495025 (297.0 Mb) TX bytes:20197624 (19.2 Mb)
Interrupt:20 Base address:0xcf00

fixed by dhcpcd eth0
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 25 October 2007, 08:57 GMT
Reason for closing:  Fixed
Additional comments about closing:  in latest initscripts
Comment by lanjelot (lanjelot) - Monday, 21 May 2007, 12:03 GMT
Correct, any dhcp-configured interface won't get an IP address after network restart and here is the explanation.
The network init script will skip any interface that is already up. And after /etc/rc.d/network stop, eth0 is still UP because killing dhcpcd does not bring an interface down.
I already proposed a fix for this issue in bug #6959.
See attached patch that works.
   network.patch (0.5 KiB)
Comment by Loic Nageleisen (lloeki) - Tuesday, 03 July 2007, 13:51 GMT
anyway, UP should not be made equivalent to inet addr, see  bug 7554 .
Comment by Matt (v01d) - Thursday, 02 August 2007, 04:38 GMT
I think the problem of restarting and dhcp could be solved with just adding the "ifconfig ${1} down" right after the dhcp kill, don't know what it wasn't solved before.
Comment by Loic Nageleisen (lloeki) - Thursday, 02 August 2007, 12:17 GMT
Matt, this would prevent ifplugd (and others) to work at all, because downing the interface will prevent cable sensing. That's because UP != inet addr, and why my solution in task #7554 fits (IMHO) better.
Comment by Matt (v01d) - Thursday, 02 August 2007, 12:46 GMT
Oh, ok. I understand. Hoped that 7554 gets attention then.

Loading...