Recent content by dodgygeeza

Just to confirm, the workaround appears to have fixed the issue :-) ICMP connectivity to the AP has been solid and there have been no more bad ARP entries logged by pfSense (on the 65_2 release).

Testing now, haven't seen any bad ARP requests over the last hour and ICMP to the router now appears stable (after connecting/disconnecting multiple wifi devices). Will continue to check for the next 24 hours.

No output on 65_2.

Managed to get a connection for long enough to run the command/capture the output. Not sure the specific entry to check for, but there are a few MAC values listed: 0:macaddr=F8:32:E4:A6:D1:44 1:macaddr=F8:32:E4:A6:D1:40 2:macaddr=F8:32:E4:A6:D1:48 et0macaddr=F8:32:E4:A6:D1:40...

Hi RMerlin, AP was power-cycled twice, no difference sadly. I flashed the previous release and tested again, couldn't replicate the issue (nothing in pfSense, no bad ARP according to wireshark, even with the same device connected that was triggering it). I reflashed the latest version (_2) and...

On the 380.65.2 front I have also been having connectivity issues to the AP (AC3200 running in pure AP mode). After doing some digging (wireshark to the rescue) it appears that the AP is sending out a bad ARP request to the network. Specifically, while the ARP request contains the IP of the AP...