You are right…From now on, I will try not to duplicate the same topics... @cmb: Stop duplicate posting things, you still have 2 threads of this and I deleted 3 others you posted yesterday. Don't ever post the same thing twice.

http://doc.pfsense.org/index.php/Upgrade_Guide#Changing_architecture_.2832_bit_to_64_bit_or_vice_versa.29_during_upgrade

Cool, thanks!

Thank you cmb, that is very helpful to my understanding.

The lighttpd logs went nowhere before. So these always happened you just never saw them. It tends to show up more often with captive portal. It's not fatal, you can most likely ignore them.

What bandwidth will is need to handle? What packages are you wanting to run? How many interfaces? Anything else you think might be pertinent.  ;) Steve

As you found by default everything is blocked on WAN. If you need to access anything from the WAN side you have to add firewall rules to explicitly allow it. Steve

Did you look at the sticky? http://forum.pfsense.org/index.php/topic,1998.0.html

Should have probably stated I'm using i386 embedded (nanobsd) on a Firebox x700.

Using virtual adapters the detection code may not be able to see the change correctly. Just select the interfaces manually instead of using the auto-detect. I imagine they will be shown as em0 and em1. This shouldn't affect the normal operating of the NICs. Steve

not sure how your email got buried in my inbox (sales emails only come to me until we get our ticket system upgraded in a couple weeks) but I just responded to you. Definitely something we can help you with, can have that entire config done within a day of purchase.

Configure your access point to assign the two ssids to two VLANs. Then setup VLAN interfaces on pfSense to connect to it. That way the 'internal' and 'guest' traffic will arrive on separate interfaces so you can have different rules and CP etc. Steve

The nanobsd images are meant to be written to flash media, such as a CF card. PfSense will then boot directly from that. No hard drive needed. The memstick images are used to create a bootable USB stick that you can use to install pfSense to the hard drive. See: http://www.pfsense.org/index.php?option=com_content&task=view&id=43&Itemid=44 Steve

Any particular reason you want to downgrade ?

Thank you for your answer. For the moment, they were in raid mode, than i changed them to ahci and set up pfSense on one single disk. The problem is that i would like to ensure that if one disk fails the firewall could work further without downtime… do that work fine with gmirror?

@johnpoz: That thread is about nat reflection - which no where in your post did you state where you were trying to access these sites from.  You would have to assume from outside your firewall - since the normal operation in accessing a site while on that network would be to access it via its common IP on your own network. Also you state that wan admin access is "default" - that is not the case.  You can not access admin gui of pfsense from wan in a default state of pfsense. You would have to configure firewall rules to allow access to web gui/ssh from wan - which is not a recommended configuration. Glad you got what you wanted sorted, but you really need to accurately convey your issue and your setup if don't want people guessing what your question/problem is. You know what, you are absolutely right! I was a bit short on time to get this sorted out and the fact that my problem description sucked completely did not help anyone… Question 1: I got slightly confused as I tried to access the wan from within lan and never thought about the firewall accepting it as I was testing from inside. Question 2: I was trying to see my sites behind opt1 from LAN and got the NAT reflection issue. Stress sometimes work for you, sometimes against! Thanks and sorry for wasting your time! Ozz.

@Paul47: I was just wondering about the construction, "/dev/ufs/pfsense0". I'm unfamiliar with that. I was expecting something like "/dev/da0s1a", that's all. It's a GEOM label, so we can refer to the slice by name instead of by its physical designation. So we don't have to worry about the disk driver/device name at all, we use our own label for the filesystem. @Paul47: I know about the read-only business in nanobsd, except for a couple details: I'm guessing a restore operation automatically mounts the cf partition rw? It had to have, otherwise my restore wouldn't have worked. I'm a little shakey on where the gui automatically mounts it rw, and where I have to do it manually. I will dig into that some more. It handles that automatically for changes made in the GUI. If you want to manually make changes at the shell or over scp, etc, then you'll need to switch it manually. @Paul47: As to clicking on the logo, that makes little sense. What's wrong with a nice, obvious "cancel" button? Then people don't have to field so many newbie questions in the forum.  :) I added some text to the wizard to state that clicking the logo gets out of it.

@stephenw10: @Nachtfalke: Perhaps they are updating all sites and mirros for pfsense 2.0.3 !? Positive thinking. Nice. ;) Steve pfsense.org and packages are up again but no pfsense 2.0.3  ;)

@Wamba: Thank you Sir! Toggling with hard drive options in BIOS solved the problem! I ran into the same issue last night after a mobo/cpu/ram upgrade.  I had to change hard drive access from AHCI to IDE to allow installation. Switching back to AHCI after install causes pfSense not to boot.

There's this: http://doc.pfsense.org/index.php/Automatically_Restore_During_Install Not completely unattended though. Steve