dhcpcd-discuss

... and reverting the logging patch allowed dhcpcd to continue and get through the BCT link local tests without interaction.

____________________
Michael Sweet

> On Jun 3, 2020, at 2:03 PM, Michael Sweet <msweet@xxxxxxxxxx> wrote:
> 
> So following up after doing more testing and digging:
> 
> - Turning off power management was not sufficient.  I needed to leave the network interface in promiscuous mode for it to see the ARP packets. (waiting for a subscription request to go through for the Broadcom and Cypress wireless mailing lists so I can find out if this is a known firmware bug...)
> 
> - dhcpcd is quitting after 10 failed attempts to get an IPv4LL address.  Not sure if this is the result of the patch you gave me, I'm building a new Yocto image right now to confirm...
> 
> - If I re-associate (ifup wlan0 which fires up dhcpcd) manually after dhcpcd goes away, I'm able to complete the BCT link-local tests successfully!
> 
> 
>> On Jun 3, 2020, at 9:52 AM, Michael Sweet <msweet@xxxxxxxxxx> wrote:
>> 
>> Roy,
>> 
>>>> On Jun 3, 2020, at 8:31 AM, Roy Marples <roy@xxxxxxxxxxxx> wrote:
>>> 
>>> Hi Michael
>>> 
>>> On 03/06/2020 02:23, Michael Sweet wrote:
>>>> Roy,
>>>> I started with v8.0.2 (what is normally packaged with Yocto Zeus), then tried v8.1.6 (Yocto Dunfell's version), then v9.0.2 last week, then I saw v9.1.0 just got posted and tried that.  All of them fail in the same way during the IPv4LL tests... :/
>>> 
>>> Wow. If those versions all fail then something must be seriously wrong!
>>> ...
>>> I deliberately configred privsep for a bogus user to match your output.
>>> But it works either way.
>>> ...
>>> Can you try the attached patch please?
>>> It will hopefully provide some debug info to help show where the issue is.
>> 
>> OK, I tried the patch and didn't see any of the GOT ARP messages.  Then I ran tcpdump (tricky enough since it doesn't like it when the interface isn't up) and dhcpcd started seeing the ARP packets and BCT started getting happy.
>> 
>> tcpdump puts the interface in promiscuous mode...
>> 
>> Digging around a bit and it looks like a lot of people are seeing lost ARP packets on Raspberry Pi's when the network interface is not in promiscuous mode, and there might be some power management issues... So now I'm on to tracking down what is going on there...
>> 
>> (FWIW, both the Ethernet and Wi-Fi on these things go through USB-based FullMAC controllers, so I have a feeling this is going to have a common solution...)
>> 
>> ________________________
>> Michael Sweet
>> 
>> 
>> 
> 
> ________________________
> Michael Sweet
> 
> 
>