…so what have you done "after the failed squid install" - have you removed the package, reinstalled the package, removed it and tried a different version of it, restarted the pfSense, etc... What version of pfSense are you running? Which squid did you try to install? What sort of failure messages did you get? When all else fails, a configuration backup and pfSense reinstall from scratch followed by a configuration restore solve a lot of fiddly issues, often faster than hunting them down. If you had squid 2 and tried to install squid 3, that's an "expected to fail" arrangement unless you remove squid 2 first.

Yeah that whole thread is quite interesting including the links in it to various other forums. It looks like it is possible to get that board working it's just a PITA! Hopefully a bios update can sort it. Until then this post looks most promising: https://forum.pfsense.org/index.php?topic=73518.msg418094#msg418094 Steve Edit: I see Gigabyte have now released their F3 BIOS which is reported to be much better. http://www.gigabyte.com/products/product-page.aspx?pid=4918#bios

@jimp: More like 2.3, not 2.2.x :'( Anyway, thanks!

@fusion88: and with the 2 nic ports.. have the adsl modem in bridge mode going to the port assigned as wan… and then just buy a 8 port 1gbe unmanaged switch to connect all my computers.. im then faced with what to do about getting wifi working? i just hope i dont have the same issue as above when i do install it on a vm ... Normal 'best practice' is to have your ISP modem (cable or asdl) as a single function device, with only a single connection from there to your pfSense machine (or VM) WAN port.  If you use a combo unit, turn off the wireless part of it, and don't use any of the other LAN ports.  And as Steve said, double-check that the modem is in bridge mode, you should see a public IP. For wireless, it's easiest to use a wireless access point, just turn off it's DHCP server and plug it into your LAN switch.  And if you are buying a switch, you really should consider getting a managed switch capable of VLANs.

The biggest update for 2.1 was the vast amount of work that went in to get IPv6 functioning. It wasn't the only thing though: https://doc.pfsense.org/index.php/2.1_New_Features_and_Changes More has gone in since for 2.1.1, 2.1.2 and 2.1.3. Steve

Everything's been running smooth. Marked the subject as solved. Thanks again!

Thank-you stephen

You can install to a USB 3.0 drive. What you cannot do is use a USB 3.0 port.

Nahh. I think the IBM server i have is strong to have everything on him. Also i dont need HAVP cose ClamAV is integrated to Dansguardian already.

How do you have the pfSense WAN configured? The WAN and LAN interfaces must be in different subnets. If the modem is successfully in bridge mode then the WAN will get a public IP which is a different subnet to LAN. Before that though the modem ip is in the LAN subnet which cannot work. Steve

Thanks. Had to download the latest 64bit version and upload it manually as it doesn't recognise the version difference. But after a hard reset, a lot of sweating as it went through a disk check, it came back up all good.

Yes, fixed. I suspect a package installer was to blame. We have Squid and SquidGuard installed. I had originally named the script that was getting deleted '/usr/local/etc/rc.d/squidguard_setup.sh'. When I renamed it to '/usr/local/etc/rc.d/blacklist.sh', it survived upgrades. I suspect either the Squid or SquidGuard package installer is doing something like 'rm /usr/local/etc/rc.d/squid*'. Thanks for the help, everyone.

Thanks for the help guys. Bridging the interfaces is exactly what I needed. I was able to route traffic with no problem and have all of my rules setup as I wanted them. We can close this topic now

Ok, found it on another thread: remove network cables before install.

For / on the Hamakua, I believe so, due to its BIOS limitation as far as I remember. You can try a larger size, but it may not work.

Personally I would choose ESX. TO me it seems more stable and compatible than the rest.

Using Pc engines APU1C with latest bios Pfsense 2.1.2 x64 full install edition on a 20 GB USB 5400 rpm spinning HDD My boss ran the install script from webgui over the weekend to 2.1.3 and now it cannot find it's kernel. Running squid, lightsquid  and openvpn Thank god he didn't try it on the other one, 5 hours drive away in Toronto…  :-[ Any idea when the gold stars are going to be added to the forum? ** Edit This was caused by not enough space. The pfsense partition I'm using is just over 4 GB since it was originally dd'd from a SD card. I restored to a HDD image from last week and then I deleted the squid cache tree ( rm -rfv /var/squid/cache/* ) Then I invoking the upgrade script and it completed without issue.