Uploaded image for project: 'TrueNAS'
  1. TrueNAS
  2. NAS-105472

invesigate pf.conf.block usefulness

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Done (View Workflow)
    • Priority: Low
    • Resolution: Complete
    • Affects Version/s: TrueNAS 11.3-U2
    • Fix Version/s: None
    • Component/s: HA
    • Labels:

      Description

      TrueNAS HA systems implement a global lock on all CARP interfaces until the system is fully booted. This means no traffic will work on the VIP until the system is "ready".

      Since pf.conf.block is configured to only block on the VIP addresses and is only enabled on the passive storage controller, nothing is really being blocked because the VIP mac address will only exist on a single switchport for the active controller.

      I need to investigate if this code is still useful.

        Attachments

          Attachments

            JEditor

              Activity

                People

                Assignee:
                caleb Caleb St. John
                Reporter:
                caleb Caleb St. John
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: