Messages

I upgraded from 24.1.10_8 to 24.7.2 and I noticed that the Insight Aggregator service is not running. Looking at the logs I see this

Error   flowd_aggregate.py   flowd aggregate died with message Traceback (most recent call last): File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 160, in run aggregate_flowd(self.config, do_vacuum) File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 80, in aggregate_flowd stream_agg_object.add(copy.copy(flow_record)) File "/usr/local/opnsense/scripts/netflow/lib/aggregates/source.py", line 73, in add super(FlowSourceAddrTotals, self).add(flow) File "/usr/local/opnsense/scripts/netflow/lib/aggregates/__init__.py", line 185, in add self._update_cur.execute(self._update_stmt, flow) sqlite3.DatabaseError: database disk image is malformed

Update:
Resetting the netflow data solved it.

Consider that the DNS for Proton is on a private IP 10.2.0.1. While setting up my FW rules I noticed that on this page:

https://docs.opnsense.org/manual/how-tos/wireguard-selective-routing.html

one of the rule only routes traffic with destination outside the RFC1918_Networks and that excludes access to Proton DNS so you need to change it or create one specifically for the DNS.

I just switched to Wireguard and it's working well. Now I want to create a Monit rule to restart it in case it dies. Maybe I'm missing something but I don't see a pid file in /var/run.

How else can I monitor if it's running?

Fair enough, I'll try that. Thanks.

Thanks for the reply. My issue with not having the interface as binding option is that my WAN is assigned through DHCP (cable home connection). Then I use Cloudflare dynamic DNS to resolve the name which I use for remote connections. The IP hasn't changed in almost two years, but there is always a chance it will.

What's the advantage of using this instead of the "old way". I have 2 different servers running on different ports just fine. Also why in the instance config page I can't select a bind interface instead of an IP address.

Any undesirable interaction between the new version and AdGuard to be aware of?

Updated without issues. Here's my config:

Unbound on LAN interfaces standard port 53
AdGuard on dedicated VIP on port 53 using 127.0.0.1 ad upstream DNS
DHCP pointing to AdGuard VIP as DNS

If I have AdGuard configured to use a dedicated VIP on port 53, forwarding queries to Unbound on 127.0.0.1:53, will this update break it?

I'm using an old CloudKey Gen1 in my home network and I'm tempted to switch to the Unifi Controller plugin for OPNsense.

Before I start messing around with it, I'd like to know if I can update the controller using the official Ubiquiti releases or am I stuck waiting and hoping for the maintainer to update the plugin? That would be a deal breaker for me.

Update:
I contacted the maintainer and he confirmed he will have to release the updates.

It's fixed now after updating to the latest version, but I rebooted few times (test pipes were created a couple of months ago) before and never went away. Anyway, thanks for the reply.

I was testing different configurations with the shaper and before I settled on what I wanted, I created two test Pipes that I then deleted. However I noticed that they are still showing in the Status page without any description, along with the ones I'm actually using. How can I delete them for good?

[Update]
I downloaded and check the config file. Under TrafficShaper I only see the Pipes, Queues and Rules I created. There is no trace of the test ones, so I'm not sure where the status page gets that.

[Update 2]
After updating to 23.1.1 the problem was solved.

Thanks for the suggestions. I'll wait a couple of days to see if it's an issue on their end. Then I'll attempt a manual update

I've always been able to upgrade AdGuard from within it's UI. Today there was a new update (v0.107.15), but for some reason it doesn't run. Instead, I get this message "Auto-update failed. Please follow these steps to update manually." redirecting me to https://github.com/AdguardTeam/AdGuardHome/wiki/FAQ#manual-update

You are a brave man! Enjoy your time off, I just came back from there ;)