OK. Stupid solution here, but put a static route in either the host using
IP route if it is windows, or put a static route in the default gateway of
that host. I have had some issues in the past and also put a static gateway
in the first router as well.
Internet > Router 1 > Router 2 ( on same s
On Sun, Apr 15, 2012 at 1:07 PM, Joe Landman
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
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
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 193.168.1.1/16 and 192.168.3.1/16 make me wonder if you
understand that they are
Have you configured a NAT rule?
-Original Message-
From: list-boun...@lists.pfsense.org [mailto:list-boun...@lists.pfsense.org]
On Behalf Of Joe Landman
Sent: Sunday, April 15, 2012 1:07 PM
To: list@lists.pfsense.org
Subject: [pfSense] Running into some very basic problems: can't se
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 r
