Have got the same problem. Is there a fix? I couldn't see anything in the bug reports. Regards, Sebastian

How are you trying to connect? You will only be able to connect via the LAN by default. Steve

There are many people running pfSense virtuallised with no problems. You are relying on the security of the host OS though. The raspberry pi is arm based and pfSense is x86 only so that's a non-starter. What bandwidth are you pushing? Do you intend to run packages? Steve

We discussed this outside of the forum and it ended up being a broken gmirror causing the kernel to load from one disk and the OS to load from the other. Fixing the mirror allowed the system to boot and run OK. Normally during an upgrade the OS and Kernel are all updated, so there had to be something else going on. :-)

Hi! I found the solution. I have two disks in a mirror (gmirror) and it turned out that one of the disks had been taken out of the mirror. The upgrade installed on the "good" disk, but when rebooting it read the core/OS from the bad disk and then swapped to the good disk when the mirror came online, so then I got an "old" OS and a new pfSense version. I removed the bad disk from the mirror and then added it again for rebuild (it was OK after checking it with smartctl). After reboot everything was ok :-)

At the initial interface config at the console the names of the available interfaces are listed. In a virtual environment the host presents virtual NICs to pfsense and there is often a choice of hardware it can simulate. Intel Gigabit NICs are a common type that would appear in pfSense as em0, em1 etc. Steve

USB fails at same stage, and just tried a R710 with different hardware an a PERC6/i and exactly the same. Tried removing the H200 from the R610 and booting, same result. I really want to avoid installing ESX, does anyone have any other ideas?

There is nothing in the file except for the XML start and stop tags Also, when there are portals, includin the extra zones, the backup file does not contain the zones in the backup file. When I place a pair of XML tags in the file that have no zones in it, the erroneous extra zones go away. So my ink concer now is why this is happening. Also, why is there an error when I create zones manually now? There are other related bugs too, like certificate based issues. I have reinstalled and re-tried all of this, and the errors still exist. I'm afraid I will have to skip this version of pfsens until it gets more stable. I can't upgrade our office to this version until its more stable. It's a shame.

@pvoigt: When the above BIOS message is appearing it's already to late to enter the BIOS. The problem this time was that I didn't really know at what point the memory test began. Pressing s very shortly after turning the power on got me into the BIOS setup. As the BIOS baud rate is now set to 9600 I can finally see the BIOS messages on every reboot. Your answers are of great value and your help is appreciated. Thanks again!

I have a Soekris with 128M and 2.1-RELEASE 4g. Running simple NAT/PAT to PPPoE WAN + one OpenVPN tunnel and routinely see these: Nov  9 03:48:52 sysname kernel: pid 63874 (php), uid 0, was killed: out of swap space I am coming to the conclusion that 128M is no longer adequate and am about to order a netgate 2D13 as a replacement. This is a new install, with OpenVPN replacing IPSec on a Cisco RV042 so I can't compare this install with 2.0.3.

Though the information on the doc wiki is old, it is still accurate if you want to do it by hand. It would probably be quicker and more reliable to back it up, put in the extra drive, and use the installer option for gmirror.

Can someone verify this?

I have the same problem but opening the page with another browser ip's are present. Try clearing cache and restart your browser.

It seems that the kernel panic only happens when booting the live medium. I deactivated the Realtek, installed pfsense, reactivated the Realtek in bios. The card is now working. It is a RTL8111E-VL. I looked it up in the manual.

The input validation was not effective. $input_errors array needs to be initialized. Fix is in pull request https://github.com/pfsense/pfsense/pull/848

@rjcrowder: @ckraimer: I appreciate the fix.  As of today, it doesn't appear there is a new version of cron available.  Has it been released yet? It has been fixed since early October… Cron package is at 0.1.8

@koos147: i think i have found it. the dest. addr in the portforward tab is not the local LAN address but it represent the local WAN address Yes, on Firewall: NAT: Port Forward: Edit GUI you are selecting traffic coming to a particular destination (usually a port(s) on a WAN(s)) - the destination that is the in original packet arriving from the internet. Then you fill in "Redirect target IP" and "Redirect target port" to send it on its way to where you really want it to go inside your network.

I have done lots of successful Alix 2D13 updates remotely across a functioning OpenVPN link, although all the recent ones have been from 2.1-BETAn to 2.1-RELEASE, since I was using 2.1-BETAn for some time, and I use the 2G image. The system reboots and OpenVPN re-establishes. There is no need to do "duplicate slice" before upgrading. The upgrade will write the new version on the slice you are not currently using, then switch boot slices and reboot. Perhaps you are duplicating slices, switching the boot slice, then not rebooting - or some unusual sequence that then causes the upgrade to not write to the expected place? If it comes up in factory defaults, then that implies config.xml has got lost, corrupted or??? That is on a separate CF partition, separate to the 2 boot slices/partitions.

It works for me on various 2.1 systems. I guess you need to look through what things are now setup in 2.1. This sort of chain of settings: a) Gateway for OPT1 is valid. b) Gateway group(s) exist with WAN and OPT1 selected in tiers the way you want (e.g. WAN and OPT1 on same tier for load-balanced traffic). c) Rule(s) on LAN that are directing traffic into the appropriate gateway group(s). Post the above settings if you are still stuck.