The upgrade works fine for most people. All known issues are listed here: http://doc.pfsense.org/index.php/Upgrade_Guide Pay special attention to: http://doc.pfsense.org/index.php/Upgrade_Guide#International.2FSpecial_Characters_in_1.2.x_Configs We are also preparing the 2.0.2 release which includes several more upgrade fixes, but I don't recall if any of them would have resulted in any sort of crash.

@gderf: Looks like you are trying to boot a 64 bit version of pfsense on a 32 bit platform. :o  :o  :o Oh my god… you are right! Just confused by the file names  :-[ Sorry and thank you anyway for your time.

I have port forwarding on my WAN interface. I followed your steps A and C (B and D are unnecessary). Port forwarding is discussed on page 130 and following in the book "pfSense The Definitive Guide …" You haven't provided any information suggesting you should bridge WAN and DMZ. I don't know the details of the ordering of input processing but it is possible the bridge code will decide packets arriving on the WAN interface are for pfSense itself before the port forwarding can take effect. Note that it is sometimes necessary to reset firewall states after significant changes to the firewall rules - see Diagnostics -> States, click on Reset States tab. On removing the bridging it might be necessary to reboot for that configuration change to fully take effect.

You don't need to reset to defaults. Easiest way overall (for me anyhow) would be to download the config.xml and search/replace the old card with the new card, then restore the backup and let it reboot. Easiest way in the GUI, if both cards exist at once, is to create the tags on the new card and then reassign them. After you confirm they work on the new card, remove the tags from the old card, then take the old card out.

@jimp: Unfortunately unless you have some experience with unix it will be hard to manually recover from that missing library. Since you can't do an automated upgrade/firmware application, you'd have to manually transfer the fimware image to the firewall and unpack it manually to restore that library. Alternately, you could reinstall+restore your config, which would be a lot easier. That doc wiki link is talking about putting the config on a USB stick on the firewall. Thanks.  I tried that earlier this morning, and after installing from the LiveCD with the USB flash drive containing the old config files plugged in, the pfsense box rebooted and came back up with what look to be the previous settings (at least the IP info on the boot menu screen).  It's not hooked up to anything so I won't really know if it was truly successful until I take it back out to the remote office location and hook it back up.

You don't need anything special for handling a large hard disk beyond what you would need for the package itself. A 1 TB Squid cache would require about 10 GB of RAM however…

[2.0.1-RELEASE][root@pfsense.my_domain.com]/root(3): netstat -m 1036/764/1800 mbufs in use (current/cache/total) 769/599/1368/25600 mbuf clusters in use (current/cache/total/max) 768/384 mbuf+clusters out of packet secondary zone in use (current/cache) 0/27/27/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 1797K/1497K/3294K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/8/6656 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines

Wasn't sure where the bug tracker was, thanks.  Bug 2564.

@sgb: Thanks cmb.  Seeing as how the CARP IPs are already in place and the enumeration may be a problem, I'll schedule a full outage on the cluster. Not necessary, I've walked people through a number of such NIC additions with no issue. Do the secondary first, see if its NIC assignments have shifted, if so reassign the NICs (there will be no adverse consequences, but to make 100% sure of that, only plug it into a test network to see how the NICs get addressed). Then you know what to expect on the primary. It would be prudent to do it at a time that is as best possible in case you take them both down for some reason.

@victorhooi: In this case, it is just a simple ADSL2+ modem - Billion 5200 SRD modem - it cost just $27 from MSY…lol. Sorry, last time I looked there didn't seem to be many "just" modems. Many of the cheap boxes advertised as modems seemed to be modem/routers. @victorhooi: I've just changed from pfSense 2.0.1 to pfSense 2.1-BETA0, so I might give it a shot under that. It's a shame there isn't more verbose logging on why exactly the connection is failing, apart from a "timeout"…hmm. Your other post on DHCP on the Hacom suggested to me there was a problem in the communication between the modem/router and Hacom. Perhaps if that has been cleared up with pfSense 2.1 you might find PPPoE on pfSense 2.1 works. @victorhooi: Is there any way to increase verbosity of logging somewhere? Or some other diagnostics I can run from pfSense, such as trying the PPPoE negotiation manually from the console? Or would a packet capture help somewhere? Not even sure how to do that under FreeBSD…lol? You can do a packet capture by running tcpdump in a shell session or from the web GUI: Diagnostics -> Packet Capture. Depending on what you are looking for, a packet capture on either the ppp interface (pppoe0) or the physical interface (em0?) or both might be useful. @victorhooi: What other setups are you guys using for working PPPoE? I have use the configuration described in http://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall so I can access the modem web server from my home network on the other side of the pfSense box. This has been occasionally useful for troubleshooting.

heya, The DHCP client in this case is a Billion 5200 ADSL2+ modem. In this case, I restarted pfSense, and it seemed to work, sort of. Sometimes it'd work fine. Otherwise, if I I started it up, and then plug in the DHCP-serving modem, the WebConfigurator would sometimes become unresponsive - and even the VGA console on the server wouldn't respond to keystrokes. Since I couldn't get in via the web interface, console, or SSH, I didn't really have a way to retrieve /var/log/system.log  ???. However, the pfSense server would still respond to pings. Anyhow, I've ended up trying out pfSense 2.1-BETA0, and that seems to work ok with DHCP. Cheers, Victor

heya, Turns out it was actually a bad DOM SATA module =(. I emailed Hacom, and they said they had a bad batch of 8GB DOM chips…sigh. I wish they'd said that earlier. Anyhow, they're sending out a 64GB SDD to replace it =) - I'm using a spare Intel SSD I had lying around until then. It was just a bit confusing getting those error messages, and it being linked to a missing HDD - it didn't seem the most intuitive leap...lol. But then, hey, I've probably just been spoilt by Ubuntu and Arch installers...haha. Thanks all for your help =). Cheers, Victor

reboot has solved the problem :) thanks for support

Thanks, Ill setup and take to location in a few hours for testing.  Ill let you know.

Under diagnostics -> Backup/Restore … click on backup config and save it wherever you like.

OpenNTPD is gone from 2.0.2 and 2.1. It's ntp.org's daemon now on both.

@GullMoli: I'm quite slow when it comes to linux and working around in the shell environment so I'm having some trouble with this. pfSense is based on FreeBSD which is very similar to Linux in some aspects and quite different in other aspects. @GullMoli: (I cant figure out how to edit that file, or even get to it :l) How you tried the pfSense GUI function Diagnostics -> Edit File?

Hello guys, I´m having the same issue to upgrade. The packages to be removed are the original ones? I mean the "1.2.3-relaese packages", because the "Installed packages" I have none. Thanks. Jorge Eston