@jack290: As a linux user,  the way I've got round this is to connect the SSD into a linux system and partition the disk using the linux fdisk. I found that when installing, the PFS installer gets upset if the partitions are not aligned on what it thinks is a cylinder boundary,  and I find the way round this is to choose sectors which align with both 63 (the old cylinder system) and also 4K boundaries.  This requires a little use of a calculator.  There is usually plenty of room on an SSD, hence I align to 63 x 4096 boundaries, ie 258048. Typically, start 4644864  ( 18 x 258048)  finish 30965759 ( (120 x 258048) -1 )  is 26320896 sectors, 12.5Gb Mark the partition as bootable and set a free BSD type (a5).  More partitions can be created by the same method.  The partition marked bootable must be used. Put the disk in the PFS box and install. When installing, choose own partitioning, pick this partition, do not format then install the bootblocks (bootloader) and complete the install. EDIT -  BSD calls partitions slices.  The above should read  "do not slice the disk, pick the slice (partition) you created."  I'm working from memory so I hope there is enough here for you to get started. The above is a somewhat blunt approach which works for me because I am familiar with the linux version of fdisk.  It is not much help if you do not have an available linux box to use.    Someone else may offer a better solution,  if you are familiar with the BSD version of fdisk it should be possible to boot the installer to a command line,  fire up the BSD partitioner and then use the approach given above to set the partition start and end points.  ( I'm not familiar with the BSD  version of fdisk and it may insist on cylinder boundaries,  however a little use of a calculator should still allow the problem to be solved.) There are differing views on whether or not to set trim, if you want to do so, after installing, boot to a command prompt at the first menu and run:-     /sbin/tunefs -p /    and      /sbin/tunefs -t enable / to enable trim. Hope some of this helps,  and I might add that 4k is also preferred for many modern spinner disks which use "advanced format". I just do a 16MiB alignment. No thinking involved then and only wastes a minuscule amount of space.

Version upgrades such as 2.3.2 to 2.3.3 are not going to be done with 'pkg update; pkg upgrade' as far as I know because pkg doesn't quite know how to update its own repository configurations. The pkg updates are for minor updates, security fixes etc.

No, you should be getting the compressed file as it is. It's probably your browser that is uncompressing the file for you. Try with another browser.

Double check IPs & subnet masks Sounds like these are Windows systems - Temporarily disable firewall of target to see if that is where you're getting blocked Check output of arp -a on both source and destination to see if there is a layer 2 issue

The problem should be in the state of the device (real terminal, terminal emulator, whatever) connected to the end of the serial cable, not in the Alix or the software on the CF card in the Alix. The Alix serial port will still be sending ASCII abcdef etc but the "selected font" on the display device has switched to "klingon mode" and displays these ASCII abcdef as the line-drawing shapes. I can remember actually coding stuff like this to make tables/cells with borders on VT terminals!

@phil.davis: Someone else had a similar problem and updated their I350 to the latest flash - read and try: https://forum.pfsense.org/index.php?topic=86065.0 Yes, I went through all those hoops, the fatal error 12 etc and have updated my Intel NIC to the latest F/W as mentioned in the original post. I can even see the NIC in the WebGUI or in the PFSense VGA terminal. But on assigning WAN or LAN to it, the device just doesn't work.

I can't remember why I created the Bridge anymore, I followed a tutorial a year ago. I plugged in my Laptop into OPT1 directly, LAN got an IP via DHCP instantly. I now connected Gargoyle LAN4 to OPT1 but WiFi client doesn't get an IP. So something on the Gargoyle is blocking DHCP I assume? EDIT: I SSH into my Gargoyle Router (Archer C7), manually disabled and stopped the Firewall (/etc/init.d/firewall disable and /etc/init.d/firewall stop) and rebooted it and now the Wifi clients get IPs issued. Maybe the GUI didn't apply some firewall config properly. I'll do some more testing and firewall rules now…

@mikej2007: I just wanted to leave this here for those who are setting up a Linux Terminal Server Project (LTSP) server.  If you follow LTSP install notes, they assume you are using the LTSP server as the DHCP server as well.  In my environment, my pfSense machine is already doing DHCP, so I wanted to configure it to handle PXE booting. Here is what I did using: pfSense 2.1.3-RELEASE (i386) FreeBSD 8.3-RELEASE-p16 From the drop down menu select Services > DHCP server Click LAN tab Click TFTP server “Advanced” button TFTP Server: (I entered the IP address of my LTSP server) 192.168.1.100 Click Enable network booting “Advanced” button Enable network booting checkbox  (make sure the box is checked) IP address of next server: (I entered the IP address of my LTSP server) 192.168.1.100 filename: ltsp/i386/pxelinux.0 Enter the root-path-string: /opt/ltsp/i386 Hi, doesnt installing LTSP require DHCP server to be installed too & configured? would be helpful if you can let me know how you did that?

You need another network interface for LAN. All that is detected is em0.

Thanks for taking the time to update your posts. Welcome to pfSense, and enjoy  ;)

Thanks found it  :)

Look here for the information about 32-bit i386 and nanoBSD not happening for 2.4: https://forum.pfsense.org/index.php?topic=121255.0

That's a bit tricky ;) A default install on any sort of hardware with "common" network device names ("igb0", "vr0" etc) should pick 2 interfaces to be WAN (DHCP client) and LAN (192.168.1.1 with DHCP server enabled). So you can physically plug in to each network port until you find the one that is being LAN. That will let you get to the webGUI and either assign interfaces using the webGUI or enable SSH and login to a text session an use the console menu.

Yeah just click the little button next to their lease to create the static/reservation for their mac to always get that IP.  go to the bottom of the dhcp server and add it..

I don't suggest a version. Don't know your setup, needs, … nothing from you.

A note for future readers of this thread: replace the old em1 with ibg0 when doing a search/replace in your favorite text editor, always be careful to look and think about where it finds "em1". Quite often it happens that a string like "em1" happens to appear in some randomly-generated long key (e.g. in the OpenVPN section or…), so you do not want to mindlessly/accidentally replace those.

misconfigured… I found the culprit: when I said that I had deleted the bridge, it turned out I had not! pfsense was running with a Bridge between LAN/DMZ with DHCP on both. Not what I intended or wanted. I had deleted the 'Interface Group' instead of the Bridge! I'm not even sure what it is or how to use that. Now that the Bridge is really gone, all appears normal.