I have a somewhat unusual config - a hap lite, with wireless in station mode, part of a bridge (call it wan-bridge) with eth1. Then there is a second bridge (call it lan-bridge), that has eth2 configured master, and then eth3 and eth4 are slaves. There is a nat running between the bridges, and eth1 does not have a cable plugged in most of the time. The standard firewall rules from the normal CPE mode are changed to act on interface wan-bridge instead of wlan1 where applicable (the drop rules), and the nat chain outbound interface in wan-bridge.
It is convenient traveling setup powered from a 10000maH powerbank or my laptop which is connected via eth2 (most of the time). The idea is to make it more convenient to connect to wifi or wired services in hotels and other untrusted public places.
It has worked fine for a few months with few versions (6.29,6.30,6.31,6.32,6.32.1), but after upgrading to 6.32.2 it does not seem to work. What happens is that the wlan1 connects to the AP, the DHCP client on the wan-bridge obtains an IP, and sets default route, but the router is unable to send any packets to the default gateway - ping timeout coming from local wan-bridge interface ip. Looking at the arp table does not show any entry for the default gw, even though it is the same as the dhcp server, and disabling and enabling the dhcp client always is able to bind to the dhcp. My wan-bridge has the arp option enabled.
Has anyone seen something similar after the upgrade?