Thanks… that really solved the issue...  ;D 8) PS - Forgot to say... KEEP ON THE GOOD WORK, pfSense ROCKS!!!  ;D

Just upgraded. Final reboot and thats it, let the dust begin doing its job on sitting on perfect firewall :) Thanks to all involved!

It's been fixed and is back up if you haven't noticed already.

Release 2.1 upgrade (i386) was successful. I'm having some minor issues, will post them in an appropriate thread.

Might want to try to limit the HD to less than  1TB and also try to disable multicore and any CPU power saving features in BIOS.  Once installed, just re-enable multicore and C1E. http://forum.pfsense.org/index.php?topic=61799.0

This is a good start: http://forum.pfsense.org/index.php/topic,64315.0.html It could be worth making that post a sticky in General Questions or Installations and Upgrades.

You shouldn't have any problems upgrading from 1.2.3 to 2.0.3 but bringing a spare cf card can't hurt. The config file was updated between those releases. When you update it will be updated accordingly but that means it will no longer be compatible with 1.2.3. So you should make sure you've backed it up in case you have to switch back to the old slice. Steve

Guys, this weird method worked! Before touching the live system I made a quick test on the backup hardware by replacing the config file in the /conf directory and rebooted. As expected, interface mismatch happened, but during boot I fixed that with dummy values of that different hardware to let me in. I noticed that there were package problems, the config file brought the already broken package list from the live system. I compared the initial dummy config file with the one coming from the live system and copied the XML part referring to the packages from there. Brushed it up a little to keep packages's configs - except NTP which was completely changed during the update. Afterwards, a new reboot, new interface mismatch - but everything else seemed to work fine. Today I took the live system down, plugged in the newly created card with the patched config file, booted - et voila! It worked! Apart from having to click Save once in the NTP service settings page, everything worked fine! No interface mismatch or any other errors. Now I have a fully functional, fresh and up-to-date system, and during the process I had virtually no downtime on any of the services offered by the system.

Yes - And thank you for typing thanks  ;D (If only there were a more simple way right?) I'm glad its working for you.  The 2.1 official release will be out soon.  Update when its out.

In VirtualBox under the System section for your install, look at the boot order for the storage devices. Try moving Hard Disk to the top.

How did you disable the firewall? It probably stopped NAT working at the same time. Interesting the lease time helped. Do your clients generally keep the same address across a lease renewal? Steve

Packages are not and can't be compatible with the LiveCD in a clean/integrated way. You'd be better off with a NanoBSD install with a small SSD/USB. There is little benefit to continued long-term use of the LiveCD these days, even if it is the Memstick version.

I wish I knew enough to install this stuff for a living…    Sounds like fun.  :D I hope you got paid by the hour?

I don't believe there were any changes to the config file format between 2.0.1 and 2.0.3. Those were only bug fix updates. But backing up the config file takes seconds so do it anyway. Steve

Apologies for not being able to post this right away . . . I installed the new network cards and the issue has been resolved  ;D Thank you.

Interesting setup. The two DSL lines are bonded in the Cisco modem? I wonder what sort of bridge mode might be possible with such a setup. pfSense supports ML-PPP, which I imagine is what the Cisco box is doing, but you'd need two bridged modems to use it. Anyway that's further down the line. If you set it up initially as you suggested you should be good. I'm failing to see what possible reason there would be to running an ADSL modem/router just to provide DHCP.  ??? Steve

Hi thanks for replying.. I've gone through many threads about squid & multi wan.. everyone say to add a floating rule and add "tcp_outgoing_address 127.0.0.1" in squid custom options (I've already done that). But i'm still facing the same issue.. Please help!! For adding more information.. i'm currently using pfsense version 2.1-RC0 (i386). [image: c.JPG_thumb] [image: c.JPG]

I have an idea….  that you are using IE...  I'm wrong?

Yes I should have read your first post more closely. pfSense does not expect to see more than one disk so there's no option to do this from the webgui. There are a number of threads detailing peoples experiences with similar setups though. A number of people have used a second drive for a Squid cache when running from a flash drive primarily. Not sure about Snort but I expect it can be done with some manual tweaking. Steve