Phil Oester wrote: > It is caused by TCP sequence adjustment problems -- see my email with subject > '[PATCH] Fix NAT TCP sequence adjustment' Great. I'll get to that later tonight. Regards Patrick