• SG-1100 initial setup failing

    7
    0 Votes
    7 Posts
    1k Views
    stephenw10S
    I was expecting 192.168.1.10 but it turns out .100 is the start of the DHCP range so that is actually expected. I could have sworn it started at .10 but the default config files don't lie so it must just be what I set. Or I was somehow in a parallel universe! The actual cause of the problem was the subnet conflict between WAN and LAN. Anyway I'm glad we were able to get you up and running despite my confusion. Steve
  • Pfsense works with DSL ISP but not WISP - Please help

    4
    0 Votes
    4 Posts
    535 Views
    stephenw10S
    You could but if the same switch port works with no change other than plugging the DSL modem in instead of the WISP connection then it probably won't help. When you connect the WISP can you ping the gateway IP from pfSense? Were you unable to ping anything even by IP, like 8.8.8.8? Steve
  • New Install of pfsense, L3 managed switch with vlans, no internet

    8
    0 Votes
    8 Posts
    1k Views
    DerelictD
    Where in NAT? Outbound? Yes, it is perfectly normal to apply outbound NAT to localhost addresses and whether or not it is a VM has nothing to do with anything.
  • Monitor IP (new install)

    monitor ip
    2
    0 Votes
    2 Posts
    563 Views
    GrimsonG
    RTFM: https://docs.netgate.com/pfsense/en/latest/book/routing/gateway-settings.html#monitor-ip
  • Em2 loses connection after setup

    5
    0 Votes
    5 Posts
    954 Views
    B
    Thanks for the help. I upgraded to Windows Pro to use Hyper-V. Same setup and everything is working fine.
  • 2.3.4-RELEASE-p1 => 2.4.0 "system update failed" please help!

    19
    0 Votes
    19 Posts
    10k Views
    S
    I was very hopeful this would fix me, but it did not. Same issue trying to go from 2.3.4 to current. Doing this actually made the issue slightly worse in that before I could at least check for updates and now I cannot. Sounds like I might be stuck with a config backup/fresh install/config restore situation now unless someone has a better suggestion.
  • pfSense update

    7
    0 Votes
    7 Posts
    862 Views
    johnpozJ
    your pfblocker and other packages have to be OLD as shit as well... Since packages for 2.2 died a long time ago.. Sorry but no I don't get its working ;) Not when it comes to your security devices.. They need to be kept up to date if you expect to be secure. See it all the time with users, Antivirus is from 3 years ago - but it was working! <rolleyes> Sure it was ;)
  • 2.4.4_p2 unable to retrieve packages

    8
    0 Votes
    8 Posts
    813 Views
    GrimsonG
    @gwaitsi said in 2.4.4_p2 unable to retrieve packages: so smarty, why is it unable to retrieve packages PEBCAK, very obviously.
  • pfsense is unable to check for updates with IPv6 Only setup

    2
    0 Votes
    2 Posts
    309 Views
    jimpJ
    We are aware, IPv6 access for those hosts should be back up in the near future.
  • Pfsense on Futro S900 random restart

    3
    0 Votes
    3 Posts
    716 Views
    B
    Completely reboot No crash report, I have to connect serial port and check the output. thanks
  • Update failed

    10
    0 Votes
    10 Posts
    1k Views
    stephenw10S
    Yes, once it has recovered the config it returns to the install menu so you can install using that. If you have a backup of the config file anyway just go ahead and install there. You can always restore the config after install if you have to. Steve
  • To pfSense or not

    3
    0 Votes
    3 Posts
    642 Views
    chrismacmahonC
    I am new to pfSense and was feeling quite excited. Great, welcome to the club! After trying to install on an old HP G5 and coming across a thread hashing out the debacle over 2.4.4 breaking stuff for people and not being able to get official access to previous version I figured I should ask some questions. We don't allow back access not because it's insecure. We are a security company; each of our updates contains security patches and fixes. It would be irresponsible of us, hurt our customer's relationship and trust with us if we willingly allowed insecure software to be officially distributed. I currently have a Protectii Intel i5 7200U, AES-NI, Barebone. 2.4.4 installed and seems to run great. Approximately how long before this is obsolete and gets broken from an update? No one really know's, We are not going to force you to purchase a new piece of hardware. If something fails because of poor manufacturing that is not our responsibility. The only hardware support we have retired was our 32 bit OS support. We don't intentionally 'break' updates or willing try and cause our customer's pain. If you follow the steps in our posts at time of update; you should be fine. I would recommend you attempt restoring a backup before you are forced to do so. Now is a great time. If you are on 2.4.4 please consider updating to 2.4.4-p2. And if I understand correctly from the other thread if it does stop working at some point, I won't be able to roll back to a previous version (even if I still have the installer in some cases due to packages not being available) to get up and running at least until such a time that I can get newer supported equipment, if that is the route we choose? This is not always the case; the update from 2.4.3 to 2.4.4 we migrated from PHP5.6 to PHP7.2. That was a large project, and we could not keep our packages running both versions of PHP. Most of the time the jump in version, 2.3 to 2.4 allows us to have both package servers running, you would be able to rollback, but again we would prefer you not too, as it's insecure. I am assuming that there would be ample notification if I continue to do my due diligence and stay up with notifications and such? Yes, Please keep in touch: Follow our Twitter Feeds Youtube Channel Our blog sign up for our Newsletter Please become involved more in our forum. Would there be a difference in the above scenario (assuming it is correct) between running the Community Edition or the Paid Support Edition? Yes, and No. The bigger difference is if you had our hardware, we don't have the resources to test every iteration of hardware our customer base uses. We, the Global Support team tests our hardware, updates, new install and packages a multitude of times. We want this to be a smooth process for all of our customer base. The biggest issues we have see "update xxx broke my machine it won't boot now." That is a symptom of our success, it's unfortunately is timing issue. As an OS pfSense is incredibly stable, we see people brag about their large up time. During the up time a component of hardware failed, and it won't work after the power is shut off or rebooted. This is why when you read our update guide, step 1 is to backup, step 2 is have a fallback plan, step 3 is reboot, only after then do we discuss running the backup. The paid support is for you to be able to contact the Global Support team at Netgate. Probably will have more questions, just not experience enough yet to know them. Thanks for your time. I hope I have answered your questions. Please let me know if you have any more.
  • "Recover config.xml" does not trigger reinstallation of packages

    3
    0 Votes
    3 Posts
    391 Views
    RicoR
    Ouch sorry I overlooked that. Thanks for clearing. -Rico
  • PHP ERROR: Type: 64 firewall_nat.php, Line: 37

    2
    0 Votes
    2 Posts
    404 Views
    C
    @cmenghi Solved updating to 2.4.4_2
  • Freshly installed pfSense, however no GUI access?

    3
    0 Votes
    3 Posts
    467 Views
    E
    Still an issue. Lost pfSense GUI connection again, after trying to access Diagnostics > Backup/restore.
  • 0 Votes
    2 Posts
    536 Views
    jimpJ
    Sometimes that happens if you are in the middle of an update when a new snapshot rolls out. Wait a few minutes and try again.
  • Upgraded to 2.4.2_1 But still shows 2.4.2

    20
    0 Votes
    20 Posts
    5k Views
    RicoR
    Same issue maybe? https://forum.netgate.com/topic/138788/no-default-route-after-reboot-using-gateway-groups -Rico
  • SG-3100 all blue lights blinking, no DHCP, no console

    4
    0 Votes
    4 Posts
    3k Views
    G
    I had some trouble with the console on my Windows 10 PC but support I was able to point me to a proper copy of the drivers. Then things misbehaved in the putty session to the console (oddly garbled screen) but a power cycle got me to the menu and a factory reset. I am having a mess of trouble importing a backup from my old pfsense box and support is trying to see if they can possibly massage it to be usable in the SG-3100. I'll update when I hear back from them. Thanks for the reply.
  • pfsense 2.4.4-p2 package issue

    4
    0 Votes
    4 Posts
    645 Views
    RonpfSR
    The check to the left of System Watchdog means it's current. The text would be red if something is wrong.
  • pfSense appears fully functional but doesn't appear to fully boot.

    7
    0 Votes
    7 Posts
    973 Views
    stephenw10S
    We don't usually put out a patch release image for CE but there were a sufficient number of issues with 2.4.4 that we did this time (along with all the additional testing that incurs). P2 is a much smaller patch, installing p1 and upgrading should be painless. Steve
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.