Just to be clear you switched to IKEv2 on the Soekris box? Steve

Hello, Just to let you know that my IPv6 is working now, again it seemed to be a faulty firewall rule. Once the connection established between my "pfsense" <-> "default isp gw" everything else went fine. . public addresses 2800:160:17C5::/48 . internal addresses 2800:160:17C5:1~4::/64 Initially I messed up with dhchpv6, then manual ipv6, finally stateless :-) and it works all right! Again, thank you all for your great comments and support!

If you have LAN and WAN, then everything is blocked coming from WAN. You need to access from LAN (make a VM client on LAN side) or the console. From there you can add pass rules on WAN if you need to allow access from a "private" WAN side to manage it.

This https://github.com/pfsense/pfsense/pull/1508/files isn't yours ?? I'll post in git to tack the attention back here.

The rrd data will not survive across an architecture but usually simply doesn't appear. If you have a backup of the config file without rrd data try that. Steve

Successful in booting 2.2 from another usb stick without any fuss. Must have been some compatibility issue with the first usb stick and 2.2 so I will use it for 2.1

Indeed it does!  ::) In NanoBSD the filesystem is supposed to be mounted read-only. It gets re-mounted as read write only when a config change is saved. It is designed that way to prevent excess writes to flash media. https://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/ Steve

I am trying to make change in GitHUB now for everyone.  I made this change but and others for 64 bit which I think spawned jimp to change it.  But there is that one change I made that didn't get into it.  I will try again tonight see if I can get github to work with me .. still learning it I was the one that fixed the LED's on the Crystalfontz displays so I did it in past lets see if I can do it again

In 2.2 you can use 'hybrid' mode which allows you to add your own rules but keep the automatic rules added for a new interface. Steve

You did not install… You are booting live CD.

I'm headed out for a few hours I'll reply to any other questions later in the day. Thank you

What error are you seeing? Nano or full install? 32 or 64bit? Steve

Aaah yes, now why didn't I think of that. Fixed. Thanks

Can you ping the OPT1 gateway, 192.168.1.1? What is the actual error produced when you try to ping from the OPT1 WAN? Is that your own IP address, 21.1.1.7/24? If not why are you using it? Anything in the logs? Steve

I would highly recommend that you stop right now and grab pfSense 2.2-x64 and start from there. I've setup a small lab in Virtualbox many times before and I usually create a 3-NIC vm with em0 simulating a WAN link on my LAN, em1 on intnet1 and em2 on intnet2 to simulate a LAN and DMZ (nevermind em2 if you're not doing a DMZ).  Then I create a small vm (Lubuntu or something) on intnet1 to talk to pfSense WebGUI and do all my testing and playing in the small vm.  Slap a LAMP serve rin the DMZ and play away.  BY default, your WAN is set to block private IP space, so you need to disable that if you want to access it from your real LAN, like testing a port-forwarded server in your DMZ.  Uncheck Interfaces - WAN - Private networks - Block private networks.

From what I gather both hard drives are fine. I ran Seagate tools on both using quick test and the both passed.

I can do it from lan, it doesn't matter since the configuration is being done locally.