@Knight: ….it so it took me quite a while to have a working system again...). What should take time : Ones its up, you create a backup 'disk' (CD, USB stick, etc) so when your principal media dies (SSH, Hard disk etc) you can reboot 'in a snap'. Ones in a while, when you're up and running, and you modify your pfSense config, store it also in a save place - better yet : write it to your backup media …. ;) You do can all this while "all is good and you have plenty of time". Btw : you should only do this if the "internet access" is important for you. I do understand you have other things to do (as we all)  ;D Now, the update day arrives. Now, you are ready ! Without even thinking, you hit that upgrade button. If things go downhill afterwards, well, you reboot from your backup media ..... and you're up. I assure you that you have a workable solution in 5 minutes, whatever the outcome will be : new version, or boot to old version. Added to that : something I don't do - but, which I should do : I'm running pfSense a a vanilla ancient Dell Office Desktop PC" (stripped down - I removed everything not needed on a firewall. What I should do : every time pfSense includes a new freeBSD kernel (meaning : new drivers etc) I install FIRST the original new FreeBSD OS. If that goes well, I'll have a pretty good that pfSense works also. Easier will be : run pfSense on pfSense certified machines .....

Well, that's a very obscure description of the problem, offering virtually no information to let anyone help you. I can tell you that when I upgraded from 2.2 to 2.3 I did encounter a problem with /var/log filling and causing the system to be unbootable, there were also a few corrupted files, not sure of the cause. I ended up reinstalling. Maybe this will help, if not try to provide more relevant information.

I finally found the option to make it work  :D. I configured the virtual IP as "Proxy Arp" and not "Ip Alias "

In this case it would be worth to try changing/cloning the MAC.

Cisco firmware 1.4.5.02 loaded. Was not sure the update was cumulative so I flash all the incremental updates. Did not find a more recent boot version than 1.3.5.06 so I guess it is up to date. I did try vlan in trunk mode with the move to General step and apply. No change in results. Finally, I turned off globally STP and all the Discovery options. Success! I will go back and play with the settings at the interface level to determine exactly what needs to be turned off. Thank you for your help.

@Pimmetje: Seems correct to me. I configured and everything works as expected, Thank you so much man!

It copies the bulk of the data at that point without moving the progress bar much. With a slow disk, and/or slow source medium, it'll take some time.

@fastfire: Hi guys, I have a server with a Realtek 3 port network adapter (http://atacom.com/program/print_ipc_spec.cgi?Item_code=IMDB_JETA_1N_3R). This adapter work correctly in 2.1 pfSense Release, but it is not recognized in 2.3 pfSense Release. Support for this device was deliberately eliminated? pfsense server (32bit) with realtek ahahah is NOT a real server buy an intel nic card bye

Thanks, didn't realize it was a .gz file that was being downloaded Apparently Safari automatically converts .gz files before placing in the download folder.

Never thought to use VLAN tagging to segment the 1 NIC, I just bought an expresscard NIC and called it a day. So what does the physical topology look like?

Thanks for the response. Received the hardware yesterday evening (Korea) and installation was effortless like I had hoped. Went ahead and omitted the mSATA installation, since I don't have any real requirements for it at this time. Everything functions fine, and maybe it's just me, but network throughput seems to be a bit better, too :) Now to expand my horizons and create a VLAN soley for the VPN Client, and have segregated wireless networks on the Unifi AP; one for VPN and one for Clearnet. :D

Ah yes your right, i 'read' 2.3.1 if kulpreet is still on 2.3.0_1 that explains it. @kulpreet , can you confirm that 2.3_1 is the version your running and not 2.3.1 ? Upgrading pfsense and/or deleting old files as mentioned above should fix this issue. If your still having trouble getting it to run let us know :).

I see things are starting to go on track again. :) Thanks for the hard work!

@PiBa: Hi Dennis, Any particular reason why haproxy failed for your ocsp requirements.? If your willing to try again, or can explain me how to reproduce the issue in a few steps please contact me on irc or open another thread for the haproxy issue. Thanks, PiBa-NL Sorry for my late response. I will try it again with haproxy somewhere in the coming weeks and will post the results here.

Gonna bump this one and ask, would it be worth a bounty and would anyone, with knowledge of the task, be interested?!?!  :-\

If you close the window at that point, it does not continue.

@ricle: If nano dies i have to shredder my alix? Or is there a way to use a usb stick? You can keep running whatever the last release is that has NanoBSD. Current plan is to keep maintaining that branch for a while. IIRC when we drop NanoBSD, i386 is also being dropped, so either way the ALIX can't move forward. It's past time to be seeking a replacement for that hardware, it's been EOL for some time now.

Odds are it isn't hanging on that but with whatever is happening next. What is next there depends on your hardware. Could be CPU/Power related, could be clock-related, etc. It's definitely still initializing the hardware though. There should be an option for a verbose boot at the first boot menu that comes up. Activate it and see if anything more useful is printed.

Check the system log before you reboot. From the sound of it, it's rejecting something in the configuration and going back to what it believes is the last valid one. Also check the config history in the GUI (Diag > Backup/Restore, Config History tab) and see what it shows happening. Either the configuration change is not being written, or it's being rolled back.