• Previous releases not available

    4
    0 Votes
    4 Posts
    916 Views
    7
    ok, got it.  It isn't clear, but after going to Dowloads and clicking "Show me the mirrors" in the text paragraph at the bottom, it took me to the file list. Thanks for the help everyone. 70tas
  • 0 Votes
    1 Posts
    519 Views
    No one has replied
  • Upgrade 2.2.2 –> 2.2.3: Listen queue overflow --> Bad performance

    2
    0 Votes
    2 Posts
    8k Views
    H
    [Solved] –> See: https://forum.pfsense.org/index.php?topic=95837.0 Had to remove the sync-option from /etc/fstab
  • 0 Votes
    2 Posts
    2k Views
    R
    I ran into a similar situation when I was trying to save the config file directly with the web interface based file editor. Also got the same when I tried to replace the file manually on the file system with another one, uploaded with SFTP. It looks like there's a process "watching" this file when it's being modified from outside, and instead accepting the modifications, it deletes it and it tries to restore something from a backup. The problem is, that: if the backup doesn't contain a valid file, the result will be an empty file the user doesn't have a chance to override this behaviour. It may be very well that somebody wants to do this on purpose, and fighting against the system is not something pleasant to do.
  • Cannot not ping any interface

    4
    0 Votes
    4 Posts
    722 Views
    johnpozJ
    you can ping the wan address from the lan side with the default rules. Not sure what a proxy service has to do with icmp? Sounds like to me he put a gateway on the "lan" which I just am blown away at how many times that comes up..  And yup will break it pretty bad..
  • Pfctl loading errors after 2.2.3 update

    1
    0 Votes
    1 Posts
    406 Views
    No one has replied
  • Upgrade from 2.1.5 to 2.2.3 - Login fails

    9
    0 Votes
    9 Posts
    2k Views
    D
    @mwagner: My password contain these characters: _£@;[{.#! [/quote] [image: password_strength.png] SCNR.
  • Upgrade from 2.1.5 to 2.2.3 - Configuring interface hangs during boot

    5
    0 Votes
    5 Posts
    780 Views
    C
    Great. Surprised that worked previously, the default limits generally much too low for 10G cards. The bce tunables usually aren't necessary unless you're seeing problems of some sort, but shouldn't hurt anything to set them.
  • PC w/VGA -> SG-2440 w/Serial, backup & restore question

    3
    0 Votes
    3 Posts
    728 Views
    N
    Thanks for the reply. The SG-2440 uses the second serial port for console.  Is there a setting in the config file to specify the serial port?  I looked and didn't find it in the backup of my PC installation. Also, of more concern, what of the "optimizations" in the ADI image for the SG-2440?  Will I lose any of those or need to make changes after restoring the PC backup? Thanks, Frank
  • How to reset pfSense VK-T40E to factory defaults using the reset button?

    2
    0 Votes
    2 Posts
    712 Views
    M
    What about the 'Diagnostics\Factory Defaults' menu item?
  • Upgraded to 2.2.3 and OpenVPN/internet access dies

    1
    0 Votes
    1 Posts
    444 Views
    No one has replied
  • 2.2.2 -> 2.2.3 NanoBSD APU required hard power cycle

    2
    0 Votes
    2 Posts
    653 Views
    S
    When I auto-upgraded my APU from 2.2.2 to 2.2.3 I also had the device eventually hang and lockup requiring a hard reboot. Except when mine came back up I was getting a Kernel not found error. Using my original 2.0 thumb drive I was able to boot up a shell and get into /tmp/hdrescue and run: tar xzpf /tmp/hdrescue/kernels/kernel_SMP.gz –exclude loader.conf -C /tmp/hdrescue/boot/ The above command I found from this thread: https://forum.pfsense.org/index.php?topic=46725.0 I'm now able to boot back into 2.2.2 but most of my packages are hosed in an inconsistent state.  At least now I can grab some configs and kernel modules before doing a fresh 2.2.2 install.
  • Hard drive led constantly on after upgrade to 2.2.3

    3
    0 Votes
    3 Posts
    785 Views
    I
    Yep, but couldn't understand which process was the one doing I/O. I'm not a *nix expert… but the forum and the many "good news" rang a bell https://forum.pfsense.org/index.php?topic=95837.msg533449#msg533449 mount -o nosync / SOLVED! PS: now removed the "sync" option out of /etc/fstab and rebooted, looks ok.
  • WIFI home router working with pfSense

    10
    0 Votes
    10 Posts
    4k Views
    DerelictD
    The only reason to have a default gateway in the netgear is so the netgear device itself can route to the internet.  You might or might not be able to even set a default gateway on the LAN side of that device. The wireless clients should have the IP address of pfSense as their default gateway either from DHCP or static.  The Netgear simply bridges the wireless clients with the wired network.  The netgear/AP is not a layer 3 hop.  You are putting wireless and wired clients on the same segment.
  • 0 Votes
    7 Posts
    1k Views
    C
    You're redirecting it somewhere else. There are suggested workarounds to get in here: https://doc.pfsense.org/index.php/Locked_out_of_the_WebGUI
  • MOVED: How to completely uninstall iperf and freeradius2

    Locked
    1
    0 Votes
    1 Posts
    351 Views
    No one has replied
  • MOVED: pfSense 2.2.3 - Internet is very slow via Squid3

    Locked
    1
    0 Votes
    1 Posts
    596 Views
    No one has replied
  • Browsers do not work.

    5
    0 Votes
    5 Posts
    1k Views
    J
    How do you know you have internet access?  I suppose you can ping IP addresses on the internet? Could be a DNS problem.  If you can load PFSense in your browser, then I don't see how this is a totally "browser" issue.  It seems odd that it would be a PFSense issue that not a single browser would display a web page for you.  Unless it's a rules problem… Can you ping by domain name?
  • PPPoE issue after upgrading to 2.2.3

    6
    0 Votes
    6 Posts
    2k Views
    ivorI
    If it works fine that was the issue then, your DNS doesn't like the pings! You can lower the number of pings or just use a different server to ping.
  • FYI: crash during 2.2.3 upgrade

    6
    0 Votes
    6 Posts
    1k Views
    rcfaR
    So, great, previous crash fixed, ran the "reinstall all packages" routine to test, but now I get this crash: Crash report begins.  Anonymous machine information: amd64 10.1-RELEASE-p13 FreeBSD 10.1-RELEASE-p13 #0 c77d1b2(releng/10.1)-dirty: Tue Jun 23 17:00:47 CDT 2015    root@pfs22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10 Crash report details: PHP Errors: [29-Jun-2015 12:35:33 Etc/UTC] PHP Fatal error:  require_once(): Failed opening required '/usr/local/pkg/shellcmd.inc' (include_path='.:/etc/inc:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg') in /etc/inc/filter.inc on line 3852 Another thing that would be useful: if version updates wouldn't mess with the crontab file: after each update I have to re-add the 'MAILTO=""' line in order not to get swamped with notification e-mails; even better if we'd get notifications e-mails when there are package and/or OS updates ready. But those are different issues…
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.