@mwagner: My password contain these characters: _£@;[{.#! [/quote] [image: password_strength.png] SCNR.

Great. Surprised that worked previously, the default limits generally much too low for 10G cards. The bce tunables usually aren't necessary unless you're seeing problems of some sort, but shouldn't hurt anything to set them.

Thanks for the reply. The SG-2440 uses the second serial port for console.  Is there a setting in the config file to specify the serial port?  I looked and didn't find it in the backup of my PC installation. Also, of more concern, what of the "optimizations" in the ADI image for the SG-2440?  Will I lose any of those or need to make changes after restoring the PC backup? Thanks, Frank

What about the 'Diagnostics\Factory Defaults' menu item?

When I auto-upgraded my APU from 2.2.2 to 2.2.3 I also had the device eventually hang and lockup requiring a hard reboot. Except when mine came back up I was getting a Kernel not found error. Using my original 2.0 thumb drive I was able to boot up a shell and get into /tmp/hdrescue and run: tar xzpf /tmp/hdrescue/kernels/kernel_SMP.gz –exclude loader.conf -C /tmp/hdrescue/boot/ The above command I found from this thread: https://forum.pfsense.org/index.php?topic=46725.0 I'm now able to boot back into 2.2.2 but most of my packages are hosed in an inconsistent state.  At least now I can grab some configs and kernel modules before doing a fresh 2.2.2 install.

Yep, but couldn't understand which process was the one doing I/O. I'm not a *nix expert… but the forum and the many "good news" rang a bell https://forum.pfsense.org/index.php?topic=95837.msg533449#msg533449 mount -o nosync / SOLVED! PS: now removed the "sync" option out of /etc/fstab and rebooted, looks ok.

The only reason to have a default gateway in the netgear is so the netgear device itself can route to the internet.  You might or might not be able to even set a default gateway on the LAN side of that device. The wireless clients should have the IP address of pfSense as their default gateway either from DHCP or static.  The Netgear simply bridges the wireless clients with the wired network.  The netgear/AP is not a layer 3 hop.  You are putting wireless and wired clients on the same segment.

You're redirecting it somewhere else. There are suggested workarounds to get in here: https://doc.pfsense.org/index.php/Locked_out_of_the_WebGUI

How do you know you have internet access?  I suppose you can ping IP addresses on the internet? Could be a DNS problem.  If you can load PFSense in your browser, then I don't see how this is a totally "browser" issue.  It seems odd that it would be a PFSense issue that not a single browser would display a web page for you.  Unless it's a rules problem… Can you ping by domain name?

If it works fine that was the issue then, your DNS doesn't like the pings! You can lower the number of pings or just use a different server to ping.

So, great, previous crash fixed, ran the "reinstall all packages" routine to test, but now I get this crash: Crash report begins.  Anonymous machine information: amd64 10.1-RELEASE-p13 FreeBSD 10.1-RELEASE-p13 #0 c77d1b2(releng/10.1)-dirty: Tue Jun 23 17:00:47 CDT 2015    root@pfs22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10 Crash report details: PHP Errors: [29-Jun-2015 12:35:33 Etc/UTC] PHP Fatal error:  require_once(): Failed opening required '/usr/local/pkg/shellcmd.inc' (include_path='.:/etc/inc:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg') in /etc/inc/filter.inc on line 3852 Another thing that would be useful: if version updates wouldn't mess with the crontab file: after each update I have to re-add the 'MAILTO=""' line in order not to get swamped with notification e-mails; even better if we'd get notifications e-mails when there are package and/or OS updates ready. But those are different issues…

Hello Guys, I have an emulex OCE11102-NT which works well on freebsd 10.1. I get the oce driver from there and add it to pfsense which see my two 10Gbe ports. However, I can't make any vlan working with. It works well on pfsense but not directly on PFsense 2.2.2. I ran some tests with Emulex, it seems the VLAN tag received by the network card is not correct. Any idea of what's going on ? Thank you

i'm such a fool….sorry... it was MY failure - used a wrong netmask on wan interface... thx for your attention phil...

remove all manually created gateways … dhcp on wan does it for you.