dhcpcd-discuss

On Thu, May 24, 2018 at 9:49 AM, Roy Marples <roy@xxxxxxxxxxxx> wrote:

>
>
> On 24/05/2018 08:32, Serge Schneider wrote:
>
>> I've had a look at the patches we apply on top of upstream dhcpcd, and
>> this one is likely to be the culprit:
>>
>> --- a/if.c
>> +++ b/if.c
>> @@ -534,7 +534,7 @@
>>           /* We reserve the 100 range for virtual interfaces, if and when
>>            * we can work them out. */
>>           ifp->metric = 200 + ifp->index;
>> -        if (if_getssid(ifp) != -1) {
>> +        if (if_getssid(ifp) != -1 || *ifp->name == 'w') {
>>               ifp->wireless = 1;
>>               ifp->metric += 100;
>>           }
>>
>
> That could be the culprit if dhcpcd is setup to start wpa_supplicant on
> the interface, which dhcpcd-6.x will try and do by default.
> This has been turned off in dhcpcd-7.x and the user (or distro package)
> has to install the wpa_supplicant hook script if this functionality is
> still needed.
>

Yes , we have the hook enabled. Is that not the recommended way to start
wpa_supplicant when using dhcpcd?

IIRC, the original reason for adding this patch was that some wifi devices
don't match "if_getssid(ifp) != -1", so " *ifp->name == 'w'" was added as a
quick workaround.


> Roy
>
>