That's a driver issue that we just imported a fix for into 2.3 today. Needs more testing still, but seems to be fixed now.

Hello BlueKobold, I just solved my problem and I finally install pfSense, thank you for your interest. Like many others but since the USB installation will work flawless smooth and liquid there is often no really need to use a CD/DVD device anymore. So you could get a USB pen drive and then push there on the amd64 version of pfSense there are pre-defined USB pen drive images to do so and then install from there. I agree with you with respect to the USB ports but i disable by recommendations in the Boot Troubleshooting (hardware conflict). It could be that there are some quirks with the BIOS or some BIOS settings with this device. How many RAM and what CPU is in that device? How many and what kind of LAN Ports (NICs) are inside of this server? My server has 5 GB of RAM and an Intel Xeon CPU 3.20GHz processor by default brings only 1 network port but bought a Hp Nc360t Dual Port Pci-e X4 Gigabit Server Adapter 412651-0 (with 2 networks ports) to have a total of 3 network ports. Here are the settings that work for me: USB ports disabled. Serial port disabled. Parallel port disabled. Integrated lights-out disabled. (Also called port ILO). Floppy disabled. Integrated SCSI ports disable (u320 HBA Port1 and u320 HBA Port2). I use the latest version of pfsense 2.2.6 64-bit architecture. NOTE: The integrated SCSI ports they are not using because it had all the hard drives are connected to the PCI RAID controller. I hope will be helpful to many here in the community. ;)

Backup the config.xml file and a full system backup will be not the same as I see it right. Do a system backup and a config backup and then do a fresh and full install of the pfSense using the same version as you are using now! Then restore the backup and config. backup to the new installation.

It's a compatible machine in theory. What you see on occasion is hardware quirks that other OSes might not trigger, or might have workarounds for, where other OSes may not. You can run all the time from a USB flash drive, just choose the nanobsd version, and write that out to the USB flash drive. Boot and run from that.

ended up using a Perc5 controller instead of the 6..  works ok now

What version of pfSense?  FreeBSD did not start to get ability to UEFI boot until the 10.x series, and depending on what your configuration is, may need a bit of hand effort. Version of pfSense, hardware, boot disk would be useful information for people to help you

Hi Your HP 4-port 331FLR Adapter is most certain not realy "the same", as the meintioned adapters … Apperantly, there were compatibility-issues with this card, have a look here (middle): https://forum.pfsense.org/index.php?topic=79032.0 Regards Walbog

Please do not start multiple threads on the same topic your original post is still active.

Ok got it sorted Changed the gateway on under firewall rules and it worked

FYI- The problems with the 525-B units on FreeBSD 10 appear to be limited to the CF socket. I ran a few quick tests here with a SATA disk and with an mSATA disk and it was fine one both. Though there are plenty of reasons to replace it ASAP (it's a space heater, among other problems), that may be a way to squeeze some more use out of it. The underside of the access panel on the bottom has a mount for a 2.5" SATA disk, and at least mine has a cable inside already with SATA power+data on one connector. mSATA will work in the mini-PCIe socket that is directly across from the CF socket. [image: Gr3Zzs5l.jpg] The socket for mSATA is circled in blue on the image above. The SATA cable is circled in orange. CF socket is in red. I didn't run from it long term but I imagine it would also run fine from a USB thumb drive.

I've installed FreeBSD since 3.3 from CD/DVD and have not experienced anything like you are saying.  This is from media purchased from BSDMall and ISOs I've downloaded and burnt myself on different platforms. If you used the same media on all 3 systems, perhaps that is the source of your problems.  The boot delay?  Perhaps due to BIOS/firmware probing of the hardware and the drive itself is taking a long time to respond. This is FreeBSD installs, not pfSense installs.

A Google search shows people seem to have been able to run pfSense with these boxes, so I'd look for some change from the "ordinary?" Check for BIOS versions/upgrade?

Update - So I'm not sure what the root issue was, however I decided to upgrade to the latest version. My network is fairly simple so reconfiguring is not difficult at all. I created a memstick image and nuked the installation and started fresh. Worked right out of the box. I added a few tweaks, like not letting my router serve 192.168.0.1-254, I limited it to a handful of IPs, etc. So, now I have a clean install thats working, and I have reinstalled my packages. Next step, once I have time, is to configure it for PPPoE and get my Zyxel into bridge mode. I've searched quite a bit on the topic, but if anyone has any experience with that particular dsl modem/router and pfsense, any suggestions would be great. Thanks!

That all got reworked for 2.3, so hopefully less confusing now. On 2.2.x, when the box is checked, states will not be killed.

If you purchased two appliances, they likely come with support.  Contact ESF and get their recommended procedure.

Yeah it seems like your old hardware used a different baudrate then your new SG-2440. What is actually configured? It should be set to 115200. https://doc.pfsense.org/index.php/Console_Types