• Upgrade 2.4 killed my wpa2-eap with ntlm passwords

    4
    0 Votes
    4 Posts
    1k Views
    G
    Today I reinstalled 2.4 used a backup config. Problem still there. Then I reinstalled 2.3 again with the same backup config and everything is working again. So for me no 2.4 yet.
  • What can be done to simulate NanoBSD behavior in pfSense 2.4?

    3
    0 Votes
    3 Posts
    1k Views
    ?
    Hi there, For quick full pfsense backups and recoveries this is what we do with our telecommuters. It works quite well. Hopefully the idea can also benefit you. First, make sure that your router hardware can boot from an external USB hard disk drive in "legacy BIOS boot" mode. If for some reason the BIOS doesn't allow it scrap the idea. Also if you do not have 3 USB ports on your pfsense hardware, make sure that you have an external powered USB hub with 3 ports. Then, get/make yourself a bootable USB flash-drive with some flavor of Linux on it that you are comfortable with. For instance, it could be a live Linux Mint 18.2 disk, or BootRepair live disk, or still bitdefender live disk. Whatever you pick ensure that it is GUI based. Something that's capable of booting up your router hardware and allow you to run a terminal window and a utility like dd, or dcfldd or yet dc3dd (these are all raw disk copy tools for command line use). Next, get yourself a couple of identical, top quality Flash disks no larger than 16GB, (or a couple of small size SATA SSDs that you get from AliExpress for cheap and convert to external USB drives by using cheap enclosures). Regardless what kind, ensure that the drives are not larger than 16 (or at most 32) GB. The reason for size limit is that, as a matter of routine backup you will be performing an image copy of the entire disk drive, and the larger the drive the longer the copy time will be. A nanoBSD based pfsense system is a lightweight system and it fits on a few gigabytes at most. So, my assumption is that 8, 16 or 32GB will be more than enough for your situation. But on the other hand larger USB flash drives are faster than smaller ones, so that's why 16GB is probably the perfect size/performance point. Now, install pfsense 2.4 on one of the USB flash disks (no ZFS, no UEFI, just basic ufs in legacy bios boot mode). Configure it and use it as if you are in normal operational mode. At your intended, periodic backup time, simply shut down pfsense, plug in your Linux USB flash disk mentioned at the beginning, get a terminal session going and run a dcfldd copy of the entire pfsense flash disk onto your backup flashdisk of identical physical size. Typically this would take a few minutes. So, basically you will be running pfsense off an external USB flash drive and when you decide to run a backup, you go into linux mode and copy one flash drive onto the other in raw copy mode. This will result in absolutely identical, physically separate pfsense disks that you can swap as needed. Performance wise the USB flash disks won't be worse than any nanoBSD solution, but obviously you won't be able to run "heavy" stuff like squid cache etc. But I gathered that that's not what you're looking for based on the fact that your starting point is nanoBSD. The beauty about this solution is that if you need to restore, you simply switch to the other flashdrive, there is no need to copy anything. Again, this is something that we have been doing with many telecommuters (50+) at large with different levels of technical knowledge and all kinds of pfsense hardware, and the cornerstone of our logic has been that regardless how expensive the hardware, the firewall/gateway would eventually fail, so quick recovery, high level of safety and painless but guaranteed backup were all necessary. So hopefully this will also help you. Good luck.
  • MOVED: pfSense 2.4.0 and syslog-ng management interface woes

    Locked
    1
    0 Votes
    1 Posts
    335 Views
    No one has replied
  • Downgrade 2.4.1 DEV to 2.4 RELEASE?

    2
    0 Votes
    2 Posts
    1k Views
    jimpJ
    At the moment, the config.xml is compatible and you can move back to 2.4 if you want. This is the easiest method: https://doc.pfsense.org/index.php/Automatically_Restore_During_Install#Recover_config.xml However, 2.4.1 will be coming out in a week or so, you may just want to stay on 2.4.1 for the moment.
  • Hyper-V PCI passthrough with PFSense 2.4

    1
    0 Votes
    1 Posts
    408 Views
    No one has replied
  • EMMC not recognize with latest pfsense on Gigabyte mini pc EL-20 3710

    5
    0 Votes
    5 Posts
    1k Views
    M
    Same issue here!! I have a ECS LIVA Z https://www.newegg.com/Product/Product.aspx?Item=N82E16883105009&cm_re=ecs_liva--83-105-009--Product with 32GB emmc and I've tried installing the nand installer on it as I read in some article by booting Ubuntu live cd from one usb stick and from the other usb stick (with nand pfsense install) used dd to copy image from sencond usb stick to emmc but it doen't boot. Goes straight to bios…. In Ubuntu emmc shows as /dev/mmcblk0 ... or something like this ( as the post above). I just tried to install pfsense 2.4 with usb installer but same issue. NO EMMC detected! What's the solution for this? And if you have one please show the steps. I'm not too advanced with pfsense...
  • Libssl.so.7 not found after upgrading to 2.4.0

    6
    0 Votes
    6 Posts
    3k Views
    E
    I had same issue and installed from USB stick.  I'm sure there is a less brute force way to accomplish the same thing, but it worked. https://forum.pfsense.org/index.php?topic=137993.0
  • [SOLVED] 2.4.0, SG-4860 will not upgrade

    4
    0 Votes
    4 Posts
    835 Views
    C
    Exact same experience: "failed" on the download first time. The second time worked perfectly. The reboot time was around 10 minutes, maybe a bit more.
  • 0 Votes
    1 Posts
    1k Views
    No one has replied
  • ANSWERED/SOLVED: libssl.so.8 not found - I CAN'T UPDATE FROM 2.34p1

    4
    2 Votes
    4 Posts
    14k Views
    M
    Thanks for the posts, I did notice that on my machine I needed to install the kernel afterwards. Running the normal update from the console fixed that.
  • Clean Factory 2.4 install on SG2440

    3
    0 Votes
    3 Posts
    751 Views
    MORGiONM
    Fresh install worked perfect, thank you
  • 0 Votes
    2 Posts
    7k Views
    jimpJ
    That must be an outdated copy of /usr/local/lib/php/20131226/zmq.so being referenced because it doesn't use that library any longer. And the pkg errors indicate that it can't lookup and DNS requests. The fastest method of recovery is a fresh installation if you can, then use the 'recover config.xml' option in the installer and it will read your current config in before wiping the drive and reinstalling, you'll boot back up good as new.
  • 2.4.0 Release

    Locked
    40
    0 Votes
    40 Posts
    8k Views
    jimpJ
    OK, this thread is officially getting unwieldy :-) Locking this thread for now. Please find an existing thread for a single issue topic or start separate threads for distinct issues but only after searching to see if you can find an existing related thread. We're seeing the same info in 2-3 threads and new threads for duplicate topics and so on. Using the "All Unread" view is especially helpful for locating new/recent threads: https://forum.pfsense.org/index.php?action=unread;all;
  • Packages locked in v2.3.x?

    2
    0 Votes
    2 Posts
    695 Views
    JeGrJ
    Sorry, just found https://forum.pfsense.org/index.php?topic=137938.0
  • 0 Votes
    6 Posts
    5k Views
    F
    Update:  I gave up trying to fix this and just chalked this up to a bad snapshot from 10/8.  I did a reinstall with the 10/9 snapshot, and things are back to normal.
  • Random Rebooting in PFsense 2.3.4-RELEASE amd64

    12
    0 Votes
    12 Posts
    2k Views
    Y
    ALRIGHT. So I returned the Quad Port Intel Gigabit NIC and am now using two dual port gigabit Intel NIC's with the new version of pfSense 2.4.0 . This appears to be running successfully now. I have tested it with the same load I placed against the previous build with the different NIC and it has not rebooted once yet. The Dual port NIC I got is the Intel PRO/1000 Py Dual Port Server Adapter. I will provide an update if the issue re-occurs but we appear to be running smoothly now.
  • Upgrade cluster to 2.4 failed on second node

    8
    0 Votes
    8 Posts
    1k Views
    M
    @jimp: No, it is most likely too damaged to correct. Reinstall and use the "recover config.xml" option on the first screen of the installer to get your current config back. You'll be up and running in only a few moments. when i did the pkg-static update –f it all happend but i forgot to do  pkg-static upgrade –f  i cant remember if i saw that somewhere. After that was done i did the pfsense-upgrade and it all updated correctly. Didn't have to reinstall. only had to do the reinstall packaged from the Gui otherwise i would not access the addons via the Menu.
  • Unable to access upgrade behind proxy

    1
    0 Votes
    1 Posts
    608 Views
    No one has replied
  • Removing pfSense trademarks?

    Locked
    3
    0 Votes
    3 Posts
    1k Views
    ivorI
    Thread locked for obvious reasons. See: https://doc.pfsense.org/index.php/Can_I_sell_pfSense https://www.netgate.com/blog/its-still-free-to-use.html https://www.netgate.com/blog/announcing-a-new-trademark-policy-for-pfsense.html
  • Does pfSense support Cisco ERSPAN?

    2
    0 Votes
    2 Posts
    983 Views
    I
    No. https://redmine.pfsense.org/issues/7029
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.