1
21.1 Production Series / Re: Problems after 21.7.1_1 update
« on: Today at 03:20:16 pm »
Thanks to all of you guys! 
Cheers,
Michele.
Cheers,
Michele.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
21.1 Production Series / Re: Problems after 21.7.1_1 update
« on: Today at 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...
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...
3
21.1 Production Series / Problems after 21.7.1_1 update
« on: Today at 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.
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.
4
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.
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.
5
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.
I've a couple of machines to be upgraded.
I'll report back.
Cheers,
Michele.
6
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.
So what should I do in case I would face a signature error again?
Thanks again.
Michele.
7
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.
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.
9
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.
Then I tried to upgrade from console but still no updates available.
10
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.
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.
11
19.7 Legacy Series / Re: GUI on Google Chrome: tools to move, delete, edit, clone rules not visible
« on: September 25, 2019, 10:49:29 am »
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.
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.
12
19.7 Legacy Series / Re: GUI on Google Chrome: tools to move, delete, edit, clone rules not visible
« on: September 25, 2019, 09:23:48 am »
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.
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.
13
19.7 Legacy Series / GUI on Google Chrome: tools to move, delete, edit, clone rules not visible
« on: September 23, 2019, 04:23:09 pm »
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.
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.
14
19.7 Legacy Series / Re: Error on Suricata 4.1.4_4 Logs
« on: September 23, 2019, 04:08:42 pm »
Noone who faced this problem and tried to solve it?
15
19.7 Legacy Series / Error on Suricata 4.1.4_4 Logs
« on: September 12, 2019, 04:37:13 pm »
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.
"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.