Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    1. Home
    2. Tags
    3. systempatches
    Log in to post
    • All categories
    • C

      [Crash Report] - Crash after update from 2.6.0 to 2.7.0

      Watching Ignoring Scheduled Pinned Locked Moved General pfSense Questions crash 2.7.0 systempatches update
      3
      0 Votes
      3 Posts
      701 Views
      C

      @stephenw10 said in [Crash Report] - Crash after update from 2.6.0 to 2.7.0:

      Which is fixed in 2.7.2.

      Cool - thank you. As I just wrote in my edit I managed to upgrade it to 2.7.2, so it probably won't happen again.

    • JonathanLeeJ

      Patches update

      Watching Ignoring Scheduled Pinned Locked Moved Development patch systempatches
      13
      0 Votes
      13 Posts
      2k Views
      M

      @michmoor said in Patches update:

      Yep. Sorry if that wasnt clear.
      I am doing full MITM.

      Np, I was just trying to understand :)

      @michmoor said in Patches update:

      If you rely only on the internal redirect then pfsense points back to itself on the management port (firewall.example.com:443) .
      The problem of course is that in order to serve the page you must make your management port accessible to all LAN clients. That means making management accessible to all LAN clients. The only workaround is to use an external webserver that has php code on it to interrupt whats being sent to it from pfsense

      Now I see what you meant, yes, indeed that would be a problem.. Using an external server for that solves this problem.

    • S

      System_patches

      Watching Ignoring Scheduled Pinned Locked Moved pfSense Packages systempatches
      1
      0 Votes
      1 Posts
      964 Views
      No one has replied