Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
22.1 Legacy Series
»
Gateway offline after upgrade to 22.1.6 but fixed it (in a weird way?)
« previous
next »
Print
Pages: [
1
]
Author
Topic: Gateway offline after upgrade to 22.1.6 but fixed it (in a weird way?) (Read 940 times)
JT21
Newbie
Posts: 1
Karma: 0
Gateway offline after upgrade to 22.1.6 but fixed it (in a weird way?)
«
on:
April 29, 2022, 06:25:57 am »
I upgraded to 22.1.6 from 22.1.5 and this upgrade made it so it showed my gateway offline and here are some symptoms I had noticed:
Part of my network devices / computers worked (weird?)
The opnsense box was able to reach the internet just fine - again gateway showed offline.
Here's what I tried to do to fix it (not in this exact order but did try all of these listed):
Reboot ISP modem
Reboot opnsense box
Disabled gateway monitoring (so that it would just be online no matter what)
Upgraded to the latest development version... because why not? I was already at the point of ready to just re-install and restore config...
What fixed it so far because everything else listed above did not work... I disabled my OPT1 interface. This, this for some reason made my gateway come back online. I then re-enabled my OPT1 interface and the internet at this point is still working. I wish I knew why this worked but at this point I'm glad I don't have to re-install and restore my config.
Just thought I'd share my experience with my upgrade here in case anyone else has a similar issue upgrading to 22.1.6. If this is some how a known issue I was not able to locate any threads for this kind of issue with this kind of fix (my searching skills could be rusty).
I do have a question, now that I'm on the latest development version... not that I sometimes don't mind being on the bleeding edge... is it possible to switch back to the community version when the official release of 22.7.x is ready for release? Thanks.
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
22.1 Legacy Series
»
Gateway offline after upgrade to 22.1.6 but fixed it (in a weird way?)