I've just had the case that the networkDB looked correct, but the packages were still being routed to the wrong node.

I've detailed how I analyzed this and the potential fixes here: https://gist.github.com/dhilgarth/1d2c350ddb1204ae07640471b4f2a732

I had two different issues, but in both cases, the networkDB looked correct, but there still was an incorrect bridge fdb entry.

Originally posted by @dhilgarth in #47728