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/

@robi:

@Derelict:

Mixing tagged and untagged traffic on one interface can be problematic. Vendors do it differently. Just tag it all and it'll work.

On TP-Link switches, it is possible to have tagged and untagged traffic on the same interface, and it works flawlessly also with pfSense like that.
I'm using dozens of UniFi wireless hotspots on each site with TP-Link switches, which require to have their management network untagged, and wireless networks tagged on the same interface.

Hi Derelic,

I've always used it as you described, untagged LAN network, additional tagged networks and the switch in LAGG with trunked ports.

However, since i've upgraded it stopped working for my LAG, i've now decided to buy a new switch to see what it does, i'll keep you guys posted.

I ended up figuring it out.  Thank goodness for pfSense making periodic backups of it's config file.

1. Boot into single user mode (during boot, hit 'S' at the pfSense menu)
2. Hit enter when it asks for shell /bin/sh
3. Mount filesystem Read\Write: /sbin/mount -o rw /
4. Go to config folder: cd /conf
5. Rename broken config.xml: mv config.xml config.xml.bak
6. Go to config backup folder: cd backup
7. Find latest backup config: ls -la
8. Copy latest backup config to conf folder: cp config-<numbers>.xml ../config.xml
9. Reboot: /sbin/reboot</numbers>

Thanks @cmb.
All works correctly as it should.
It would be better to purge all blank entries from the config file to make it readable.
There can be a checkbox in the save config form to choose to save blank entries or not.
Safe defaults on being blank and being assumed blank when the config file is parsed would be in order.

@muswellhillbilly:

@tbaror:

i have succeeded install it but suddenly i get following below panic after rebooting.
The only thing i changed is to activated the ILO to be able remote configure

So did the device start correctly initially but then didn't when you activated ILO, or did it never start correctly? If it only started giving you problems after you installed PFS and then enabled ILO, then I would disable it and re-install. You can test this first by running PFS live from the CD before installing.

Hi

Issues solved , the source where sourcing  from ILO , firmware where version 2.10 upgraded to 2.30
Solved the issue
Thanks All

I am already at version 2.2.6  , after installing 2.1.1 version and configuring everything , i invoked the auto upgrade and pfsense auto upgraded itself to latest version .

this was an "old" mini itx board i had here , i choose this board because already came with 2 gigabit ethernet ports .

This board is a jetway NC-81-LF
http://www.jetwaycomputer.com/NC81.html

However , i will still change the case of this "firewall" , the current case in the pictures was just for testing and configuring it .

you do understand a switch with vlan support is very cheap these days..  You can get a 8 port gig switch with vlan support for <$40

http://www.amazon.com/TP-LINK-TL-SG108E-8-Port-Gigabit-Tag-Based/dp/B00K4DS5KU
$37

How has your performance been on these with 2.2.6?

Mine run out of memory often!

I am slowly replacing all my alix with homemade 2578

Thanks anyways guys, figured this out on my own. :)

This is just install and go.

Forget switches, etc. Plug your management host directly into LAN and set if for DHCP. It will get an address and be able to access the webgui at http://192.168.1.1/

If that doesn't happen you are probably not plugging into igb2.

Hi,

I can confirm this behaviour after doing a configuration restore on a fresh installed 2.2.6 system.
DHCP works fine, is churning out DHCP leases, logs correctly to the system log but dhcp leases page is not updated accordingly.

RESOLVED: Thank you for the heads up on the hash verification of the file. I downloaded it again, and redid the install. It finally worked!

One point at last from me to this on top, HP has mostly his own and custom version of ESXi to work
with their Servers well, perhaps you should have a look to this.

Your photo seems to indicate a SCSI drive failure, or possibly an issue with the SCSI controller. For my own part, I've avoided using Dell hardware with PFS as I had some nasty issues with Dells after upgrades. My personal feeling would be to use fresh hardware, but someone came up with a 'workaround' of sorts here:

https://forum.pfsense.org/index.php?topic=31907.0

@Ruddimaster:

Is there a chance to work around this issue?

Remove limiters, or disable pfsync.