dhcpcd-discuss

Hello,

I am trying to update dhcpcd-6.11.1 from 6.9.2 so that I can use 6.11.2 short term
when you will release dhcpcd-6.11.2.

However I met one issue which always remained in waiting for carrier condition.

The attached patch (0001-Candidated-modification-way-to-meet-our-operation.patch)
can resolve this issue.

If possible, could you give me your advice whether it is reasonable modification?

I try to explain what I would like to do with some assumption.

[Background]
As the cause of issue may be not appropriate our operation, we have to control
dhcpcd functionality with master mode which always stays in one process during
CPU on.

In addition, we have to choose network interface one by one with master mode.
(Network interface are changed according to our system condition)

To realize the above on dhcpcd-6.9.2, the following way is adopted:

1. First start up time
   $ dhcpcd -M -b <network node name, e.g) eth0>
   $ dhcpcd --exit <same as the above network node name, e.g) eth0>
   Please note that we need only daemonised dhcpcd one process without DHCP function

2. When DHCP function is needed
   $ dhcpcd -M -b <network node name, e.g) eth0>


3. When DHCP function isn't needed
   $ dhcpcd --exit <same as the above no.2 network node name, e.g) eth0>

Repeat No.2 and No.3 accordingly. When CPU turns off, "$ dhcpcd --exit" performs.

Best Regards,
Koichi Okamoto

Attachment: 0001-Candidated-modification-way-to-meet-our-operation.patch
Description: 0001-Candidated-modification-way-to-meet-our-operation.patch