On 04/15/2012 03:57 PM, Ernst den Broeder wrote:
The host sees the packet as coming from !192.168.0.0/16 and will route to its default gateway. If your just playing around, you could add a route for 10.100.0.0/16 on your host to 192.168.3.1.
I did try this, but I don't think it worked.
The way you refer to 193.168.1.1/16 and 192.168.3.1/16 make me wonder if you understand that they are both in the same subnet. (just
Yes ... this is something specific a customer wants, with their internal gateway as a primary, and various sites routed through the pfSense firewall.
I didn't add any specific NAT rule entries beyond the basic entry I had done.
I am sure I am missing something obvious (and pilot error is strongly suspected on my part).
-- Joseph Landman, Ph.D Founder and CEO Scalable Informatics Inc. email: land...@scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/sicluster phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615 _______________________________________________ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
