I've just recently got an apu2c4 and i haven't had any trouble installing from pfSense-CE-memstick-serial-2.3.1-RELEASE-amd64.img file. What usb stick are you using? i'm using a sandisk usb 3.0 in the front usb 3.0 ports, have also tried a corsair flash voyager usb 2.0 stick. I've read elsewhere (don't remember where) that people have got around the problems by using the internal usb 2.0 header instead of the front usb 3.0 ports.

You might want to have a read of the Virtualization installations and techniques forum.  Post your issue there with specifics of your problem and how you have configured it.

Try uninstalling Squid and reinstalling it.

I've added a "todo" in pfSense packages.  https://redmine.pfsense.org/issues/6443

Hi, I have configured Pfsense+Squid 2.3.1-RELEASE-p1 (amd64) for 90 users in our company. now problem is pfsense is working fine without squid but when i install and configure squid+squidGuard Transparent then it's given very slow browsing so please tell me the best configuration of squid for 90 users. My System configuration is i5 4 core, 8GB RAM, 500GB HDD. Squid configuration below mentioned. Cache Replacement Policy–-Heap LFUDA Low-Water Mark in %--------85 High-Water Mark in %-------88 Enable Offline Mode----------checked Hard Disk Cache Size--------102400 Hard Disk Cache System----ufs Level 1 Directories-----------16 Hard Disk Cache Location---/squid_cache Minimum Object Size--------0 Maximum Object Size    -------20 Memory Cache Size---------4096 Maximum Object Size in RAM-256 Memory Replacement Policy--Heap GDSF I's Very Urgent please help

I think is the same problem happen to me: https://forum.pfsense.org/index.php?topic=112169.0 Add "PPPoE" to the thread title, so the pfSense can collect info about this bug.

Hi All, Just like to apologise for my dumbassery! As you said @johnpoz it was very straight forward I noticed I could add logging on the firewall rules which I did then found I needed to add a 'Floating rule' to allow traffic, discovering how to enable the logs on the rules though is what really sorted it for me. @johnpoz: I have just started a new role in a cloud hosting company and they have set us tasks to do to learn the systems they use and how they are implemented and this was one of the tasks. I also have to do a project to complete my probation and im looking into deploying a PFsense cluster using CARP depending on complexity (I dont want to bite off more than I can chew)

@Gadmin: I see that 2.3.1 is released. Will this update solve the problem Yes, 2.3.1 and newer fix that issue.

Now that's funny right there. :)

@xhark: OK, so I understand it was a bug and now a normal operation ? Could you please precise the id of the bug that you fixed ? https://redmine.pfsense.org/issues/6120 the scope is potentially wider than just what's described there, but the root of it is your configured console settings weren't always applied. You're not configured for a serial console. So now it is applied correctly. Enable the serial console, and it'll be applied correctly as such.

I've had a couple of issues trying to upgrade my pfSense installation from 2.3 to 2.3.1_1 on Hyper V that sound similar to this issue. At first, my original installation would simply break when the update was applied in a completely repeatable manner (restore the VM from backup, rinse, repeat). Basically, I would update using the standard update feature in the UI, which would download, install, then reboot the system. At that point it'd install a couple more things, then continue to boot up the point where it said "Configuring WAN interface…" and immediately reboot. At that point it would then display a bunch of things after the boot prompt and "BTX halted" (as attached). At that point, I thought that it'd be a good idea to simply start fresh, so I made a config backup in the web interface and created a whole new VM and installed 2.3.1 on it from scratch. What I found was that I could successfully update it to 2.3.1_1 after making the minimal configuration required to get it onto the Internet, but if I tried to restore my config.xml file prior to upgrading, then I'd have issues during the upgrade process similar to the above (with the same "crash" at "Configuring WAN interface…" and reboot after installation), although it would at least attempt to boot the system, but with various issues (which seemed to change each time I tried it). For example, here is an excerpt of the console I captured while booting one of these attempted upgrades: KDB: current backend: ddb Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.3-RELEASE-p3 #2 1988fec(RELENG_2_3_1): Wed May 25 14:14:46 CDT 2016     root@ce23-amd64-builder:/builder/pfsense-231/tmp/obj/builder/pfsense-231/tmp/FreeBSD-src/sys/pfSense amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz (1664.84-MHz K8-class CPU)   Origin="GenuineIntel"  Id=0x306a9  Family=0x6  Model=0x3a  Stepping=9   Features=0x1f83fbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse,sse2,ss,htt>Features2=0xfe982203 <sse3,pclmulqdq,ssse3,cx16,sse4.1,sse4.2,popcnt,aesni,xsave,osxsave,avx,f16c,rdrand,hv>AMD Features=0x20100800 <syscall,nx,lm>AMD Features2=0x1 <lahf>Structured Extended Features=0x200 <erms>XSAVE Features=0x1 <xsaveopt>Hypervisor: Origin = "Microsoft Hv" real memory  = 536870912 (512 MB) avail memory = 478343168 (456 MB) ... SMP: AP CPU #1 Launched! Timecounter "Hyper-V" frequency 10000000 Hz quality 10000000 Event timer "HyperV" frequency 10000000 Hz quality 1000 storvsc0 on vmbus0 storvsc1 on vmbus0 da0 at blkvsc0 bus 0 scbus1 target 0 lun 0 hyperv-utils0 on vmbus0 hyperv-utils0: Hyper-V Service attaching: Hyper-V Heartbeat Service da0: hyperv-utils1 on vmbus0 hyperv-utils1: Hyper-V Service attaching: Hyper-V KVP Service <msft virtual="" disk="" 1.0="">Fixed Direct Access SPC-2 SCSI device da0: 300.000MB/s transfershyperv-utils2 on vmbus0 hyperv-utils2: Hyper-V Service attaching: Hyper-V Shutdown Service hyperv-utils3 on vmbus0 hyperv-utils3: Hyper-V Service attaching: Hyper-V Time Synch Service da0: Command Queueing enabled hn0: <synthetic network="" interface=""> on vmbus0 da0: 5120MB (10485760 512 byte sectors) hn0: unknown status 1073872902 received hn0: hv send offload request succeeded hn0: Using defaults for TSO: 65518/35/2048 hn0: Ethernet address: 00:15:5d:00:04:17 hn1: <synthetic network="" interface=""> on vmbus0 hn1: unknown status 1073872902 received hn1: hv send offload request succeeded hn1: Using defaults for TSO: 65518/35/2048 hn1: Ethernet address: 00:15:5d:00:04:18 hn2: <synthetic network="" interface=""> on vmbus0 hn2: unknown status 1073872902 received hn2: hv send offload request succeeded hn2: Using defaults for TSO: 65518/35/2048 hn2: Ethernet address: 00:15:5d:00:04:19 hn3: <synthetic network="" interface=""> on vmbus0 hn3: unknown status 1073872902 received hn3: hv send offload request succeeded hn3: Using defaults for TSO: 65518/35/2048 hn3: Ethernet address: 00:15:5d:00:04:1a Trying to mount root from ufs:/dev/ufsid/574a68fd984d1bc6 [rw]... May 29 15:48:35 init: login_getclass: unknown class 'daemon' May 29 15:48:35 init: login_getclass: no default/fallback class 'default' Configuring crash dumps... Filesystems are clean, continuing... Mounting filesystems... rm: /conf: Read-only file system ln: /conf/conf: Read-only file system     ___ ___/ f \ / p \___/ Sense \___/  \     \___/ Welcome to  2.3.1-RELEASE on the 'pfSense' platform... rm: /COPYRIGHT: Read-only file system rm: /bin/cat: Read-only file system ... /etc/rc: cannot create /dev/null: Operation not supported Creating symlinks...ln: /tmp/tmp: Read-only file system rm: /tmp/config.cache: Read-only file system rm: /tmp/config.lock: Read-only file system rm: /tmp/mnt/cf: Read-only file system rm: /tmp/mnt: Read-only file system rm: /tmp/php_errors.txt: Read-only file system ..cp: /dev/null: No such file or directory ./etc/rc: cannot create /dev/null: Operation not supported done. /etc/rc: /usr/local/sbin/-upgrade: not found /etc/rc: cannot create /tmp/php_errors.txt: Read-only file system /etc/rc: cannot create /dev/null: Operation not supported Launching the init system...rm: /cf/conf/backup/backup.cache: Read-only file system done. Initializing.................. done. Error: cannot open dmesg.boot in system_dmesg_save(). cannot create /dev/null: Operation not supported cannot create /dev/null: Operation not supported Starting device manager (devd)...done. Loading configuration.....PHP Fatal error:  Call to undefined function xml_parser_create() in /etc/inc/xmlparse.inc on line 205 Fatal error: Call to undefined function xml_parser_create() in /etc/inc/xmlparse.inc on line 205 PHP ERROR: Type: 1, File: /etc/inc/xmlparse.inc, Line: 205, Message: Call to undefined function xml_parser_create()Starting CRON... /etc/rc: cannot create /dev/null: Operation not supported done. fcgicli: Could not connect to server(/var/run/php-fpm.socket). /etc/rc: /usr/local/sbin/-upgrade: not found (pfSense) 2.3.1-RELEASE  Tue May 17 18:46:53 CDT 2016 Bootup complete /etc/rc: cannot create /dev/null: Operation not supported rm: /tmp/config.cache: Read-only file system</synthetic></synthetic></synthetic></synthetic></msft></xsaveopt></erms></lahf></syscall,nx,lm></sse3,pclmulqdq,ssse3,cx16,sse4.1,sse4.2,popcnt,aesni,xsave,osxsave,avx,f16c,rdrand,hv></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse,sse2,ss,htt> In this particular case, it seems it's trying to rm -rf itself, but it hasn't mounted the filesystem in r/w mode in order to do that. My next attempt (i.e. start again with a fresh install, then restore config.xml, then try upgrade) did this on boot (which looks similar to the OP's behavior where it's trying to parse an invalid file): start_init: trying /sbin/init May 29 19:07:12 init: login_getclass: unknown class 'daemon' May 29 19:07:12 init: login_getclass: no default/fallback class 'default' Configuring crash dumps... Using /dev/label/swap0 for dump device. Filesystems are clean, continuing... Mounting filesystems... [: -eq: unexpected operator Welcome to  (Patch ) on the '' platform... Dump device does not exist.  Savecore not run. Creating symlinks......done. /etc/rc: /usr/local/sbin/-upgrade: not found /etc/rc: cannot create /tmp/php_errors.txt: Read-only file system pid 89 (php-fpm), uid 0: exited on signal 11 Segmentation fault fcgicli: Could not connect to server(/var/run/php-fpm.socket). Launching the init system...pid 94 (php-cgi), uid 0: exited on signal 11 Segmentation fault Starting CRON... done. fcgicli: Could not connect to server(/var/run/php-fpm.socket). /etc/rc: /usr/local/sbin/-upgrade: not found ()  (Patch )  Bootup complete[/code] I did boot this machine back up off the installation disc and found that most of the files in /sbin and /bin were 0 bytes in length - even fsck and ls were not usable in this state. If I restored my config.xml file [i]after[/i] performing the upgrade (which I did try multiple times to see if it was definitely not a fluke), the upgrade itself would always work correctly (and it wasn't crashing at the "Configuring WAN interface..." step of the boot process either). Since this has worked, I haven't really worried about it and most of the testing I did was more from a curiosity point of view, since my main gateway was working again after I did it the aforementioned way. In my case, the disk isn't a suspect as this disk is used by both other VMs and the host for storing data; and the consistency at which I can replicate the issue by restoring my config.xml, [i]then[/i] upgrading.  

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. Unlocking package pfSense-kernel-pfSense... done. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense: 2.3.1 -> 2.3.1_1 [pfSense] 3 KiB to be downloaded. **** WARNING **** Reboot will be required!! Proceed with upgrade? (y/N) >>> 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 (1 candidates): . done Processing candidates (1 candidates): . done The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense: 2.3.1 -> 2.3.1_1 [pfSense] 3 KiB to be downloaded. Fetching pfSense-2.3.1_1.txz: . done Checking integrity… done (0 conflicting) Upgrade is complete.  Rebooting in 10 seconds. Locking package pfSense-kernel-pfSense... done. Upgrading necessary packages... Checking for upgrades (1 candidates): . done Processing candidates (1 candidates): . done Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense: 2.3.1 -> 2.3.1_1 [pfSense] [1/1] Upgrading pfSense from 2.3.1 to 2.3.1_1… [1/1] Extracting pfSense-2.3.1_1: …. done Removing unnecessary packages... done. Cleanup pkg cache... done.

For AWS, you need 80 and 443 to firmware.netgate.com only.

Well one thing that comes to mind, is a failover setup (carp)? That would take away lots of your worries, and as it is already a vm the added cost is minimal. Maybe one caveat; Not sure though on the "MAC given by our provider" thing? I seem to remember there was some limitation of spoofing a MAC for a CARP IP… that would be worth a question or search in the CARP forum.

that my wlan card might be supported in the near future… Well known working wireless cards for pfSense If this card will be a someday supported or the plain WiFi ac support was added you might be trying out your card, but until this is not given you can only hope or change your card against another one that is working well.

Worked like a charm! Thank you!!!!!

@martylavender: The two default rules pfSense creates are the only rules under Firewall > Rules Out of interest, what rules are these exactly? In PFS version 2.3.x, the LAN side should have three default rules (One anti-lockout and two LAN-2-any rules for IPv4 and IPv6). The WAN side is what has two default rules. Could you have mistakenly set your WAN interface internally? That might account for the blocks you're seeing in the logs.