• Where r the 2.3 DEV snapshots?

    4
    0 Votes
    4 Posts
    885 Views
    P
    Good to see the 2.2.3 snapshots just appeared after I made my post above. On the front page at http://snapshots.pfsense.org/ you could now s/2.2.2/2.2.3/
  • Revert from Dev 2.3 to stable 2.2.2

    4
    0 Votes
    4 Posts
    703 Views
    N
    luck is my baddy today :) thx again. solved it
  • SOLVED: all NTP servers are unreachable after upgrade from 2.1.5 to 2.2.2

    4
    0 Votes
    4 Posts
    1k Views
    Y
    IMHO the CARP interfaces/IPs should be used for what they've been designed. Agree. It was just an upgrade issue - in 2.1.5 worked, in 2.2.2 without tuning - not. In any case I would not qualify this as an error in pfSense :)
  • 0 Votes
    4 Posts
    862 Views
    X
    i can confirm that solved it, probably it should be set as default in the config
  • Installing pfSense 2.2.2 on Netgate RCC-VE 2440

    7
    0 Votes
    7 Posts
    2k Views
    jahonixJ
    @clusty: I got this working only with Putty under windoze as a serial console. All others I've tried […] give me garbaged output Coming from a Windows world myself I know what you're saying. Been there, … There's puTTY for OS X which works reasonably well (but needs X11). Currently I use ZOC in OS X which works great. I also have a Win7 VM where I use Tera Term frequently.
  • Upgraded from 2.1.4 to 2.2.2 and unbound wont start

    Locked
    8
    0 Votes
    8 Posts
    3k Views
    R
    @phil.davis: Perhaps this file owner and permissions thing is the same as: https://forum.pfsense.org/index.php?topic=92712.msg514140#msg514140 and this thread: https://forum.pfsense.org/index.php?topic=92782.msg514463#msg514463 and re-applying the update using the latest full update files at http://files.atx.pfsense.org/mirror/updates/ will put everything correctly in place. Thanks Phil, I did not get a chance to try this. I already went onsite and did a reinstall and then config restore and it works like a champ. I'll remember this for next time, but hopefully there wont be a next time….
  • Installing pfSense 2.2.2 Tutorial

    11
    0 Votes
    11 Posts
    3k Views
    KOMK
    It's in desperate need of some formatting.  Download a few professional manuals or guides and take some notes on how they look.  Pay attention to: Font faces & sizes General layout & spacing Chapters or Headings Make your title font size larger than the body text, and BOLD it or something to make it stand out. Also, don't link to the i386 build since it's being deprecated. Do as John says and use a virtual machine so you can create clear screencaps instead of fuzzy photos with flash flares. Don't put your images inline with your text or it just looks like a jumble. VLAN, not Vlan. I could go on, but the major thing seems to be you're installing in one particular way and you don't talk about other options.  Any time the user has some sort of choice, you need to explain the available options and what they mean instead of just saying "Do this", when it may not apply to that user.  For example, you say to enable DHCP on LAN.  That can cause major problems if the user already has a DHCP server.
  • 2.2.2 Upgrade -> OpenVPN Failure in Web GUI

    4
    0 Votes
    4 Posts
    1k Views
    B
    Happened to me on a fresh install posted in this thread.  https://forum.pfsense.org/index.php?topic=92712.0  Not an upgrade but a fresh install.
  • [solved] New errors with WAN (sk0) with upgrade to 2.2.2

    19
    0 Votes
    19 Posts
    4k Views
    S
    Ah ok =) Anyway. This isn't really a problem anymore for me. I know what caused the issues now. Therefore i would like to take this opportunity to thank everyone who has been helping me out with this issue =) Thanks !
  • Issues making bootable install USB with 2.2 RELEASE i386

    7
    0 Votes
    7 Posts
    1k Views
    jimpJ
    Those are the ones you give out to people you don't like when they ask for a flash drive to "borrow" :-)
  • MOVED: fresh installed pfsense 2.2 - captive portal crashed.

    Locked
    1
    0 Votes
    1 Posts
    373 Views
    No one has replied
  • MOVED: can't install squidGuard after pfsense updated to Release 2.2

    Locked
    1
    0 Votes
    1 Posts
    386 Views
    No one has replied
  • PfSense 2.2 Not Accepting sshpass Command

    9
    0 Votes
    9 Posts
    2k Views
    johnpozJ
    ^ yeah is this script in clear text?  Sounds like bad idea to me ;)
  • User 1001?

    7
    0 Votes
    7 Posts
    1k Views
    jimpJ
    There was an issue with the update .tgz files that should be corrected now. Forcing another update to the same firmware should be OK, or a wipe+reload is always a solid path to success.
  • Unifi controller problem to install mongodb

    1
    0 Votes
    1 Posts
    703 Views
    No one has replied
  • 0 Votes
    2 Posts
    532 Views
    stephenw10S
    Interesting. So it appears the ale(4) driver was causing problems for fragmented packets. Thanks for posting that. Steve
  • Upgrade 2.2.1 -> 2.2.2 no sync anymore

    5
    0 Votes
    5 Posts
    944 Views
    N
    Thanks a lot for the hint Gertjan!
  • PfSense doesnt install BootLoader on HP Thin client.

    9
    0 Votes
    9 Posts
    1k Views
    P
    There is no 8GB nanoBSD image built. Install the 4GB image. It will use the first 4GB of the 8GB CF card. The last 4GB will be free. Who cares? Dansguardian (becoming E2guardian) and Squid (as long as you do not want to cache) run on nanoBSD. If you are going to do Squid caching then you need a full install. Some packages are not supported on nanoBSD - to see which are not supported you can look in https://github.com/pfsense/pfsense-packages/blob/master/pkg_config.10.xml - search for "noembedded" to find packages that do not install on nanoBSD.
  • 2GB NanoBSD (no VGA) flash issues (and upgrade issues) with 2.2.2

    6
    0 Votes
    6 Posts
    1k Views
    P
    Upgrades should go fine - the vr* interfaces are already in the config of the upgraded system. I have upgraded 10 Alix 2D13 to 2.2.2 all without trouble. The change to factory default behavior is documented in just 1 line I can find: https://doc.pfsense.org/index.php/2.2_New_Features_and_Changes Change default NICs from vr to em – vr is on the way out and em is the most common NIC in use today. A reader needs to already know a bit about pfSense and default interface assignment… to understand the ramifications of this 1-line statement  :)
  • Can't access web interface after initial setup

    4
    0 Votes
    4 Posts
    825 Views
    D
    Uhm… perhaps it would work better if you changed your PC's IP address as well to match the pfSense LAN subnet. Or perhaps enable DHCP? Or maybe just try again so that you can tell us what exactly you have done, since you apparently cannot even remember? Sigh...
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.