Messages

Slow speed just indicates mismatch in NIC handling/checksum failures, etc.


Cheers,
Franco

Fix by forcing a reinstall of the core package?

# opnsense-revert opnsense


Cheers,
Franco

Maybe it's throttling itself making it seem to use 100% CPU when it doesn't? Have you looked into changing powerd settings?

Before chasing ghosts please make sure to set our powerd settings in a way that the system can't throttle its CPU to MAKE IT SEEM that CPU is 100%.  ::)


Cheers,
Franco

Don't forget that logging needs to be enabled for each pass rule as it otherwise won't log.

Loggin has some defaults, but never goes out of its way to log things that a user-based rule catches where logging is disabled.


Cheers,
Franco

Not entirely. From the command line I would try to see how the oversize ping goes:

# ping -c4 -s1500 pkg.opnsense.org
# ping6 -c4 -s1500 pkg.opnsense.org

Of course it's difficult to tell if pkg utility will use IPv4 or IPv6. As a rule of thumb it should prefer IPv6 unless that has been turned off or IPv4 is preferred (system: settings: general). And you need to use the mirror you set up if it's not the default.


Cheers,
Franco

Usually it takes a week or two to prepare, best to look out for announcements giving the green light.


Cheers,
Franco

What would be "a small amount" in your particular case?

We are discussing ideas quite often, but nothing concrete surfaced yet. If there is a demand there can be room for more than just "community" and "business" release types. ;)


Cheers,
Franco

Problems that disappear for no reason usually come back for the same reason. Keep an eye out for this. :)


Cheers,
Franco

One other thing that I noticed that I can't figure out and could be related to me being double nat'd (22.1b behind 21.7.7 production)...URL Table aliases in the firewall from spamhaus aren't populating.  No messages on that one.  If no one else reports it, chalk it up as a local issue to my setup (the URL is not being blocked).  Can that be manually triggered for testing?  Or where to check...nothing in system log.  Thx!

Not an expert on this subject depending on what interval that alias has been set to resolve it could take a while to resolve (check settings first).


Cheers,
Franco

Ok, found it https://github.com/opnsense/src/commit/a35bc248fd6

We try to fix /var MFS issues, but they do pop up quite frequently with newly added plugins for example.

After some head-banging it looks as if /root directory on FreeBSD 13 has changed permission to 750 away from 755, which means vnstat user cannot get to /root/var anymore. It's easily fixed, but not very nice and overwritten on next base update:

# chmod 755 /root

We will need to discuss what to do internally...


Cheers,
Franco

Frohes (und gesundes) neues Jahr! <3

The possibility to move certain types of plugins to community version was discussed and not generally disagreed upon, but in order to do so we do need to provide new business plugins to keep the balance so that might mean after 1-2 years something can be made available. Things like central management, however, will probably not be available in the community version at all.


Cheers,
Franco

That's still gateway monitoring code in action:

2022-01-13T15:04:07   Error   opnsense   /usr/local/etc/rc.newwanipv6: Choose to bind VODAFONE_DHCP on since we could not find a proper match.

Not sure why it doesn't return an address. What does ifconfig say to VODAFONE_DHCP interface? Any IP at all? Coming and going?


Cheers,
Franco

I think this can be reproduced with the information you've given. I had to rework the /var link stuff for mount points that interfere like is the case on ZFS. Let me take a look. :)

The whole /var/lib/vnstat business is a bit fishy though, at one point the plugin might try to "rm -rf /var/lib/vnstat" which is bad news when /var/lib/vnstat is a link to begin with.

In 2022, I can't much recommend /var MFS option anymore unfortunately. It might go away in the not so distant future.


Cheers,
Franco