Messages

This doesn't seem to be related to the Q-Feeds Plugin since you're using AGH. As your screenshot shows it perfectly pulls in the domains? If you try to reach 'cherrypharm.com' (just checked, still in the domains list), can you see any DNS requests for that domain in AGH ?

Yes, you're correct - after a bit more checking, it seems the Warning for that website was generated by my browser natively, or via an add-in (Brave) - I could see within the AGH log that it actually blocked access. When I tried Safari, I didn't get the warning as it must not have the same website checking, and again aGH blocked it. Sorry for my misunderstanding :)

Allright! Will look into it together with Deciso and get back to you. Thanks for digging into it already, very helpful!

FYI - I'm seeing this issue too however I'm using the qfeed Domains blocklist only within AGH and not within Unbound.  I'm running OPNsense 25.7.11_9-amd64  with AGH setup as the main DNS on port 53, and Unbound is on 5335. Within AGH I have 127.0.0.1:5335 setup as a Private reverse DNS server, and for Local resolution via Unbound on 127.0.0.1:5335 - this has been working well for years.

Blocking of sites on the qfeeds Domains blocklist within AGH worked well previously, however it now seems to have stopped as the example problem url's posted earlier in this thread are no longer blocked and they display warnings in my browser.

The widget shows the blocked number incrementing as I have the floating rules setup to block the qfeeds IPs which works properly - it's just the Domain blocklist isn't working anymore

edited to add - this is the url added to the AGH Qfeeds Malware Domains shown in the screenshot:
https://api.qfeeds.com/api.php?feed_type=malware_domains&api_token=tip_xxxxxxx

/boot/efi/efi/freebsd/loader.efi and /boot/efi/efi/boot/bootx64.efi should be identical, although only one will be used. Which one depends on your BIOS and its settings.

I've now ensured that both are identical - I think I should be ok now - thanks for your assistance @Patrick

ZFS pool upgrades are never applied automatically. You need to explicitly use "zpool upgrade zroot". And if you do this, then remember to also upgrade your boot loader.

As further context to my question, coincidentally today the second of two disks in my ZFS Raid pool died, so rather than replace it, I detached it from the pool and did a zpool update. However I didn't upgrade the boot loader as I overlooked that step :(

I tried to reboot but it failed as it couldn't find a bootable disk, so I booted off usb and copied the loader.efi from the usb to /boot/efi/efi/boot/bootx64.efi - thats probably why that file has today's date.

The pool is showing no errors now:

Code Select Expand

# zpool status
  pool: zroot
 state: ONLINE
  scan: resilvered 4.26G in 20483 days 03:18:56 with 0 errors on Fri Jan 30 14:19:00 2026
config:

NAME        STATE     READ WRITE CKSUM
zroot       ONLINE       0     0     0
  ada0p4    ONLINE       0     0     0

errors: No known data errors

So I'm now assuming I'll need to copy it to /boot/efi/efi/freebsd/loader.efi as that file is from 2022?



Thanks

With my installs all being ZFS is it still recommended to do this after a major upgrade:

cp /boot/loader.efi /boot/efi/efi/freebsd/loader.efi
cp /boot/loader.efi /boot/efi/efi/boot/bootx64.efi

Sorry to hijack this thread - I just listed these files on my OPNsense 25.7.11_9-amd64 system:

Code Select Expand

root@OPNsense:~ # ls -l /boot/loader.efi
-r-xr-xr-x  2 root wheel 658944 Jan 13 23:26 /boot/loader.efi
root@OPNsense:~ # ls -l /boot/efi/efi/freebsd/loader.efi
-rwxr-xr-x  1 root wheel 890368 May 31  2022 /boot/efi/efi/freebsd/loader.efi
root@OPNsense:~ # ls -l /boot/efi/efi/boot/bootx64.efi
-rwxr-xr-x  1 root wheel 658944 Jan 30 18:28 /boot/efi/efi/boot/bootx64.efi

Looking at the dates, /boot/efi/efi/freebsd/loader.efi is from 2022 and a different filesize, and the others are the same size but different dates and I assume they are the same file.

I should I copy /boot/loader.efi to /boot/efi/efi/freebsd/loader.efi to fix this? I wonder why I haven't (yet?) seen any issues?

Thanks

Any thoughts on if my router should be accessible via example.com and why I am getting an error?

The help for the setting "Alternate Hostnames" under System > Settings > Administration says this: "Alternate Hostnames for DNS Rebinding and HTTP_REFERER Checks
Here you can specify alternate hostnames by which the router may be queried, to bypass the DNS Rebinding Attack checks. Separate hostnames with spaces."

Perhaps you could enter this in there and see if you still get the error?

Code Select Expand

example.dyndns.org example.com

Thanks guys for clarifying

Sorry if the following are obvious questions, hopefully someone can clarify please.

• I'm using native ISC DHCP on 25.7.11_2 and don't intend to migrate (yet) to the alternatives.
  I see the release notes for 26.1 says "ISC-DHCP moves to a plugin. It will be automatically installed during upgrades."
  
  Does this mean the existing ISC-DHCP configurations for IPv4 and IPv6 will be "imported" into the plugin, so I won't need to do any configuration changes?
  
  
• Regarding the release note comment which seems a bit ambiguous:
  
  "To accommodate the change away from ISC-DCHP defaults the "Track interface" IPv6 mode now has a sibling called "Identity Association" which does the same except it is not automatically starting ISC-DHCPv6 and Radvd router advertisements to allow better interoperability with Kea and Dnsmasq setups."
  
  As I'm remaining on ISC-DHCP, will I need to make any changes to "Track interface" as I'll need ISC-DHCPv6 and Radvd to autostart.
  
  

Many thanks

