[pfSense] Running into some very basic problems: can't seem to get port forwarding working ...
Ernst den Broeder
ernst at denbroeder.ca
Sun Apr 15 15:57:19 EDT 2012
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.
The way you refer to 18.104.22.168/16 and 192.168.3.1/16 make me wonder if you understand that they are both in the same subnet. (just checking - I mean no disrespect)
Sent from my iPod
On 2012-04-15, at 1:07 PM, Joe Landman <landman at scalableinformatics.com> wrote:
> Hi folks:
> Have pfSense 2.0.1 stable installed on a machine we are using for testing. 2x em network ports. Have em0 configured as WAN with IP 10.100.241.121/16, and em1 configured as LAN with IP 192.168.3.1/16.
> I can reach the LAN port with ssh/others easily. No issues. I turned on ICMP response on the WAN, and can ping that as well.
> Ok. Want to set up a simple external port forward from WAN->LAN (specific IP on LAN). Logged in through GUI, and set this up
> WAN TCP * * WAN net 22 (SSH) 192.168.1.171 22 (SSH)
> This host uses a different default gateway ... 192.168.1.1/16 . I can (and have) set up a virtual machine on the 192.168.3.0/16 net using the 3.1 machine as a gateway, and redirected ssh there. This works, fine as it turns out.
> My question is, how (if at all) can I configure pfSense to handle the case where it isn't the primary gateway? That is, its being used as a router for external traffic, but the primary gateway is on a different router. Do I need to add a specific route back on the client side, or is this something pfSense can automagically handle?
> Joseph Landman, Ph.D
> Founder and CEO
> Scalable Informatics Inc.
> email: landman at scalableinformatics.com
> web : http://scalableinformatics.com
> phone: +1 734 786 8423 x121
> fax : +1 866 888 3112
> cell : +1 734 612 4615
> List mailing list
> List at lists.pfsense.org
More information about the List