Messages

ALL: 

  Just wanted to close out my additions to this thread.  Just like the OP, I ended up removing all traces of ZenArmor and then was able to successfully update to 24.1.  Current info is now:

OPNsense 24.1.1-amd64
FreeBSD 13.2-RELEASE-p9
OpenSSL 3.0.13

Will think about putting ZenArmor back on later.

Thanks to all.

Hi Cookiemonster,

  I understand and appreciate your point.  I will attempt to take matters into my own hands.  I was hoping others on here would have offered some additional insights - am guessing not very many people use ZenArmor like I am using.  For now, I will plan to proceed with what I have described and hope for the best.

Thanks.

Hi cookiemonster.  I appreciate the feedback, but am I and the OP the only ones having this problem?  Is this a ZenArmor-related-only issue?  In other words, for those who run ZenArmor with OPNsense, this 'bug' is going to prevent any patches from being installed?  Just trying to find out more as to what's going on.

Thanks.

Hello everyone,

  I came across this thread and am in a similar situation.  I am currently at:

OPNsense 23.7.12_5-amd64
FreeBSD 13.2-RELEASE-p7
OpenSSL 1.1.1w

  And when I check for updates it wants to uninstall nearly every Opnsense package.  I have never had any problems with applying updates before - total first.  I tried disabling the ZenArmor repo (/usr/local/etc/pkg/repos/SunnyValley.conf) - no change.  I saw the prior person said he had to uninstall Zenarmor (which I have installed and configured).  All of this has been running fine for over a year now and I do not want to lose any of current configs.  If I do a Zenarmor backup and download that file, uninstall all Zenarmor pkgs, will Opnsense updates then work (assuming yes) and then can I reinstall Zenarmor and reapply my backed up config to get me back where I am now, but on the latest version of Opnsense?

Kindly requesting assistance on best way to solve this.  Additionally, is there any way to prevent this from happening again in the future?

Thanks.

ALL:  Thank you very much for the replies -- all very helpful.  I do understand the continual bot scanning of IPs and all.  I just tried to access my public IP from my cell phone and nothing came up.  I am assuming the reason why it came up from my LAN is because of the already mentioned reason from above.  Very confusing if you're not aware of that clause.  I think we are OK unless anyone else would like to add anything I may have missed.

Very good questions.  so, yes, it is my public IP that is the IP and when I go to it, I am presented with the OPNsense GUI login page.  There are IPs hitting that address nearly every second.  Is there a way to disable WAN access to the OPNsense login page so as to reduce the attack vector?

Hello,

  New to OPNsense and so far I LOVE IT!!!!!!!  In looking through the blocked traffic on my firewall log and after doing a bunch of research, it appears there is a public IP address (that I did not set) to my OPNsense firewall appliance.  It begins with 96.x.x.x.  I scoured through all of my devices for the IP and MAC address and finally found that it was assigned to the WAN port on my device.  What is this for and how do I disable it?  I have put rules in place to block all traffic to and from it because I am not comfortable with a web server IP address communicating on the open web without my knowledge.