We indeed see the state being created. The packet egresses on the external

interface without NAT. So the ip packet contains the source ip address of my

laptop and therefor further on the path gets blocked because it isn't natted.

A few seconds/minutes later I try again and everything works again.
Is there a way to see why it isn't doing the NAT?
(There are around 80 interfaces (vlan + carp) on the box.)
Regards,
Andy.
No virus found in this outgoing message.

Checked by AVG Free Edition.

Version: 7.5.472 / Virus Database: 269.8.13/843 - Release Date: 10/06/2007

13:39
______________________________________________________________________
This email and any files transmitted with it are confidential and intended

solely for the use of the individual or entity to whom they are addressed.

If you have received this email in error please notify the system manager at :

systeembeheer@cegeka.be or call +32-(0)11-240234.

This footnote also confirms that this email message has been swept by Sophos

for the presence of computer viruses.

______________________________________________________________________

pfctl -x loud  && tail -f /var/log/messages
~BAS
l8*

 	-lava (Brian A. Seklecki - Pittsburgh, PA, USA)

 	       http://www.spiritual-machines.org/
     "Guilty? Yeah. But he knows it. I mean, you're guilty.

     You just don't know it. So who's really in jail?"

     ~Maynard James Keenan

Maybe try to check and possibly replace the interfaces involve as well as the cables and