Mistery "foe_clear_entry", "Delete old entry" in kernel log

Installing and Using OpenWrt
1

There is some TP-Link router from a provider, its ip is 192.168.10.201, DHCP is off, wifi is ON. dnsmasq runs on another machine in the network at 192.168.10.200 and advertises 192.168.10.201 as a default route. Plus, there is another wifi access point (192.168.1.5). Things work fine for months.
Now, I replace TP-link with GL-MT6000 (OpenWrt 21.02-SNAPSHOT r15812+1082-46b6ee7ffc), things work but almost. Every few minutes network on my Amazon FireTV stops working - it keeps responding to pings but that's about it, kodi cannot access local share, other apps cannot go to the internet. On the GL-MT6000 router I am getting these a lot (every few minutes), these appear when FireTV fails:

Sun Dec 15 23:29:56 2024 kern.info kernel: [14718.998205] foe_clear_entry: state=2
Sun Dec 15 23:29:56 2024 kern.info kernel: [14719.001787] Delete old entry: dip =192.168.10.171
Sun Dec 15 23:29:56 2024 kern.info kernel: [14719.006478] Old mac= 90:11:95:61:10:58
Sun Dec 15 23:29:56 2024 kern.info kernel: [14719.010215] New mac= d4:a3:eb:88:66:dc

192.168.10.171 is ip of the FireTV, 90:11:95:61:10:58 is its mac.
d4:a3:eb:88:66:dc is a mac of some ONVIF camera, its ip is 192.168.10.234.
Switching the camera off fixes everything. Rebooting everything does not help at all. Connecting FireTV to the router's AP or an old AP does not change a thing.

What is triggering these "old mac"/"new mac" messages, where do these come from?

2

Pretty sure foe is short for flow offloading engine. That is still in somewhat active development with bugs getting fixed. Suggest upgrading to a newer OpenWrt - either 23.05.5 or if feeling adventurous 24.10.0-rc2 as running an old SNAPHOT release is hard to support.

3

An upgrade is definitely an option ((but annoying as it resets a lot of things) but I still wonder what is at fault here - the router or the firetv or the camera, and why? Can this FOE be disabled, for debugging?

4

Often listed as hardware acceleration / NAT offload.

5

the upgrade seems have helped but since it is very different setup (I pretty much had to configure routing from scratch), I am not sure I have enabled all the features to replicate the original problem.

6

You should report glinet firmware issues to glinet. They cannot be fixed from here (and thank you for upgrading to OpenWRT)

1 Like