OPNsense Forum
Archive => 22.7 Legacy Series => Topic started by: Spiky_Gladiator on February 15, 2023, 09:41:25 pm
-
Hi,
I have noticed a couple of errors when my OPNSense is booting up and I'm not sure if it's something that I should worry about or just ignore them. They are:
PFLog0: Permanently Promiscuous Mode Enabled
I did some research on this error and it looks like it's some kind of a software switch to deactivate/activate internet connection or something like that as the only posts I came across were talking about the above going in a loop from Enable to Disabled every couple of seconds causing network distruptions.
Error in early script "Carp"
Generating Configuration: Carp socket missing
Looking online for the Carp protocol brings up failovers and redundancy, is this feature used by default in OPNSense ? In which cases would I need to use CARP protocol and finally can I just ignore this error ?
Generating Configuration: Configd socket missing
In combination with the above error, the one from below I found somewhere in the Web GUI:
Error Configd.py [Some Type of ID] returned exit status 1
I have checked and it looks like Configd.py is some type of backend for OPNSense which passes actions from the frontend (Web GUI) to the backend\firewall itself. The above error indicates that Configd.py have errored out and terminated to what I think is its backend ? Worrisome for sure.
I have successfully setup my network how I want and everything seems to be in order but the above errors worry me that something with the Firewall itself might be broken e.g WAN rules allowing someone to connect to my OPNSense where otherwise it would be secure to reject any connection attempts to OPNSense and so on.
Will someone please give me a hand with this as I tried to search and search online but can't find any solution to the above errors.
Thanks
-
We've seen this too and thought to have deployed multiple fixes. The only theory we have is that the socket in question appears and then disappears again for a few seconds for whatever reason. it only happens on slower hardware as far as we can tell, but operational impact is minimal as the socket eventually comes up fine.
Cheers,
Franco
-
We've seen this too and thought to have deployed multiple fixes. The only theory we have is that the socket in question appears and then disappears again for a few seconds for whatever reason. it only happens on slower hardware as far as we can tell, but operational impact is minimal as the socket eventually comes up fine.
Cheers,
Franco
Is there any way I can check if the sockets are working fine, just to be sure ? Perhaps checking if the socket's service is currently running would do the trick ?
Which error are you talking about in your reply, the carrp and Configd or the python error for Configd.py ? Should I be concerned for any of the listed errors ? As of right now, I'm stuck in the limbo with the said errors as I'm not quite sure what they mean and if I should be concerned about them.