Hi Wang and Tomáš, When I adopted ebtables in 2018 and I was initially focused on putting the package in shape, but this bug has remained unattended for too many time.
Now, installing i386 ebtables userspace tool on an amd64 kernel I can't reproduce this bug. I've tested both ebtables-legacy (provided by ebtables package) and ebtables-nft (provided by iptables package) on buster and sid, so I think that this bug has been solved at any moment since you reported on ebtables 2.0.10.4-3. ebtables versions tested: buster: ebtables:i386 2.0.10.4+snapshot20181205-3 i386 iptables 1.8.2-4 linux-image-4.19.0-6-amd64 4.19.67-2+deb10u2 sid: ebtables:i386 2.0.11-1 iptables 1.8.4-1 linux-image-5.3.0-3-amd64 5.3.15-1 In all the combinations tested the behaviour was the expected not the reported in your bug. Please, reply this message with any other information needed if the bug remains in other scenario. Regards, Alberto
