August 28, 2010 at 4:13 am #51011
seems to be a known bug. old post now, any new info? does seem it might not play nice with NAT. i thought a balancing rule of in eth00.2 out eth00.2 might do the trick but no help. is this a linux kernel bug i wonder?