If I had to guess then your CF card is not too happy: /dev/ufs/pfsense0: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) /dev/ufs/pfsense0: SUMMARY INFORMATION BAD (SALVAGED) /dev/ufs/pfsense0: BLK(S) MISSING IN BIT MAPS (SALVAGED) /dev/ufs/pfsense0: 15885 files, 873983 used, 2906045 free (2597 frags, 362931 blocks, 0.1% fragmentation) /dev/ufs/cf: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ufs/cf: clean, 99618 free (42 frags, 12447 blocks, 0.0% fragmentation) Warning: file_get_contents(/etc/version): failed to open stream: No such file or directory in /etc/inc/globals.inc on line 88 pfSense  on the 'nanobsd' platform… Try another one - they are pretty cheap - or run a thorough test on the current one on another machine and try again.

It worked!! Last thing i could see before seeing it crashing was something about not being able to lock on a database. Anyway its up and running now Thank you very much

Funny ??? I just try to run a new install from a USB with a fresh download (pfSense-CE-2.3.2-RELEASE-amd64.iso & pfSense-CE-2.3.2-RELEASE-i386.iso) both .ISO file's are not bootable as rufus said. Even burned one of the ISO's to a CD-R and it booted but a few mins in at "Trying to mount root /cd9660/dev/iso9660/PFSENSE [ro]…" it spits out preparing crash dump and reboots. I used this doc to see if I was doing anything wrong: https://doc.pfsense.org/index.php/Installing_pfSense Even looked over this one as well!!! https://oitibs.com/pfsense-usb-install-guide-rufus/ :o I have been booting .ISO's & running PF for yrs now and I feel like a nub [image: Screenshot_158.png] [image: Screenshot_158.png_thumb] [image: Screenshot_159.png] [image: Screenshot_159.png_thumb] [image: 20161112_211942.jpg] [image: 20161112_211942.jpg_thumb]

@Numenor: @johnpoz: "6. I then went to Bridge tab and bridged them with the LAN interface." Huh???  Your wanting to use these as switch ports???  That is NOT a good idea at all… If you need switch ports, go get a switch!  Get one that supports vlans is what I would suggest if you want to start putting your stuff on vm and running a more complicated type of network.  Vlan supported switch will allow you to segment your network for control and security.  As to your wifi I would suggest you get a real AP vs some card your going to install in your VM host and then try to pass through to a vm?? Dude if you want to run VMs on hardware.. Why would you not run esxi or actual hyper-v version of windows vs just the hyper-v that is included in the windows 10?  Or any of the other hypervisors out there??  What you want is a VM host, then run type 1 not type 2. Hyper-V in Windows 10 does have type 1. [image: Gppf2CD.png] Also what you're saying makes no sense at all. How would getting switch help at all? When they would still require Ethernet ports to be hooked up to the PFSense box that is acting as a router. Network doesn't need anything fancy since its only meant to be a home network, it only has 3 computers that need Ethernet ports. It just needs wifi for a couple of phones, 1 laptop and a smart TV. Also the reason why I am running PFSense on a PC VM instead of ordinary router is because hardware upgrade ability, power efficiency since it would only require one device to running all the time, instead of multiple. Also your post really doesn't offer any real help. I just need the Ethernet ports from the PFSense box to give internet access to the devices that get plugged into it right now. Isn't that the whole point of PFSense? To act as a router? If you're telling me I should of just gotten ordinary wireless router, then what is the point of having PFSense at all? Type 1 and Type 2 hypervisor is not the same as Generation 1 and Generation 2 virtual machines which is a Hyper-V only.

thank you, bro!

The way I normally do it that works every time and makes sense from a networking perspective: WAN - Bridged (to your real LAN network) LAN - Custom: VMnet2 OPT1 - Custom: VMnet3 For your virtual LAN clients, make sure their NIC is also on Custom - VMnet2.  Your DMZ virtual servers go on Custom - VMnet3. Set pfSense WAN to get a DHCP address or set it manually.  Set LAN to some other private network space outside of your real LAN.  Enable DHCP on LAN and give it a range.  Your virtual LAN clients should have no trouble getting to the WebGUI. [image: vmw.png] [image: vmw.png_thumb]

Bug reported: https://redmine.pfsense.org/issues/6904

I'm just that good  ;D

If you have the same config (or at least the same starting point) on the same hardware just connect to 192.168.1.1 and upload the config. Done.

Sure, provided you can predict their MAC addresses. You can do it in one of two ways: 1. Use static mappings for all of the different ones and set the option there 2. Create a second pool with the setting you want, and use the MAC address allow/deny controls to influence who pulls from a specific pool. Deny them from the main pool and allow them in the second pool.

Gave up and rebuilt it in the end. Then restored my config from backup. Whole process took 30 mins after my CF card reader arrived.

@jejethx: We have Pfsense 2.0.3 with HAVP + Squid + SquidGuard. I'd start with upgrading your PFS version.

I'm not quite sure what you're trying to do.  The current squid package is 3.5.19.  You want to "upgrade" to 3.5.3?

That is good to hear.  Now I just need to reinstall pfSense and I'll give that a go. Thank you all for your comments and suggestions!!

For anyone coming by this post later, it seems the MBUFS 'issue' is related to certain hardware setups.  I was initially surprised as the VM PF Servers I have don't have this high usage with the default settings. Anyway, I found the following pfsense documentation which explains this and what related settings to check: http://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards Cheers,

Still failing.  The web configurator still says that 2.3.2p1 is available but the system will not update. In the option 13 console the last lines say: All respositories are up-to-date pkg:  Repository pfSense-core cannot be opened.  'pkg update' required pkg:  Repository pfSense cannot be opened.  'pkg update' required Checking for upgrades (0 candidates): . done Processing candidates (0 candidates): . done Checking integrity… done (0 conflicting) Your packages are up to date. So why is it failing? EDIT:  I was able to resolve by reimaging another USB drive and restoring config to it.

@chuchuchu: maybe the bug is truely a bug ? [image: 4000951125_6d2591948a_m.jpg] ;) LOL

@NOYB: No idea.  Not my call.  If it were they would already be there.  As you can see by their age, they are not getting the attention we think they deserve. Just ran across this.  (It's been a week already, and it's only Weds.) I'll talk to jdillard about them.

its more then likely a bios setting of some sort. Have you tried resetting it to factory defaults?

Funny you should write that … Again, just did a box reset to default, then dropped the DHCP to use Static on the 192.168.x.x default Verified PC static at .1.16 via the ARP table ... that worked ... Then switched over to 172.28.1.1 LAN ... and static 172.28.1.16 PC It worked ... and ARP table agrees. Must have been my 501st try ;-) Thanks for the use of your magic wand.