dhcpcd-discuss

[Trying to not drag this thread too far off-topic, but since I'm the one that brought up Pi-ARP issues most recently...]

> On Jun 15, 2020, at 9:53 AM, Bruce Ferrell <bferrell@xxxxxxxxxxxx> wrote:
> 
> On 6/15/20 4:35 AM, Roy Marples wrote:
>> ...
>> There is a known issue with some Pi boards where they don't respond to ARP requests either unless the interface is in promiscous mode.
>> There is a recent thread on this list about it.
> ...
> That issue was in some of the very early PI boards... I think it was the PI 1 generation.  I think back then they were synthesizing MAC addresses and they changed on every boot.  The units I'm working with right now are all fairly recent PI 3+ or PI 4+ boards.

I was specifically testing a Raspberry Pi Zero W, which has the Pi 1's SOC and the Pi 3's (Broadcom) Wi-Fi/BT chipset.  The FullMAC firmware being loaded by the meta-raspberrypi layer doesn't feed ARP packets to the kernel driver unless the interface is in promiscuous mode, which means that any address conflicts get lost... :/  The FullMAC power management can also cause problems when running over longer periods with little or no activity on the 'Pi, so you need to disable that as well...

Anyways, I will report back once I have a good long-term solution (on the original thread), but I wouldn't trust having your Raspberry Pi working as a litmus test for anything other than the 'Pi.  Get the others working, then make the Pi work with that...

________________________
Michael Sweet