Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
O
OpnSense
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kulya
OpnSense
Commits
f1cedb7c
Commit
f1cedb7c
authored
Jan 19, 2016
by
Franco Fichtner
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
firmware: remove EOL message, we are on 16.1 now
parent
f646d448
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
27 deletions
+0
-27
firmware-message
src/opnsense/firmware-message
+0
-27
No files found.
src/opnsense/firmware-message
deleted
100644 → 0
View file @
f646d448
<p>Hello trusty friend,</p>
<p>As with all things in life, the 15.7 series of OPNsense is nearing its
inevitable end. As such it will not receive any more updates, but the
upgrade to the new 16.1 series is seamless, except for the following
points:</p>
<p><ul><li>The FreeBSD version changes from 10.1 to 10.2, mainly for driver
updates and general sanity. <strong>If you're running Hyper-V, your installed
disk may change from <em>/dev/ada0</em> to <em>/dev/da0</em> and the system
will not boot as a consequence</strong>. You can fix this by manually editing
<em>/etc/fstab</em> before performing the major upgrade. A reinstall using the
import configuration and quick/easy install will work just as well.</li>
<li>The captive portal implementation has been completely rewritten.
<strong>Your old setup won't be converted and thus will not come back
up</strong>. Reconfiguring the captive portal, however, will be relatively
easy.</li>
<li>Due to kernel interface changes going from 10.1 to 10.2 <strong>plugins
or custom-built kernel modules may stop working</strong>. Reinstalling the
offending packages from the firmware pages or recompiling custom additions
against the <em>stable/16.1</em> source branch will resolve this
problem.</li></ul></p>
<p>Please heed these points carefully before upgrading. Backup your configs,
preview the new version via the live CD or in a virtual machine. Create
snapshots. If all else fails, report back
<a href="https://forum.opnsense.org/" target="_blank">in the forums</a> for
assistance. You don't have to do this on your own. :)</p>
<p><em>Brave Badger</em>, you've served us well.</p>
<p>See you on the other side,<br>Your OPNsense team</p>
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment