Recent posts

#1

26.7 Series / Re: how to recover using an ol...

Last post by defaultuserfoo - Today at 04:55:15 PM

You could have posted at least a screenshot of the supposedly messed up rules after migration.

"It doesn't work" is not very helpful.

I'm not sure if it's a good idea to publish the firewall rules for everyone to see.  And unless you would know excatly in detail what the current rules are supposed to do, you won't be able to tell if the so-called migration was successful.  The only way to know for sure would be to try them in production.

#2

26.7 Series / Re: how to recover using an ol...

Last post by defaultuserfoo - Today at 04:50:39 PM

It means that all the rules need to be redone because migrating them doesn't work

It seems you are in the minority of users experiencing the impossibility of migrating firewall and NAT rules.

Perhaps you could invest time working through your issue and find a way to restore your old configuration file and get it working in a way where information already provided has not worked.

Considering the pain this has caused you, and in the interest that another user may some day befall your predicament, you could document the process you used and post it to the list, so they may also benefit from your experience.

The router is currently working again with 25.7.11 and an old configuration (from February) that needed only minor adjustments.  In a while, I'll use the spare machine to create a copy and to figure out if the rules can be converted.  Maybe I can document what happens then.

#3

Development and Code Review / Free GeoIP Database to use wit...

Last post by Tonton Jo - Today at 04:33:15 PM

Hi!

Not sure if it's the right place, but i wanted to share this:

I've vibecoded a script that generate a geoIP database from scratch that matches the requirements in terms of format for Opnsense.

• It's fully open sources
• Based on the internet registries database
• Automatically updated everyday using a workflow

The database here will be automatically updated:
https://github.com/Tontonjo/opnsense/releases/download/geoip/GeoLite2-Country-CSV.zip

Find the scripts for both bash and Powershell usage if you need to self-host here:
https://github.com/Tontonjo/opnsense/tree/main/geoip

Let me know if you find this usefull :)

Regards

Jo

#4

26.7 Series / Re: how to recover using an ol...

Last post by Kinerg - Today at 04:19:59 PM

You could have posted at least a screenshot of the supposedly messed up rules after migration.

"It doesn't work" is not very helpful.

#5

26.7 Series / Re: how to recover using an ol...

Last post by defaultuserfoo - Today at 04:02:50 PM

No. It's not working.

Instead it was made to appear something easy to do.  But it is isn't.

This reminds of the fatal blow Debian struck their users with their stupid brokenarch.  I had been using Debian for about 15 years and then the devs decided to comepletely mess it up, and it was forseeable that the problems would continue to exist in the next release.  So I switched away from Debian.

This is the same crap.  If I knew a good alternative to OPNsense I would switch.

As someone who is using both Debian and OPNsense I totally disagree with you :)

That's up to you.  You probably weren't using Debian when they created the problem.

We've already had a discussion about the release notes.  The devs refuse to make good release notes.

NOFI but IMHO it's you and not the software...

Maybe try something OpenWRT based or simply buy stuff like TP-Link Omada or Ubiquiti UniFi or HPE Aruba ?!

I don't know about OpenWRT.  TP-Link is fine for simple stuff like unmanaged switches.  Anything that requires firmware more advanced than that you can only stay away from.  Ubiquity totally sucks; they can't even write documentation.  Aruba makes nice switches and access points, and I have an HP router that comes with outstanding documentation which I took out of service because it's too loud.  Apparently they have put Aruba stickers on their routers.  Maybe those would be an option, but they might be expensive.  Do they do wireguard now?

#6

Zenarmor (Sensei) / Seeing a new "threat" in my li...

Last post by Greg_E - Today at 03:57:28 PM

I'm seeing this in my "threat" list listed as newly registered sites and pointing to resources.omni-sync.io. I think it might be something to do with Adobe Creative Cloud, but not certain. Currently listed as green and passing. I get this from a web search:

Search Assist




resources.omni-sync.io is likely a web address associated with OmniSync, which provides tools and services for syncing and managing tasks across various devices and applications. It may offer resources related to their products, such as guides, support, and updates for users.
 manage.sync.omnigroup.com
 omnisync.ai

Just wondering if anyone else has seen this, and if you traced it back to a certain application.

#7

Development and Code Review / Re: Issue on sysutils/sysinfo ...

Last post by franco - Today at 03:36:30 PM

I'll try to sync the ports tree tomorrow.

Locally you can use this in the port directory:

# make makesum


Cheers,
Franco

#8

26.7 Series / Re: Upgrade from 26.7.5 to 26....

Last post by franco - Today at 03:34:51 PM

Just wait for 26.7.7_7 hotfix ;)

J/k, I think we can do without a hotfix in .7. Happy to hear the issue hasn't returned.


Cheers,
Franco

#9

26.7 Series / Re: PPPoE over an unassigned V...

Last post by franco - Today at 03:33:02 PM

@fbantgat7 Your issue is likely not related to PPPoE since that part is fine, but on top negotiation changed in DHCPv6 as it seems.  This could be a provider change.  I'm not aware of regressions in DHCPv6 connectivity in 26.7.x.


Cheers,
Franco

#10

26.7 Series / Re: missing wireguard automati...

Last post by freejack - Today at 03:29:41 PM

Thanks for checking it out. Here also for completeness the instance settings -- disable route not set, as documented in the tutorial.

The only thing non-vanilla about my setup, beside being freshly created with 26.7, is the "disable source nat rule generation", as I do not need these for my fully route-able use case.