• Upgrade Successes

    51
    0 Votes
    51 Posts
    20k Views
    B
    updated to 2.3…a repurpose winxp machine... basically its a one click affair... had minor issue with the suricata package... good job guys...keep it up.. [image: pfsenseui.png_thumb] [image: pfsenseui.png]
  • Upgrade to pfSense 2.3 from 2.26 failed. Domains down.

    13
    0 Votes
    13 Posts
    4k Views
    F
    @dpsi: @fmaxwell: @jimp: The boot menu with safe mode was shown in your serial output, just power cycle it, and at that menu hit: 6, then 4, then backspace, then 1 It's shown, but the keyboard input isn't accepted over a serial port.  That threw me off for a long time when I first set it up some years earlier. Sounds like your TX is not wired correctly over your serial cable. Realized I'd made a mistake in describing.  When in the BIOS, which can redirect to serial (as shown), you still need a keyboard connected to a USB port.  Once pfSense has booted, the serial-in does work. I'm in the middle of rebuilding my server, which I had a VMWare image of, allowing me to run it virtually while the hardware is down.  I'll get back to the pfSense mess later – probably after I buy new hardware.
  • 2.3 Killed my SG-2440

    11
    0 Votes
    11 Posts
    3k Views
    B
    have a look at my thread I had a similar issue and I fixed it on my box https://forum.pfsense.org/index.php?topic=110033.0
  • [solution] unable to get on line/webgui

    1
    0 Votes
    1 Posts
    664 Views
    No one has replied
  • Gateways "Pending", no WAN access on fresh 2.3Release install

    8
    0 Votes
    8 Posts
    4k Views
    A
    Well dadgum! Got it working. I did 2 things: 1. Switched the WAN to 1gb1 from igb0. 2. Found that a Cat6A cable was being used from the modem to the router so I switched it to Cat5e. One of those two worked, I'm guessing the Cat5e cable. I'll switch the interface back to igb0 at another date… Thanks for your time and help coxhaus and cmb, I know you are busy right now :)
  • 2.3 clean install issue on SG-2440

    9
    0 Votes
    9 Posts
    2k Views
    C
    @macboy6: cmb, did the CE memstick image also require an update?  I need it for another system and downloaded at release, but have not installed yet. No.
  • 2.1.5 to 2.3 Cluster upgrade load balancer (IP Alias) problem

    3
    0 Votes
    3 Posts
    1k Views
    C
    Looks like there's an issue in the config upgrade code with changing the parent interface in an edge case there. I'm looking into the root cause, but just editing the IP alias virtual IPs with CARP parents, picking the CARP IP, save and apply changes will fix in the mean time.
  • 2.3 Missing many restore options

    4
    0 Votes
    4 Posts
    1k Views
    P
    It's a bug - see https://github.com/pfsense/pfsense/pull/2867 and Redmine issue https://redmine.pfsense.org/issues/6144 Try the very simple and confirm that it will work OK restoring an area that currently does not exist.
  • Unable to retrieve system versions. Error. 2.3 RELEASE

    2
    0 Votes
    2 Posts
    2k Views
    C
    https://forum.pfsense.org/index.php?topic=109690.0
  • Dashboard on iPhone

    3
    0 Votes
    3 Posts
    848 Views
    P
    That solved it - thanks!
  • 0 Votes
    1 Posts
    441 Views
    No one has replied
  • Unable to get in to web GUI

    1
    0 Votes
    1 Posts
    386 Views
    No one has replied
  • 0 Votes
    2 Posts
    912 Views
    R
    I have the same underlying issue. This problem also affects the use of the /status_carp.php page. I have +100k states and using a CARP HA fw pair and get this error when using the CARP status page. As I needed the function to activate / deactivate CARP on this page I patched the file  /usr/local/www/status_carp.php and replaced $states = pfSense_get_pf_states(); with $states = 0; so the page loads but displays no states because of my workaround. René
  • Slow Down Since Update

    6
    0 Votes
    6 Posts
    1k Views
    P
    I might have worked out the issue.  I had snort on the machine and I saw other people are having problem with that package.  What I did was delete the snort package and based on my users they say it is back to normal. Not sure if this helps anyone and I will still run some test to see but looks like the removal of snort might have fixed it Paul
  • PARTIALLY SOLVED - AutoConfigBackup not working (and other issues)

    10
    0 Votes
    10 Posts
    2k Views
    M
    OK, this has been partly solved - the ACB failure was down to a subscription issue which has now been sorted. However, I still think there is a bug with the ACB module, in that if the ACB registration fails, it messes up the GUI in a major way until you reboot. Cheers, Keith
  • MOVED: 2.3-RELEASE - Links de Internet

    Locked
    1
    0 Votes
    1 Posts
    357 Views
    No one has replied
  • 2.3 Wake on LAN

    11
    0 Votes
    11 Posts
    2k Views
    jimpJ
    Good to know it wasn't a problem – if it was, it would have been quite unusual given it appeared to be working correctly in every way. :-)
  • Dpinger wont start after upg to 2.3

    4
    0 Votes
    4 Posts
    1k Views
    jimpJ
    Don't do that. Replacing entire files is a bad idea, and this is one example why. If that was a more critical system file, your config would have rendered any system it was restored on inoperable. Using a patch is much better way to accomplish that task, and if things change too much, the patch won't apply, but the system will still be operational.
  • Services

    4
    0 Votes
    4 Posts
    983 Views
    S
    @phil.davis: I did mine by editing the config: Diag->Backup/Restore - download the config. Edit the config, look for the package name (e.g. I did tftp yesterday on a box) and delete the sections related to it - probably a menu entry, services entry, and a package settings section. Restore the config. (System will reboot) Thanks ill try this.
  • NUT fails / UPS Status after 2.3-RELEASE (amd64) upgrade

    3
    0 Votes
    3 Posts
    1k Views
    K
    @robi: Nut package does not exist on 2.3. Yet….  :)
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.