@deajan: Hello, as you're using a CF card, you have a NanoBSD setup which won't be of great use if you intend to use Squid or any other disk space hungry plugins. The best advice I can think of is to make a clean install and restore the config file from the NanoBSD install, and then reinstall the packages. Yeah I decided to do that, moving files would most likely cause major issues in the future. Thank you!

Thanks for the advice, I know linux can't deal with GEOM and slices as in FreeBSD. The funny part is that CloneZilla is supposed to deal with FreeBSD partition scheme, but can't handle pfSense's one. Anyway, this was my quick and (really) dirty solution to handle my problem in a couple of hours.

@shaharhd: I followed this: https://www.netgate.com/docs/rcc-ve-2440/pfsense.html You're fine. The bits weren't technically all wiped from the drive, but your reinstalled OS can't read any of them that remain.

figured out: https://www.netgate.com/docs/rcc-ve-2440/pfsense.html

thanks Divsys the disk usage command screamed that /var/log was the culprit consuming all the free disk space. I will dig deeper and rotate the logs…after Easter. My intention is to move the /var dir to the separate free space partition on the internal mSATA drive. There's plenty of disk space there so why not!? have a great Easter everyone.  ;D

FIXED! Yea….motherboard was same... ;D I took out the PCIe card and ran the live cd again. This time only showed the one PCIe (re0). Thanks for your quick help!

You will probably need a managed switch to do this with one physical interface. I don't get it though. With only one NIC how are you connecting both the AP and the modem?

The packages should reinstall but will take more time. System > Tunables will migrate in the config. You'll want to manually copy loader.conf to the new system. Restoring a full backup and restoring a config file to a new install are two different things.

You can't put the same IP subnet on multiple interfaces.

My gut tells me both technologies have improved (and continue, I'm waiting for Nantero to reveal a commercial version of their product - exciting possibilites). Any rough analysis will tell you a USB stick will never outperform/outlast a SSD if their from the same generation. The SSD is supposed to be hard drive storage for laptops/desktops/servers, etc. The USB stick is supposed to be convenient storage you can carry around and plug into various things. There's lots of overlap in their design criteria, but there's differences in their intended usage which makes SSD what you want for a pfSense box.

That's not what he's asking for. DNS running on the second pfSense interface (OPT1) doesn't matter because it will only do anything if the hosts on that subnet have it configured as their DNS server. Just don't do that. You could, in fact, set your hosts to use the DCs for DNS then have the DCs forward to pfSense for actual Internet DNS resolution. When you create an OPT1 interface a DHCP server is not created automatically so there will be no DHCP server so no problem. If you want to just use LAN that was automatically created, got to Services > DHCP Server and disable it. Configure your DC DHCP server to give your AD clients the addresses of your DCs for DNS. Neither has anything to do with whether you have internet access or not, other than without good DHCP and DNS, which should be provided by the DCs, the internet won't work.

I just upgraded a pfSense 2.0 install to pfSense 2.2.x and I'm seeing the same issue. My real gateway is not listed under RRD Quality instead I see an entry called WAN_DHCP without any stats at all. I've never used DCHP for the WAN connection on this setup so this puzzles me a bit. I'll report back if I manage to figure out a workaround or fix. Edit: Turns out my gateway had the "Disable Gateway Monitoring" option checked, when I removed it the real gateway showed up in the list above the RRD graph.

To me the one untagged isn't really a virtual though.  It's "native" (for lack of better term) or real, or physical, etc. and requires no vlan technology, capability or processing.

Thank you to all, for the consensus reply. VLAN's it is then. Kind regards, jB  8)

Choose the custom install option and define a / partition that's smaller than 64 GB (probably put the rest on /usr/).

nah about to look over it , been setting up alot , but AP it is :) thanks guys

Not sure why the Realtek NIC isn't working. You want to assign static IPs to the internal interfaces - ie LAN and OPT1 (when the Realtek NIC starts functioning) - and let pfSense act as the DHCP and DNS server for your network. The configuration of the WAN will most likely be DHCP or PPP depending on your ISP requirements. pfSense defaults setup upon installation is as per https://doc.pfsense.org/index.php/Installing_pfSense#pfSense_Default_Configuration. By default pfSense blocks any traffic on OPT1 so LAN will be able to communicate to devices on OPT1, but OPT1 won't be able to communicate with LAN or WAN. Firewall rules will need to be added to OPT1 to enable this. The Unifi AP doesn't need a static IP as it will work with DHCP, however for ease of use I would assign it a static IP through DHCP as a minimum. If you have a device running the Unifi Controller software then you will need to setup the DNS CNAME "unifi" for the device to assist the AP in finding the controller (see https://help.ubnt.com/hc/en-us/articles/204909754-UniFi-Layer-3-methods-for-UAP-adoption-and-management) Option 1 - You have a switch between pfSense and your AP With the Unifi AP, if you are just going to have a single WLAN SSID then it can be plugged into your switch connected to the LAN interface. If you want to have multiple WLAN SSIDs that are on separate subnets (for example a private LAN and isolated from a GUEST network) then you will need to either use a managed switch or get the Realtek NIC functioning. You will need to setup VLANs on LAN NIC and managed switch (if using a managed switch) or plug the AP into the OPT1 NIC and setup VLANs on OPT1. The WLANs will also need to be assigned a corresponding VLAN. The management VLAN for the AP will need to be untagged in both cases. Option 2 - You have no switch and your AP connects directly to pfSense You will need to have a computer connected to the AP via a wired link first to configure the WLANs and settings with the controller software. Once it is setup connect the AP directly to the LAN interface. If you have a single WLAN SSID then it should all work. If you want to have multiple WLAN SSID subnets then you will need to setup VLANs on the LAN NIC and assign VLANs on the AP WLANs. The management VLAN for the AP will need to be untagged.

have a look here: http://timita.org/wordpress/2011/08/01/protect-windows-with-pfsense-and-virtualbox-part-4-installing-and-configuring-pfsense-on-virtualbox/ http://pc-addicts.com/how-to-install-pfsense-in-virtualbox/