Messages

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

Thanks again.

Michele.

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.

Hi Franco!

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

Thanks a lot.

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

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.

I found a way.
Using the button "Inspect" on the right top of the page, everything becomes clearly visible (tools, ecc.). When you deselect that button and make a page refresh problem appears again.
To tell the truth I never used it before and it has come with one of the latest updates.

Thanks,
Michele.

Hello Franco and thanks for reply.
Well, if a minimize the navigation bar and/or make the whole windows smaller horizzontally or make any other resizing operation the result is the same: I don't see the tools buttons. Besides, when I resize the window horizzontally, text and pictures are somehow split into two parts.
I attached another shot for better comprehending.

Cheers,
Michele.

Hi.
As I just wrote in the object: I noted that on the right side of the GUI tools to manage rules are not visible in Google Chrome while they're in Mozilla Firefox and in IE.
I attached two shots of both browsers just to see the differences (see the red circles).

Is there anyone who knows the reason ot this strange behaviour in Google Chrome and eventually how to solve this little problem?

Thanks and cheers,
Michele.

Noone who faced this problem and tried to solve it?

[suricata: [100148] <Warning> -- [ERRCODE: SC_WARN_DEFAULT_WILL_CHANGE(317)] - in 5.0 the default for decoder event stats will go from 'decoder.<proto>.<event>' to 'decoder.event.<proto>.<event>'. See ticket #2225. To suppress this message, set stats.decoder-events-prefix in the yaml.]

I recently noted this error on Suricata logs:
"suricata: [100148] <Warning> -- [ERRCODE: SC_WARN_DEFAULT_WILL_CHANGE(317)] - in 5.0 the default for decoder event stats will go from 'decoder.<proto>.<event>' to 'decoder.event.<proto>.<event>'. See ticket #2225. To suppress this message, set stats.decoder-events-prefix in the yaml."

I also can't see any packet blocked by suricata so I guess it's not working.

I tried to restart the service but error comes again.

I searched for 2225 ticket and found this for version 4.1.3: "Bug #2225: when stats info dumping in redis,the decoder.ipv4.trunc_pkt can't output.In the same time, in the stats.log this can output" but to tell the truth I did not understand whether I can solve the issue or not.

Is there a way to solve it?

Thanks and cheers.

Michele.

Hi Franco.
Just to let you know that after 19.1.9 update openvpn status is still down on the GUI.

When I first rebooted the firewall it seemed to be ok but after a second reboot the problem is still there. I had to find the process with a "ps auxw | grep openvpn", kill it and then restart openvpn server form the gui.

Thanks a lot.

Cheers,
Michele.

Ok Franco.
I will wait for the fix in 19.1.9 release.

Thanks a lot.

Cheers,
Michele.

Hi Franco,
thanks for reply.

I tried to apply patch with command "opnsense-patch c217bee" but console return me this:  "1 out of 1 hunks failed while patching etc/inc/plugins.inc.d/openvpn.inc".

Am I doing something wrong?

Then sorry but I did't understand what you wrote at the end of your post: you mean patch will be applied with the 19.1.9 opnsense update?

Thanks and cheers,
Michele.

I have two Openvpn servers in the same firewall: OPN1 and OPN2.
Sometimes after a firewall reboot both deamons don't come up and in dashboard they're red. If I try to restart them they don't and logs says that:
"openvpn[76450]: Exiting due to fatal error;
openvpn[76450]: Cannot open TUN/TAP dev /dev/tun1: Device busy (errno=16)
openvpn[76450]: TUN/TAP device ovpns1 exists previously, keep at program end"

I found an old post https://forum.opnsense.org/index.php?topic=6376.0 and there I found the solution to find and kill processes. In that post a bug was opend at Github but I was not able to understand whether the bug had been correct or not.

Is it known why this happens?
Is there a more simply way to make Open VPN deamons come up after a simple firewall reboot (for example for a system update)?

Thanks a lot.

Best regards,
Michele

Hello!
No one can help me to find out whether those rows that keep on filling my system logs are a problem or not?
Does it happen to anyone?

Thanks,

Michele.