i have just upgraded to 2.4.1 i dont use ppoe. i did notice the CPU was going mad and i even gave it another 2 CPU. (VMWare) Thanks Mat

I was able to use my pfSense box between my USG and cable modem without any issues. The only thing I had to do was create a rule within the Unifi Controller as shown in the attached pic. The workflow is Cable Modem -> pfSense WAN (DHCP) ->pfSense LAN (Static 10.35.2.20)->USG WAN (Static 10.35.2.21)->USG LAN (Static 192.168.1.20)->UniFi Switch 24 (Static 192.168.1.21). With this configuration I'm able to log in to the PfSense box and manage it from the Local LAN. Since I have a Windows Domain running I had to make some adjustments due to the fact that the clients need to point their DNS to a Domain Controller's DNS and DHCP. Both Wired and Wireless clients on the LAN can access both the internal network and the internet. With the Guest Wireless networks I set block LAN to WLAN Multicast and Broadcast Data then manually enter the MAC addresses for the DHCP/DNS server and the Controller. This prevents the Guest network from seeing the machines and shares on the LAN while still allowing them access to DNS and DHCP. I understand the USG and Edge are different but the end result should be the same. [image: 2017-10-26_8-47-21.png] [image: 2017-10-26_8-47-21.png_thumb]

Thank you all for your help. I booted the system from a 2.41 disc, accessed the control panel and then updated in the usual way from 2.4 to 2.41. It now appears to be functioning ok

same problems here 3 VLAN Wans 1 of them static ipv4 was connected 2 of them could not connect per pppoe Upgrade to latest Snapshot has fixed, without renaming anything.

Stay on 2.4  Wait for 2.4.2 Long experience…  The problem will appear to enough people and be solved in a soon future update.

@fohdeesha: …Tested on a nexus 6P and an LG something or other... @marjohn56: Is he still posting messages here? Probably not on none iPhone-threads.  ;)

Edit: my pfsense gives up retrying after a while, but it always come back.

Hi, I installed this traffic totals script (or plugin?) and now on the latest PFsense it doesnt work & I get an error: Error: {"vnstatversion":"1.15","jsonversion":"1","interfaces":[Error: Database load failed even when using backup (No such file or directory). Aborting. How do I uninstall this? Thanks, Rich

It always helps to read the release notes. But, release notes are for things that the software cannot handle or very specific unavoidable situations. In this case, running under VMWARE is extremely common and instead of assuming the user will catch the issue, why not simply make the installer add the needed change to the boot loader?? The fact that a patch to correct this, was made, says that it should have been caught in the previous release… It is still great work and it is appreciated, but like I said before, if it is meant to be Enterprise, Production ready, these 'silly' things will drive customers away as well as: "I have never, ever had any upgrade issues with Untangle". @Grimson: https://doc.pfsense.org/index.php/2.4_New_Features_and_Changes#Known_Issues reading helps.

Thanks. The reinstall did the trick.

Yep. I did a backup first. If you have done this right, and you are upgrading to the version 2.4.1 and gets out problems and issues too, I would suggest to do a fresh and full install once more again and also play back the backup file once more again! Just needed a pointer in the right direction which I got on fb from a kind soul. Please ensure that you are using the ADI-AMD-64Bit-Serial version of pfSense! All recovered now, thanks. Keep thre eMMC storage up to date and install a small mSATA that fits your needs and you get a fast backup system! Sometimes time will be not even there, and so you might be able to get a working platform fast back.

pfSense archive (all versions)

@Gertjan: @gklimeck: …... I made Rules in my firewall to match my LAN rules but it can't get out to WAN from a wireless device. What am I missing? Dono. Didn't saw your firewall rules. What about a "pass-all" rule to test? Afterward, you make more specific rules- and test after each new rule - and step back when things won't work anymore. Not a bad idea and I'll get better at this. Thanks, G

Thanks - I downloaded all of the 2.3.4…  in case the links disappear later. I know I should run out and buy 5 new boxes to get rid of the old hardware...  Let me check my pockets...  Lent!

At least that is the way with standard FreeBSD I can fairly report that it is working for me in pfSense version 2.3.x and 2.4.x too!

Awesome, thanks! Wasn't sure if there might be any incompatibilities or caveats importing a config from an older version of the nano distro into the current/full distro.

I cannot thank you enough Renato. I've been tearing my hair out for a few months with this issue before stumbling upon your suggestion here. Sure enough, /usr/local/share/pfSense/keys/pkg/revoked/.empty was there - and the moment it was removed, presto! All I wanted to do was install man :'(. This will be pinned prominently in my notebook! (Though all other systems I manage have been upgraded past 2.3.3!) Cheers, Sam. @Renato: It's exactly what I suspected. There is a bug in pkg that causes this crash. You can see details here: https://github.com/freebsd/pkg/pull/1586 We already fixed it in pfSense before submit the patch to upstream, and based on truss output we can see: The presence of the empty file /usr/local/share/pfSense/keys/pkg/revoked/.empty is the cause. I suspect there is a /usr/local/share/pfSense/keys/pkg/trusted/.empty file too. Just remove them and it will work as expected. As soon as you update pkg to latest version bug will be fixed.

@chudak: I have Sonic 1gb fiber.  @opalmer  it sounds it will/may affect me as well? Thx Answering my own query - I see no speed slowness on Sonic 1gb fiber on 2.4.1 release.