Maybe this might help? Just one of hundreds of how-to's and videos on this particular topic. Https://www.youtube.com/watch?v=pW99TOu6Hes

Try checking your card against the HCL here: https://www.freebsd.org/releases/10.1R/hardware.html

it is better to run dhcp on your AD, since it helps in the registration of clients in dns.. Or can be setup too, etc. To be honest if your running AD, use pfsense as its primary function routing/firewall..  Stuff like dns and dhcp, ntp are all just bells and whistles for a site that doesn't already have those things taken care of.  If your running AD, that is where those features should be setup. And yes you need to make sure your AD is setup with good time source, pfsense could be that sure.  But your going to want to let your AD members sync to AD - once you have setup AD correctly, etc.. You can setup your AD dns to forward to pfsense, but all clients in AD should really point to AD for dns.. Then your AD either forwards or resolves stuff that it is non authoritative for, like pfsense.org, google.com

I couldn't find anywhere else to get an answer to this, but you are doing what I'm curious to try. I would like to know if two Intel SSD's (the support TRIM) are able to be used in the softraid 1 (The option the pfsense installer gives) with TRIM enabled? It seems as though TRIM gives them longer life, and RAID firther extends system uptime. I wouldn't want to throw dual SSD's in a system only to find that TRIM can't be enabled and they would have shorter lifespans that a single one! Thanks for any heads up or help you guys can give.

D'oheth!

@robi: Go into Diagnostics: NanoBSD options and tick "Keep media mounted read/write at all times." Thanks, this fixed it… now its at normal speed :)

I didn't know about the "m" in top, thanks! Same for me, seems like it's apinger. Strenge as aping.conf tells it should store things  in file "/var/run/apinger.status" (in RAM for me!)

@johnpoz: Apinger is terrible.. Browse the threads you will find thread after thread after thread asking when apinger can be fixed/replaced..  Which seems to be hopeful for 2.3 2.3-BETA has switched to dpinger.

@pfsensed: @Nullity: @pfsensed: @Nullity: Run Wireshark to get a better idea of what is happening? Is that wise given that I already can't handle setting up the SG-2220? :) That is precisely why I chose to mention Wireshark rather than tcpdump. :) You can't cause many problems by simply monitoring the traffic. Anyway, I am a Wireshark noob myself, but the GUI literally displays erroneous packets in red or black. If there is an obvious problem, it should be … well, obvious. Look for things like duplicates, errors, strange IPs. The GUI is reasonably intuitive to newbies. Just download it, open it, select your NIC and go. Edit: I mean run Wireshark on your PC, not pfSense. I solved the problem. I disabled several browser add-ons, reset the SG, power cycled my modem and SG, then went through the configuration again, and this time it worked. I believe the culprit was NoScript interfereing with the initial configuration, as some fields which were present before are totally gone now. Now I may go install Wireshark anyway :) Congrats! I prefer the CLI of tcpdump myself. GUIs are infinitely confusing. Wireshark, or any packet sniffer, is great as a teaching aid to understand computer networking.

Well, I did confirm the unit is booting as I was able to pull and IP and log in to the web UI.  I also confirmed that the serial settings are set to 115200 but my console doesn't advance past the screen in my previous post. I've also tried different emulator software too. Any input is appreciated.

Looking at the source code for the 9287 driver, I've noticed this: /* Don't support Kiwi < 1.2; those are pre-release chips */ if (! AR_SREV_KIWI_12_OR_LATER(ah)) { ath_hal_printf(ah, "[ath]: Kiwi < 1.2 is not supported\n"); ecode = HAL_EIO; goto bad; } Looks like I probably go a device manufactured from non-production components (possibly even sample devices). :( Also Kiwi seems to just refer to the family name of the device, i.e. much like celeron, pentium, etc. Hope this helps someone else. -Wynand

!!!!Need more info or screen shots!!

After installing the version 2.2.6 the problem has gone! Thank you for the great product! Happy new year, yarick123

I have tested both again, in both combinations, now instead of using CF cards, I'm using equal SSDs, Kingston S200/30GB. No changes in the results. Both devices present higher temperature and lower performance on 64 bit, than on 32 bit.

Note that in 2.3 the factory defaults processing will automagically select from a range of physical interface combinations when first booting, avoiding the need to do interface assignment on the console for hardware like Alix, APU and SG-series devices… https://github.com/pfsense/pfsense/commit/b49e6c0113f107f5a9ff61fe8e8798de8cca0953 That should be working now in 2.3-ALPHA images.

^ that. Try a different serial speed (like 9600)

Just a FYI. I was trying to connect using one of my failover IPs on my dedi server from online.net. anyway, I manage to get it sorted. I knew what to do (almost)  I had to add a route, but didnt realise that the last bit was important, I kept trying dev eth0  when I should have been using -iface em0  once I added the route correctly, pfsense connected to internet. Thank you for providing this software.. Once my testing is done, If I keep pfsense, I`ll think about getting a gold sub. Del