Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
20.7 Legacy Series
»
OPNSENSE AWESOME
« previous
next »
Print
Pages: [
1
]
Author
Topic: OPNSENSE AWESOME (Read 2011 times)
ThyOnlySandman
Jr. Member
Posts: 85
Karma: 4
OPNSENSE AWESOME
«
on:
September 19, 2020, 10:32:15 pm »
Having played / used Opnsense for ~4 months I just stopping by to share how awesome I think it is...
Coming from having an environment with Cisco FMC / FTD is night and day. The irony.
Recently I did upgrade from 20.1.9 to to 20.7.2. Using VMware I do have vmx interfaces and did run into known netmap issue with both Sensei + Suricata. Following
https://www.sunnyvalley.io/post/opnsense-kernel-netmap-status
I was able to fix. (running: opnsense-update -kr 20.7.2-netmap)
When I first tested it out I was foolish and only gave opnsense a 20GB disk. So part of this upgrade to 20.7 was also to migrate to a fresh install. This is what got me even happier with opnsense today to make this post. Doing a full backup / restore to new VM with 60GB disk worked flawlessly. Everything restored except for disable hardware offloads from what I can tell. And I am using quite few plugins. Even the mismatching Vmware interfaces restored just in the order I wanted. Just pure awesome.
Also briefly share that on my lab environment which is 2x Dell PER710s with Dual X5650s running vmware 2 node VSAN cluster the Vmotion / failover also works flawlessly. Quite pleased with Opnsense.
Thank you Devs!
Logged
ThyOnlySandman
Jr. Member
Posts: 85
Karma: 4
Re: OPNSENSE AWESOME
«
Reply #1 on:
September 19, 2020, 11:43:32 pm »
Share few things I'm noticing.
The GEOIP aliases do appear to have a glitch. I'm using them via few inbound rules. Had traffic getting blocked. Tried updating / applying rules, moving rules order for refresh, re-running apply on GEOIP.
Quick search landed me here:
https://forum.opnsense.org/index.php?topic=18350.0
Which suggested to just create new alias / reapply to rule. Now working.
Also share that Sensei 1.6 restore doesn't appear to restore license info properly. Had to reapply key - This maybe excepted behavior as it was a new Opnsense. Regardless - after re-activation all my config / policies / whitelist intact.
Just to clarify I did not do an import of config install to 20.7.2. I upgraded my old Opnsense to 20.7.2 (+ 20.7.2-netmap) + , got backup, and restore to new VM 20.7.2 (+ 20.7.2-netmap).
I'll explore more and share any other findings. TTFN
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
20.7 Legacy Series
»
OPNSENSE AWESOME