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.

just reinstall from scratch and save the effort.

@jimp: @diablo266: Sorry for bringing back an old thread but i've ordered a 6501-70 with slc msata ssd. Are the changes required for booting from msata listed here: http://doc.pfsense.org/index.php/Boot_Troubleshooting#NanoBSD_on_Newer_Hardware persistent across updates? This is going to be installed remotely and i'd like to limit any possible complications. If an update is capable of stopping the device from booting I think I will go with a USB drive install over msata (will be nanobsd regardless). Thanks! Yes, changes to loader.conf.local are preserved across updates. Excellent, thank for clearing that up jimp!

We have seen a similar thing happen on upgrade before but we could never reproduce it even with the same customer configuration. The IP is taken from the 'interface' selection on the IPsec Phase 1 settings. On 2.0.x, the vip "interface" names were different (vip1, vip2, etc where the number is the VHID), and on 2.1 the names changed to intX_vipY where the VIP interface (e.g. em0, fxp1, vr2, etc) is a part of the name. The code to rename the interfaces in the config.xml data during the upgrade must not have properly translated the old names to the new names.

About problem 2: I encountered the same issue after upgrading 2.0.2 to 2.1-RELEASE. The fix you suggested (editing captiveportal.inc) worked okay. This issue did not occur on fresh installs of 2.1 or when upgrading 2.1 BETA/RC to 2.1-RELEASE, only for 2.0 to 2.1.

Do you have multiwan? Ipv6 enabled? This can cause your symptoms: https://doc.pfsense.org/index.php/Controlling_IPv6_or_IPv4_Preference Also have a look through the suggestions in this thread: http://forum.pfsense.org/index.php/topic,68164.0.html Steve

Unfortunately that product id covers a number of revisions and not all are supported. The 8111e and earlier are supported. You could try this: https://forum.pfsense.org/index.php/topic,65355.msg365028.html#msg365028 Steve