On 29/05/2012 14:50, Ronald Pérez wrote:
You might want to do a packet capture on your Public and Private interfaces to make sure that the NAT is doing what you expect it to. Then you can probably work through the problem yourself.Any ideas?thanks!On Wed, May 23, 2012 at 12:36 PM, Ronald Pérez <[email protected] <mailto:[email protected]>> wrote:Hi All, I'm hitting i really curious problem, let me explain, this is the topology * * *Out_Server----(Public side)PFSENSE(Private side)------In_Server* When traffic goes from public to private side we apply a port forwarding and the request reach the "In_Server" perfect, but the reply from this "In_Server" goes through the firewall default gateway in place of the static route already configured, it's like the default gateway overrides the static route. However, if we send traffic from private to public side there is an Outbound NAT, the request reach the firewall and then is send it through the static route correctly, then the reply from "Out_Server" reach the "In_Server" perfect. Maybe i'm missing something but, why pfsense use static route when traffic goes from private to public side, but when it has to reply a request that first comes from public to private side don't. Any idea?
-- Regards, Giles Coochey, CCNA, CCNAS NetSecSpec Ltd +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
