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

    Thread locking

    Scheduled Pinned Locked Moved Forum Feedback
    5 Posts 4 Posters 1.0k 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.
    • lohphatL
      lohphat
      last edited by

      I don't understand why a relevant thread would be locked. Yes it was started 4+ years ago but 1) the information contained in it seemed to have solved my issue and 2) I had more information relevant to the issue to post. Locking the thread would just unnecessarily fragment the the dialog for future problem solution seekers if the information were spread across various threads.

      https://forum.netgate.com/topic/83844/t-mobile-wifi-calling

      SG-3100 24.11-RELEASE (arm) | Avahi (2.2_6) | ntopng (5.6.0_1) | openvpn-client-export (1.9.5) | pfBlockerNG-devel (3.2.1_20) | System_Patches (2.2.20_5)

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

        Because things change. Old bugs long-fixed no longer apply, etc. You can always start a new thread and link to the locked thread just like you did here.

        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
        • lohphatL
          lohphat
          last edited by

          I get that, were it relevant to that thread topic. It's still a problem for users not familiar with the problem. Changing the NAT scrubbing setting fixes the instability on current releases. The only thing "wrong" with the thread is that it's 4 years old, however the topic is still current.

          Just trying to understand the logic.

          SG-3100 24.11-RELEASE (arm) | Avahi (2.2_6) | ntopng (5.6.0_1) | openvpn-client-export (1.9.5) | pfBlockerNG-devel (3.2.1_20) | System_Patches (2.2.20_5)

          1 Reply Last reply Reply Quote 0
          • chrismacmahonC
            chrismacmahon
            last edited by

            99% of the time, when someone comments on an older thread, it's either, SPAM, a bot, or someone wanting to start a flame war.

            In the past 4 years we have changed MANY different versions of pfSense including StrongSwan. The original troubleshooting steps might be valid, chances are they won't apply to the issue at hand.

            Need help fast? Our support is available 24/7 https://www.netgate.com/support/

            Do Not PM For Help!

            1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator
              last edited by johnpoz

              In the 10 some years I have been here I would say its more like 99.9% of the time ;) The only thing that gets posted on 4 year old threads is junk.. 4 years ago wold of been what version of pfsense... The changes in pfsense since are going to be drastic...

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

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