Hey Seth,
On Fri, Aug 7, 2015 at 6:57 AM, Seth Mos wrote:
> Hi,
>
> Only to reply to myself here, but it appears that pfSense 2.2.4 is back
> to the problem I had on pfSense 1.2 in 2008.
>
> A cursory investigation on a test node it appears that it fails to load
> all SPD entries. Both the output
On Thu, Aug 6, 2015 at 1:12 PM, Alfredo Tapia Sabogal <
alfred.ta...@gmail.com> wrote:
> internal network (LAN) em1 far as I did well, but I have some problems with
> my IP's range of IP's from my provider are 192.168.0.1 (router) in the
> PFSENSE I assigned the network card for the WAN 192.168.0.
Hello;
I'm testing the installation of pfSense and using VirtualBox I can also
create two network interfaces, one for the WAN (em0) and the other for
internal network (LAN) em1 far as I did well, but I have some problems with
my IP's range of IP's from my provider are 192.168.0.1 (router) in the
P
Hi,
Only to reply to myself here, but it appears that pfSense 2.2.4 is back
to the problem I had on pfSense 1.2 in 2008.
A cursory investigation on a test node it appears that it fails to load
all SPD entries. Both the output of ipsec status as well as setkey -DP
lack large amounts. It appears to
