Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Uptime 861 Days

    Hardware
    4
    6
    1302
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      FJSchrankJr last edited by

      For anyone who questions the reliability of pfSense, or the Watchguard for the hardware platform take a look at this:

      Uptime: 861 days, 15:51

      Yes, it's behind UPS Systems and auto start diesel generators but it goes to show you that a well configured pfSense is rock solid. This firewall pushes a lot of traffic too for our data center.

      Remember, if you're running on the Watchguard or any SSD/Flash based platform disable log writing to disk or you will eventually wear out the flash. Oh, and keep dust out of the processor and fans.

      Haven't been active here lately, just sharing. Hello to all!

      FJS - Embedded Systems Engineer
      Pictures are worth a thousand words, but <u>posting config.xml backups are worth 10,000</u>.  Alter the IPs, change anything revealing but leave subnets intact. Use find and replace. Please try to keep it brief on the description.
      ALWAYS disable TSO  & LRO EXCEPT CHKSUM IF SUPPORTED. TSO/LRO breaks traffic, pf scrub and this goes for any passive device inline

      1 Reply Last reply Reply Quote 0
      • stephenw10
        stephenw10 Netgate Administrator last edited by

        Are you still running 1.2.3 then? Or is that since 2.0 was released? (17/9/11) Edit: Nope that's 872 days.  ;)

        Steve

        1 Reply Last reply Reply Quote 0
        • S
          Sifter last edited by

          Any way you could provide a screenshot?

          1 Reply Last reply Reply Quote 0
          • F
            FJSchrankJr last edited by

            Hey Steve, long time no chat! Hope your well. Yes, now 862  ;)

            screen shot attached… quiet today on the traffic but at times it pushes 25k states+. In fact, during it's operation, it's been under numerous DoS attacks.


            FJS - Embedded Systems Engineer
            Pictures are worth a thousand words, but <u>posting config.xml backups are worth 10,000</u>.  Alter the IPs, change anything revealing but leave subnets intact. Use find and replace. Please try to keep it brief on the description.
            ALWAYS disable TSO  & LRO EXCEPT CHKSUM IF SUPPORTED. TSO/LRO breaks traffic, pf scrub and this goes for any passive device inline

            1 Reply Last reply Reply Quote 0
            • P
              podilarius last edited by

              I was on 2.0-Release for 720 days before upgrade to 2.1-Release (for IPv6 and CARP cluster). It is on a Supermicro server. Running solid!!!

              1 Reply Last reply Reply Quote 0
              • F
                FJSchrankJr last edited by

                @podilarius:

                I was on 2.0-Release for 720 days before upgrade to 2.1-Release (for IPv6 and CARP cluster). It is on a Supermicro server. Running solid!!!

                That's a nice run! I've avoided updates, upgrades, as many changes as possible, disabling NAT reflection on any UDP traffic like DNS, keeping the fans and mb clean, good equipment room temp, stable power, and no log writing to flash.

                FJS - Embedded Systems Engineer
                Pictures are worth a thousand words, but <u>posting config.xml backups are worth 10,000</u>.  Alter the IPs, change anything revealing but leave subnets intact. Use find and replace. Please try to keep it brief on the description.
                ALWAYS disable TSO  & LRO EXCEPT CHKSUM IF SUPPORTED. TSO/LRO breaks traffic, pf scrub and this goes for any passive device inline

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post