@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 . [image: DSCF1940.jpg] [image: DSCF1942.jpg] 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.

Glad you got yourself up and running. Before you get too far down your current path, you might want consider just bypassing the whole "bridging NICS to simulate an internal switch" approach and just get a small switch. They're cheap (<$30) and will definitely perform better than multiple NICs. Save yourself grief in the future, plus you can keep those extra internal NIC's for the scenario(s) you may find later (want a "guest" only WiFI?, need to add some isolated machines? etc.) Just my $.02, but you'll find this general opinion echoed  alllllll over the forums  8)

That' doesn't keep you away from content which is inappropriate… in a church! It does if you use custom DNS that filters out bad stuff, like OpenDNS or Norton ConnectSafe.  Nothing is perfect, though.  If people are determined to use a church's network to find porn, they will eventually find porn.

Dont put a gateway address on your LAN. Can you post whats in your PPP logs here?  You might have to try and reconnect that way to get those.

I ended up spinning up a VM to see if i could get it to run on there and it booted fine, not really sure why it wouldnt run on my main system. Hopefully it will run right away when the rest of the hardware comes that i plan to run it on. Thanks for the help!

I resolved my problem by ordering a new nic