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

    Need to reboot pfsense 2.3.4 weekly

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 2 Posters 457 Views
    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.
    • D
      derell
      last edited by

      I'm running pfsense 2.3.4 on an IBM System X3650 Hardware Platform, 2 x Quad Core, 16gb Ram.  The only customizations that have been done are to specify a static IP for the Lan & Wan, Enable DHCP & Forward a couple ports for my NEC Phone System that uses SIP Trunks.  I have also setup OpenVPN.  After a period of time, roughly a week all of a sudden incoming phone calls ring our phone but we cant hear anyone nor can they here us were told.  Within a few minutes of that happening computers won't receive dhcp addresses and it seems as if everything on the pfsense router just goes downhill.  A quick reboot and all work great for about another week.  I'm far from an expert and am looking for suggestions as to where to look to troubleshoot issue.  Possibly just a problem with 2.3.4?  Don't know but would appreciate any help.  The only package that I've added is the OpenVPN Client Export package.  Thanks !

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        No, we are all not rebooting our 2.3.4 nodes weekly.

        Can you get to the webgui and look around when it acts up before you reboot it?

        Look at the usual things. disk space, ram, mbufs, etc.

        If you can get a status output: https://firewall_ip_address/status.php download that file before rebooting next time so you have one while it's failed.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.