What pfSensse version are you running? What branch do you have selected in System > Update > Update Settings? Steve

Install the shellcmd package, add whatever commands you need. https://doc.pfsense.org/index.php/Executing_commands_at_boot_time Really though you'd be much better off using a different modem. Either an external device that provides a real Ethernet interface or something that you can connect with over ppp, if the speed is not an issue. Steve

@ThatotherGuy: I do appreciate your reply, however I have tried unplugging cables, numerous times. Let me guess : the device you hooked up to the LAN to visit the GUI also uses a static IP - or, using other words : you changed default network settings on that device. In that case, ripping out the RJ45 and putting it back in won't do - neither running ipconfig /renew. You have t change your IP/DNS/Gateway manually. Btw : an advice : when you buy a PC/Printer/whatever : Never ever deactivate the DHCP client. Leave it on. Don't touch any network settings except maybe the network group name. You just gave one of the many reasons why … Setup in your router (pfSense here) all IP's with their MAC addresses. All your devices will also have the IP(s you assigned on a central place. Do not use static addresses.

@joltman: Have you rebooted? Yes, in addition I have found that If I go to    "System/General Setup" and click save without changing anyting it appears again. Does it make any sense? Ops it looks like there was an empty space after the 400000

That setting actually applies immediately. You might have to trigger a refresh though by reloading the System Update tab  or refreshing the firmware check on the dashboard or running 'pkg update' at the CLI. Steve

@KOM: Can someone help to understand this error and how to fix it?  Are those because I have suricata installed? This looks like console output from suricata.  Are you actually having any problems or are you just concerned about this text? "Default deny rule IPv4 (1000104533) " which don't even exist in my rule list? what is going on? The default deny rule is a hidden rule at the bottom of every interface's ruleset.  If something isn't explicitly allowed by a rule above it, the default deny rule will catch it and block it. I'm not having problems, apparently. I though the default deny rule had a different code  Default deny rule IPv4 (1000000103)

Which part does it actually show as full? I assume you installed with no swap slice? If you have RAM to spare you might try moving /var and /tmp to RAM drives in System > Adv. > Misc. Steve

The default console speed has been 115200 for a while now. Since 2.2 at least. But if you updated from an older version it might have been 9600 and it keeps that setting. Some people set it to that to match the BIOS output so they can see the full boot sequence. The ALIX board had a default BIOS speed of 38400 and pfSense shipped with it set to match on that hardware. Steve

So while double NAT'ed configurations are generally undesirable, I am not seeing any problems with my setup.  I guess time will tell. If the USG is just a router / controller why not just disable NAT there?

EPS Power Saving Mode didn't resolve issue btw. every component of HW has been replaced… except AC adapter... gonna try that next. edit: power bricks replaced that wasn't it. so FINALLY after all is said and done i figured out what was the causing the panic, the case expansion plugs like USB ports, audio plugs, eSATA port. i unplugged all those fancy things and system has been rock solid since that time! yay! just wanted to toss that in here for future reference!

Good to hear, thanks for the feedback.  :) Steve

Ok thanks. I think i got it.

Just a follow up - I found the pfSense-upgrade command and noticed these packages queued: Installed packages to be UPGRADED: squid: 3.5.27 -> 3.5.27_3 [pfSense] redis: 3.2.10 -> 3.2.11 [pfSense] pfSense-pkg-suricata: 4.0.3_1 -> 4.0.4_1 [pfSense] pfSense-pkg-squid: 0.4.43 -> 0.4.43_1 [pfSense] pfSense-pkg-pfBlockerNG: 2.1.2_2 -> 2.1.2_3 [pfSense] pfSense-pkg-ntopng: 0.8.11 -> 0.8.12 [pfSense] pfSense-default-config: 2.4.2_1 -> 2.4.3 [pfSense-core] pfSense-base: 2.4.2_1 -> 2.4.3 [pfSense-core] pfSense: 2.4.2_1 -> 2.4.3 [pfSense] pecl-intl: 3.0.0_10 -> 3.0.0_11 [pfSense] lighttpd: 1.4.47_1 -> 1.4.48_1 [pfSense] freetype2: 2.8 -> 2.8_1 [pfSense] clamav: 0.99.2_5 -> 0.99.4 [pfSense] On a hunch, I tried installing the pecl-intl package by hand. This fixed the error message "Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20131226/intl.so' - Shared object "libicui18n.so.59" not found, required by "intl.so" in Unknown on line 0" After that, I installed freetype and clamav, squid an redis. No errors so I let fly: **[2.4.2-RELEASE][admin@mobeer.localdomain]/usr/local/lib: pfSense-upgrade -d Updating repositories metadata… Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 8 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-pkg-suricata: 4.0.3_1 -> 4.0.4_1 [pfSense] pfSense-pkg-squid: 0.4.43 -> 0.4.43_1 [pfSense] pfSense-pkg-pfBlockerNG: 2.1.2_2 -> 2.1.2_3 [pfSense] pfSense-pkg-ntopng: 0.8.11 -> 0.8.12 [pfSense] pfSense-default-config: 2.4.2_1 -> 2.4.3 [pfSense-core] pfSense-base: 2.4.2_1 -> 2.4.3 [pfSense-core] pfSense: 2.4.2_1 -> 2.4.3 [pfSense] lighttpd: 1.4.47_1 -> 1.4.48_1 [pfSense] Number of packages to be upgraded: 8 188 KiB to be downloaded. **** WARNING **** Reboot will be required!! Proceed with upgrade? (y/N) y Downloading upgrade packages… Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking for upgrades (8 candidates): ........ done Processing candidates (8 candidates): ........ done The following 8 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-pkg-suricata: 4.0.3_1 -> 4.0.4_1 [pfSense] pfSense-pkg-squid: 0.4.43 -> 0.4.43_1 [pfSense] pfSense-pkg-pfBlockerNG: 2.1.2_2 -> 2.1.2_3 [pfSense] pfSense-pkg-ntopng: 0.8.11 -> 0.8.12 [pfSense] pfSense-default-config: 2.4.2_1 -> 2.4.3 [pfSense-core] pfSense-base: 2.4.2_1 -> 2.4.3 [pfSense-core] pfSense: 2.4.2_1 -> 2.4.3 [pfSense] lighttpd: 1.4.47_1 -> 1.4.48_1 [pfSense] Number of packages to be upgraded: 8 188 KiB to be downloaded. [1/8] Fetching pfSense-pkg-squid-0.4.43_1.txz: …..... done [2/8] Fetching pfSense-pkg-pfBlockerNG-2.1.2_3.txz: …....... done [3/8] Fetching pfSense-pkg-ntopng-0.8.12.txz: .. done Checking integrity… done (0 conflicting) Upgrade is complete.  Rebooting in 10 seconds. Broadcast Message from admin@mobeer.localdomain                                        (/dev/pts/0) at 10:07 CDT... Upgrade is complete.  Rebooting in 10 seconds.** The box dumped my ssh connection after 10 seconds, but it was still up. Hard drive light blinking like crazy.  I hooked a monitor up to the 1U and it said it was "upgrading packages" so decided to let it go this time.  After 5 minutes the HD was still cranking so went off and did some woodworking. 20 mins later I heard the reboot tune play. That's actually quite impressive considering I hit the power during the upgrade - twice mind you! I've proved the upgrade is quite idiot proof if nothing else. So far it looks good. Thanks for all the support!: [image: pf.png] [image: pf.png_thumb]

Are u running a machine with old bios that can't boot from USB?  'Cuz the standard method of using Rufus to create a bootable USB works like a charm, and Rufus is even a portable Win App meaning you just run the puppy wo even having to install it.