Thread locking
-
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
-
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.
-
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.
-
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.
-
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...
