Any news about this famous issue?
Just remembering its 2nd aniversary since I saw this on MK routers.
Thanks for your reply.Yes it is still an old code, but we did some major fixes.
But what about the bug this thread is about? Is it fixed?
Aparently this issue is fixed in the new routing package.