Messages

1

22.1 Production Series / Re: Warning on Intrusion Detection logs

« on: June 08, 2022, 04:45:14 pm »

The error messages seem to say that there are errors because stuff isn't enabled.  You could delete these messages from the log file.

I really can't find a way to "delete" those messages, at least via GUI. Anyway my usual goal is to find the reason why I have certain error logs first and then, eventually, find a way to delete them.

Or maybe enable stuff ...

Ok, I could do that: would you be so kind to indicate me how to?

Thanks.

2

22.1 Production Series / Re: Warning on Intrusion Detection logs

« on: June 08, 2022, 03:13:03 pm »

Looks like it's just enabling protocols to monitor for which is not a bad thing unless you explicitly don't want those protocols looked at.

It may be just like that but log messages are indentified as "ERROR".
I'd like to know why these errors come up and how to remove them.

Cheers.

3

22.1 Production Series / Warning on Intrusion Detection logs

« on: June 06, 2022, 12:03:30 pm »

Hi.
I noticed several warnings on Intrusion Detection logs after update to version 22.1.8_1.
Warnings are like these (some examples):

• [ERRCODE: SC_ERR_CONF_YAML_ERROR(242)] - App-Layer protocol http2 enable status not set, so enabling by default.
• [ERRCODE: SC_ERR_CONF_YAML_ERROR(242)] - App-Layer protocol rdp enable status not set, so enabling by default.
• [ERRCODE: SC_ERR_CONF_YAML_ERROR(242)] - App-Layer protocol mqtt enable status not set, so enabling by default.
• [...]

I know those are "just" warnings but do I have to worry about?

Thanks a lot,
Michele

4

22.1 Production Series / Re: Alias based firewall rules doesn't work after upgrade to 22.1.8

« on: May 26, 2022, 04:07:07 pm »

I can confirm the same problem with some aliases. Especially I did have problems with network aliases (e.g. 192.168.20.0/24). Everything started working again after reverting to version 22.1.7_1.
I hope developer team can solve it in newer versions.

Have a nice day,
Michele.

5

Virtual private networks / How to force OpenVPN clients to disconnect after a certain amount of time

« on: October 27, 2021, 05:02:35 pm »

Hi guys.
I have lots of Openvpn clients who leave connections open even if they don't use for hours and some of them also go home leaving VPN connections open!
Is there a way in server or client side or both to setup a timeout so that after e.g. 60 minutes without utilization clients automatically disconnects from server?

Thanks a lot.

Michele.

6

21.1 Legacy Series / Re: Problems after 21.7.1_1 update

« on: June 22, 2021, 03:20:16 pm »

Thanks to all of you guys! 

Cheers,

Michele.

7

21.1 Legacy Series / Re: Problems after 21.7.1_1 update

« on: June 22, 2021, 10:21:35 am »

It looks like it was a browser issue.
I did the update using Google Chrome and had the problems mentioned in my thread.
Then I tried to open the gui with Mozilla Firefox and everything seems to be ok. Update check is ok, alla services are up and running.
Maybe the 21.1.7_1 update did something around the gui and something went wrong...

8

21.1 Legacy Series / Problems after 21.7.1_1 update

« on: June 22, 2021, 10:07:34 am »

I read some other threads and saw that this update caused some problems.
I did the update, something has gone wrong or better, update log in the gui stopped but the firewall did the reboot.
When the firewall rebooted the update check stucks (see image attached).
I tried re-installing the 21.1.7_1 packed with no luck and it seems to not work properly.
I also launched "/usr/local/opnsense/scripts/firmware/health.sh" but everything is ok. I tried to launch it from the gui but it doesn't work.

What else can I do to restore normal behaviour?

Thanks a lot,
Michele.

9

General Discussion / Re: How to set up sarg with opnsense?

« on: September 30, 2020, 07:00:14 pm »

Hi Raxid.
Unfortunately I have no more installations with Sarg and to tell the truth I really can't remember whether I had the plugin in the gui or not.

Sorry not to be able to give you some help.

Michele.

10

20.7 Legacy Series / Re: Upgrade no more available

« on: September 12, 2020, 07:35:56 pm »

Thanks Franco.
I've a couple of machines to be upgraded.
I'll report back.

Cheers,

Michele.

11

20.7 Legacy Series / Re: Upgrade no more available

« on: September 07, 2020, 11:09:41 am »

Ah ok.
So what should I do in case I would face a signature error again?

Thanks again.

Michele.

12

20.7 Legacy Series / Re: Upgrade no more available

« on: September 07, 2020, 10:37:49 am »

Hi Franco!
I reinstalled opnsense package and then I received prompt to upgrade again.
I did upgrade and had no signature error, that's great!
If I should receive signature error on other installs I could simply install opnsense package again?

Anyway thanks a lot for your very precious help!!!

Cheers,

Michele.

13

20.7 Legacy Series / Re: Upgrade no more available

« on: September 07, 2020, 09:57:44 am »

Hi Franco!

The output is https://pkg.opnsense.org/FreeBSD:11:amd64/20.1

Thanks a lot.

14

20.7 Legacy Series / Re: Upgrade no more available

« on: September 07, 2020, 09:26:41 am »

Yes, that's the first action I did, no result.
Then I tried to upgrade from console but still no updates available.

15

20.7 Legacy Series / Upgrade no more available

« on: September 07, 2020, 09:20:22 am »

Hi to everybody.
I'm on 20.1.9_1 version and want to upgrade to 20.7.x.
I tried to upgrade but received the error "no signature found".
I follow the advice of this post https://forum.opnsense.org/index.php?topic=11199.0 where Franco says to delete two files: /usr/local/opnsense/firmware-upgrade and /usr/local/opnsense/firmware-message.
I did that but now when I check for new version, 20.7 is no more proposed, the message simply says that there's no update available on selected mirror.

How can I solve this and upgrade to version 20.7.x?

Thanks a lot,

Michele.