• Nano install wont boot

    4
    0 Votes
    4 Posts
    1k Views
    jimpJ
    Yes it's still possible for it to be the BIO. Depending on how the BIOS handles booting from USB devices it may not like the multiple slices that exist on NanoBSD
  • Freeradius2 not working after reboot Pfsense

    1
    0 Votes
    1 Posts
    602 Views
    No one has replied
  • Firewall down

    1
    0 Votes
    1 Posts
    638 Views
    No one has replied
  • Screwed the Pooch Here..

    13
    0 Votes
    13 Posts
    2k Views
    stephenw10S
    Yes, +1 for Notepad ++, fantastic tool if you're running Windows. The hexedit pluggin is also great  :) Steve
  • Pfsense Mysql kurulum localhost issue

    1
    0 Votes
    1 Posts
    780 Views
    No one has replied
  • AHCI SDD problem

    11
    0 Votes
    11 Posts
    5k Views
    D
    Chralie, Your advice about using single user mode to enable TRIM worked perfectly.  I also disabled advanced poer management in BIOS and now the CAM status error has also disappeared.  Thanks for the assistance, I am all good now.
  • Can't load kernel after upgrade 2.1.3 to 2.1.4

    5
    0 Votes
    5 Posts
    4k Views
    P
    I also ran into this today. This thread may be helpful to anyone else who gets bitten by the problem: https://forum.pfsense.org/index.php?topic=46725.0 I had already reinstalled by the time I found the thread, though.
  • 1.2.3 Upgrade/Migrate to 2.1.4 on new hardware

    6
    0 Votes
    6 Posts
    1k Views
    S
    pkg list: Cron LightSquid bandwidthd darkstat iperf namp ntop phpsysinfo rate snort squid I'd prefer to NOT re-install Snort… for a variety of reasons, and the only other package that I "need" would be Squid. The others can all be installed fresh. I have no need for old data. Thanks for the confirmation on the XML info.... I may try what you suggested and just nuke it all, and then try a selective restore with just Squid. I'll post back any success or disaster.... -S
  • 2.1.4 Firewall Logs Widget Filter Not Working

    2
    0 Votes
    2 Posts
    1k Views
    rbgargaR
    Fixed, thanks!
  • Install pfsense on msata apu 1c

    5
    0 Votes
    5 Posts
    4k Views
    R
    found a really good guide http://www.gooze.eu/howto/pfsense-installation-on-alix-apu-board-howto/starting-firewall-in-console-mode-on-the-apu-boar
  • HP Proliant DL320 G2 needs hpasmd - Custom pfSense compilation needed?

    7
    0 Votes
    7 Posts
    4k Views
    B
    I know this is an old thread, but I MUST get control of these fans on Proliant DL360 G3 server (and similar) The fans start off low, and once ANY amount of extra cooling is needed, it goes to 100% and hangs there until rebooted. So many have come so close to getting HPASM running, can we now take a stab at it again? If no, then here is the ONLY solution to this… Load VMware ESXi on these boxes and run the firewall as a single VM on them. Then you can load the VMware ESXi drivers that are supported by HP and since ESXi is FREE and WEB BASED, you should be good to go. The idea is actually a good one now that i think of it, because I would never have to rebuild my PFsense box again! I could just move the VM to any other HW i choose moving forward.
  • BUG REPORT: Any install after 2.1.2 hangs on HP DL360 series HW.

    1
    0 Votes
    1 Posts
    699 Views
    No one has replied
  • 2.1.2 & 2.1.3 apinger and gateway monitoring broken!

    5
    0 Votes
    5 Posts
    2k Views
    M
    Hello This is sadly still true for 2.1.4. 2.1.4-RELEASE (amd64) built on Fri Jun 20 12:59:50 EDT 2014 FreeBSD 8.3-RELEASE-p16
  • APU1C4 Boot issues

    4
    0 Votes
    4 Posts
    2k Views
    S
    @pvoigt: @spid: Hi, I have the same board, and also a Kingston 30gb SSD currently running 2.1.3 (Kingston SSDNow mS200 SMS200S3 30GB) Holding off on 2.1.4 until someone confirms 2.1.4 still works with serial console as some have reported problems with the update. I can confirm the serial console is still working with pfSense 2.1.4. I have tested this with an ALIX.2D13. You can find some more details here: https://forum.pfsense.org/index.php?topic=78713.msg429345#msg429345. Regards, Peter Thank you for your feedback, but i'm not running the nanobsd image but the full 64bit memstick installer with serial and after upgrading just now from the auto upgrade web page it all seems fine  8)
  • PfSense 2.1.4 and MatrixOrbital LCD

    1
    0 Votes
    1 Posts
    834 Views
    No one has replied
  • PfSense 2.1.4 amd64 vga updaters

    4
    0 Votes
    4 Posts
    1k Views
    O
    When can we expect a 2.1.4 vga release? At the moment, on https://updates.pfsense.org/_updaters/amd64/ I'm seeing again old release dates (02-May-2014) even though version-nanobsd-vga-4g contains the "2.1.4-RELEASE" version string: latest-nanobsd-vga-4g.img.gz                      02-May-2014 21:24            94184435 latest-nanobsd-vga-4g.img.gz.md5                  02-May-2014 21:24                  99 latest-nanobsd-vga-4g.img.gz.sha256                02-May-2014 21:24                134 version-nanobsd-vga-4g                            02-May-2014 21:24                  14 On my pfSense dashboard I still see the message "You are on the latest version." Will we ever be able to upgrade from 2.1.3 to 2.1.4?
  • No WAN to LAN Throughput

    13
    0 Votes
    13 Posts
    2k Views
    stephenw10S
    Same sentiment from me. It's always better to ask questions than to struggle on alone for fear of saying the wrong thing.  ;) Since you have 4 NICs you can have a 1 WAN and 3 LAN setup (without using VLANs). 3 internal interfaces, 3 separate subnets with whatever firewall rules you choose to put in to filter traffic between them. You might choose to put any servers on one subnet, wireless clients on another and everything else on the last for example. If you want more segregation, firewall rules between each machine for example, you can add further interfaces using VLANs and your switch. Steve
  • 2.13-2.14 NAT, Firewall Issue

    4
    0 Votes
    4 Posts
    1k Views
    R
    Yes - every port forward created in the NAT section generates a firewall rule on the wan interface. Now if you disable the port forward, the firewall rule still shows as enabled, although it doesn't function anymore. This behavior is like this as I observed in 2.1, 2.1.1, 2.1.3.
  • Firmware upgrade architecture

    3
    0 Votes
    3 Posts
    973 Views
    B
    jimp, Thanks for the explanation.  It just seemed a bit strange, in terms of the "normal" GUI style.
  • Installing Pfsense on disk issues

    Locked
    2
    0 Votes
    2 Posts
    2k Views
    K
    Update, after doing a multitude of trial and error (which will be listed at the bottom), i got it past the installation,through the reboot and on to configuring pf sense on my main computer. The last method i tried was placing the hard-drive into slave mode while having the disk reader as the master on the first channel of the motherboards pata controller. 1* I feel really stupid and confused on why or how this worked. I do not believe that it has anything to do with the jumpers on the devices (master, slave) nor do i believe that the access mode (LBA) has anything do do with it (maybe) because I tried multiple combinations of everything. on a side note: I switched installation dvds and burnt myself a copy of pfsense 2.1.4 i386, which did not also worked untill I did the change above. The changes that i made were (not in chronological order, also the ones i can remember) reformatting and partitioning the drive via FreeBSD 8.3 i386 dvd (Errors when installing freebsd but partition and formats remained) switching: Pata cables, sata and pata Harddrive, cd/dvd burners, memory turning off: ps/2 mouse, onboard 1394, Serial ports, Parralel ports ,usb legacy mode support(which was turned back on) installing windows xp(which the machine Had), and updating Bios as well as partitioning the disk attempted to use pfsense live cd shell and try to learn fdisk to get a hint as to what the problem was edit: 1* as opposed to having both hard drive and disk reader be the master of their respective pata channels : hdd = channel 2 , Disk = channel 1
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.