I just tested with Wireguard and it does block if you add the Wireguard interface into the two Qfeeds floating rules:

It blocked a known malicious IP on my LAN and Wireguard interfaces:

If I install a VPN on her machine she will probably wind up leaving it on, bypassing Qfeeds

I thought Qfeeds would filter the VPN (if you added within the floating rule) the interface list that currently has WAN?

I've noticed that viewing the Events page is starting to take a while before the page is filled as my log file must be getting larger every day. I understand that the log file is cleared after a reboot which then allows the Events to display quickly, until it again gets larger.

Which logfile is Qfeeds using to populate the Events page?

Sorry didn't check that thoroughly. Seems that somehow your filter_*.log got corrupted. Did you have any system crashes, disk full, or power loss events lately? I think its best to log a bug report on the GitHub plugin repository: https://github.com/opnsense/plugins/issues

No crashes, disk full or power loss - all running fine. I restarted the host that OPNSense is running on and it's now working. Strange that it was working during the day, then overnight the log somehow was corrupted. I'll keep an eye on it.

How frequently is the widget "Blocked" number updated ?

That's very interesting, but we're glad that issue is solved now. Now regarding the events tab, that's an interesting find as well. Just to be sure, you haven't disabled logging on the rules? And you do see blocks in the dashboard widget?

Does this command dump logs ? "/usr/local/opnsense/scripts/qfeeds/qfeedsctl.py logs"

The rules have the logging enabled - I shared a screenshot in my previous reply of the live logs showing my test was blocked. Yes the dashboard widget shows a large blocked number.

The command gives an error:

Code Select Expand

root@OPNsense:~ # /usr/local/opnsense/scripts/qfeeds/qfeedsctl.py logs
Traceback (most recent call last):
  File "/usr/local/opnsense/scripts/qfeeds/qfeedsctl.py", line 50, in <module>
    for msg in getattr(actions, action)():
  File "/usr/local/opnsense/scripts/qfeeds/lib/__init__.py", line 187, in logs
    yield ujson.dumps({'rows': PFLogCrawler(feeds).find()})
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/opnsense/scripts/qfeeds/lib/log.py", line 75, in find
    result.append(self._parse_log_line(line))
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/opnsense/scripts/qfeeds/lib/log.py", line 64, in _parse_log_line
    return [parts[1], fw_line[4], fw_line[7]] + [x for x in fw_line if is_ip_address(x)]
                      ~~~~~~~^^^
IndexError: list index out of range
Thanks

Dear vk2him,

Thank you for your great feedback and suggestions!

• Thanks, fixed it right away!
• I had a look at the reports but unfortunately couldn't reproduce this either. In our backend, which contains over 80 million IOCs, this domain doesn't exist, I also couldn't find it in the OSINT or Premium feeds. If you download the list directly in your browser, do you see the domain then? And or is there anyone else on this forum who experiences connection issues with pvoutput.org? Obviously I'm using all of our blocklists but I can connect without any issues.
• Thanks for pointing out the encoding issue, it's been fixed.
• Good idea, you can now reopen cases and also edit your initial submissions.
• The IPv6 issue is solved now. We'll reconsider the scan limits later, but for now, while we're monitoring infrastructure load, you can scan multiple IPs once per week. The allowed IPs are based on where you've connected from (via TIP login or API calls), to help prevent abuse.
• We've added direct links to the Logs and API Keys sections, great suggestion! For the Available Feeds section, we'll add a link once some new planned pages are ready.

[/list]

Unfortunately, I can't assist directly with Monit configuration, but maybe someone else in the community can share some insights.

Kind regards,

David

Thanks for the reply and fixing the items I pointed out.

Regarding pvoutput.org - today I am able to connect to it, and I wasn't able to find it on the list after I downloaded it, so that's strange.

Anyway, I'm seeing something strange at the moment - my Events tab isn't showing anything and it was yesterday.

I tried browing to a site that is in the IP filter table and the livelogs show Qfeeds blocked it, however The events tab is blank? I tried this yesterday and it appeared in live logs and the events tab?

I've tested this today in my home and seems to be working ok - here's some feedback

• The main website https://qfeeds.com/ has a typo in this section
  .. "We offers detection and response services against phishing  .." the word "offers" should be "offer"
• I added the Blocklist "https://api.qfeeds.com/api?feed_type=malware_domains&api" into Adguard Home and it was working fine, however it blocked the solar monitoring website https://pvoutput.org
  I made a false positive report advising that I was using the malware domains list in AdGuard Home, and Support closed it saying it's not on the list. I double checked I set it correctly, which I had, and submitted another false positive report. Support closed it again and wrote back saying it must be an issue on my end as pvoutput.org isn't on your IP list and not in your Domains lists and to try force reloading the list. I logged another false positive after I disabled all the other AGH blocklists and force reloaded the qfeeds malware list. I also pointed out that issue is with the blocklist in Adguard Home which is using MALWARE Domains and that if I create a whitelist in AGH for pvoutput.org, I can access it, and I was able to access it until I loaded the Qfeeds blocklist - I'm still awaiting a reply
• When logging the false positive reports, I noticed that if I entered a single quote ' in my report, for example won't,  after I saved the report it displayed the HTML number ' instead won't   
• It would be good if a false positive report could be added to/reopened rather than needing to keep adding a new report as I had to keep repeating all the information from the previous ones there were (incorrectly) closed
• I was considering a Plus subscription, however Patrick reported that the scanner isn't working properly, so we need to wait a week to try again as we can only test one IP per week - can this be relaxed until you fix the issue with the scanner?
• In the TIP dashboard, it would be great if clicking on the panels My API Keys, Available Feeds and My API Calls were hyperlinks to those sections

Edited to add

• How can I enable monit to monitor qfeeds ?

Many thanks