20.7-r1 version has bugs, when i check update and upgrade, then system down and auto reboot. it is can't normal work.
Same here, it tells me its EOL though.
This is intentional, see this thread:
https://forum.opnsense.org/index.php?topic=18199.msg82605#msg82605
Just don't click on it and your system won't reboot. You can check if you are running the latest version in the dashboard.
Kind regards,
Patrick
I'm not sure what to do here: no screenshots; "20.7-r1" does not exist. Vague suggestion that it is actually the development version and no steps to reproduce. ;)
Cheers,
Franco
They are probably puzzled by this just like me.
And when you click on "Upgrade now" the system will reboot but the message won't go away, so rinse and repeat ...
Room for UX improvement. ;)
I have to disagree. If people use the development version and report defects that are used to develop and test the software it doesn't help that much, especially if the reports are not coherent.
It's super easy to go to the dashboard and copy and paste the version info into a report. It gives a lot of context. "20.7-r1" on the other hand is a typo that gives only a slight indication as to what is going on.
Cheers,
Franco
I wouldn't argue that those one line "reports" are very helpful ;)
Thanks pmhausen, solved :)
@franco It is no typo, besides the -, thats why i deemed 20.7.r1 to be sufficient. Its pretty apparent if you use this release and its good to know its intentional and not a defect.
Its was also small enough and not too inconvenient otherwise that report would have landed in the github issues.
Regards,
MartB
Guys, the versions are either "20.7.r_13" or "20.7.r1" from the dashboard system info. Depending on that version number the report has a different context. Help is impossible until one of those version numbers is actually appearing in this thread with the corresponding supposed oddity in behaviour.
Cheers,
Franco
Updated by System - Firmware -Updates
Ok, now we're talking.
You are currently using the development version. It will keep asking for an upgrade for testing purposes.
To go to the production release:
System: Settings: Firmware -> Settings -> select Production release and save. Use blue box to check for updates, click "update" in blue box... done ;)
Cheers,
Franco
I just put it in to help. In my case I'm already waiting for the final version. Thank you
I assume this is the latest devel version:
OPNsense 20.7.r_13-amd64
FreeBSD 12.1-RELEASE-p7-HBSD
OpenSSL 1.1.1g 21 Apr 2020
Which is newer than 20.7-r1?
When I switch back and forth to production/development and check for upgrade I am prompted with the following:
This software release has reached its designated end of life. The next major release is: 20.7.r1
I know I should have waited until the release, but my curiosity got the best of me :)
Once released I assume I will need to do is switch back to Production releases and perform the upgrade over the RCx and move on?
Thanks
Quote from: guyp2k on July 24, 2020, 05:26:07 PM
I assume this is the latest devel version:
OPNsense 20.7.r_13-amd64
FreeBSD 12.1-RELEASE-p7-HBSD
OpenSSL 1.1.1g 21 Apr 2020
Which is newer than 20.7-r1?
When I switch back and forth to production/development and check for upgrade I am prompted with the following:
This software release has reached its designated end of life. The next major release is: 20.7.r1
I know I should have waited until the release, but my curiosity got the best of me :)
Once released I assume I will need to do is switch back to Production releases and perform the upgrade over the RCx and move on?
Thanks
Yes, for now you are on the latest version.
The latest development version... it doesn't matter if you switch now to production or wait for 20.7. You still have to switch from development version to production version at some point unless you want to stay on the development version.
The system keeps restarting automatically and cannot work at all
Are you running Sensei?
Quote from: mimugmail on July 25, 2020, 11:21:15 AM
Are you running Sensei?
whats Sensei? it is new install system. no running other.
If it helps I have active suricata in the wan and sensei in the lan and updated without any problem.
Same here, have Sensei runnin on LAN however, after I upgraded to the RC Sensei packet manager would not start had to do the following:
pkg remove os-sunnyvalley-devel
pkg install os-sunnyvalley-devel
pkg install -f os-sensei
Just updated, no issues to report. Headless configuration here...so be aware it does take a good several minutes (didn't time it but seemed like between 5 and 10) for the server to come back online.
Big thanks to the devs!
EDIT: Did discover I can't route firewall rules to external syslog...not sure though if this is a new problem. Posted here: https://forum.opnsense.org/index.php?topic=18257.0
I had my OPNSense in a reboot loop. Pulled the power cable and then it was booting normal.
However I experience a lot less system load. Was 0.4-0.6 before, now its 0.2-0.3
Actually not quite sure, but does IDS now show the stats.log under Log File or is my config f*** up?