Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - burre90

#1
26.1 Series / Re: Unbound DNSBL
January 31, 2026, 10:37:09 AM
Tester appears to show that blocking is working as expected so nothing appears to be broken in that sense.

{
  "status": "OK",
  "action": "Block",
  "policy": {
    "source_nets": [
      "192.168.194.253/32",
      "192.168.177.248/32"
    ],
    "address": "0.0.0.0",
    "rcode": 0,
    "description": "TV Blocklists",
    "id": "54037ffe-5210-40e8-b2b3-5d9818f0d4cf",
    "passlist": ".*localhost$",
    "prio": 1,
    "hidx": 0,
    "bl": "hgz003"
  }
}
#2
26.1 Series / Unbound DNSBL
January 31, 2026, 10:30:23 AM
Seeing this spammed in my Unbound log file, no idea what is going on, tried removing all IP's from Source Net(s) but no change.

Just wanted to report this, not sure if it's normal behaviour?

2026-01-31T01:25:25-08:00 Error unbound [42645:2] error: dnsbl_module: unable to parse client source: Traceback (most recent call last):   File "/unbound-dnsbl/lib/dnsbl.py", line 107, in _in_network     src_address = ipaddress.ip_address(client)                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/ipaddress.py", line 54, in ip_address     raise ValueError(f'{address!r} does not appear to be an IPv4 or IPv6 address') ValueError: '' does not appear to be an IPv4 or IPv6 address

#3
26.1 Series / Re: MiniUPNPD
January 31, 2026, 01:54:09 AM
Quote from: franco on January 30, 2026, 11:18:37 PMI think I found it.  Looks like a feature removal gone wrong:

# opnsense-patch https://github.com/opnsense/core/commit/311184daa8
# /usr/local/etc/rc.filter_configure

It should bring back the required anchors.


Cheers,
Franco


Appears to be working for me now :)


#4
26.1 Series / Re: MiniUPNPD
January 30, 2026, 11:04:38 AM
I had some spare time, so I set up a fresh USB install of OPNsense 26.1 with the default config/settings to test UPnP behavior.

here is the log:

2026-01-30T10:00:39    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:39    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:39    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:36    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:36    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:36    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:33    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:33    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:33    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:33    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:33    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:22    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:17    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:17    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:17    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:17    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:38    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:37    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:37    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:36    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:35    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:28    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:28    Error    miniupnpd    could not open lease file: /var/run/miniupnpd.leases-ipv6
2026-01-30T09:59:28    Error    miniupnpd    could not open lease file: /var/run/miniupnpd.leases


#5
26.1 Series / Re: MiniUPNPD
January 30, 2026, 09:53:21 AM
Quote from: Marius_ on January 29, 2026, 10:18:02 PMHi,

It worked perfectly fine on 25.7.11 before upgrade... :)

I got the same errors... After upgrade.

2026-01-29T22:10:40Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-01-29T22:10:40ErrorminiupnpdFailed to add NAT-PMP 28159 TCP->192.168.1.19:32400 'NAT-PMP 28159 TCP'
2026-01-29T22:10:40Errorminiupnpdioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument
2026-01-29T22:10:40Errorminiupnpdpfctl_get_rules_info: Invalid argument



I am also getting
2026-01-30T00:51:58-08:00   Error   miniupnpd    ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument

And Franco I also tried both the opnsense-update commands you shared (with a reboot each time) and no change.
#6
26.1 Series / Re: MiniUPNPD
January 29, 2026, 09:38:01 AM
I have had issues with UPNP as well recently in 26.1, even tried making a fresh new interface with only an Allow All rule, to rule out any firewall issues, while also disabling all custom WAN Rules... no luck for my PS5 or my PC. For the time being I have just made a NAT outbound static port rule so I can get moderate NAT at least.

Really frustrating me, but I'm not trying to blame anyone, as I am not as tech savvy as you all.


Here's my logs if it helps at all, sorry I am not very knowledgeable of any of this stuff.


2026-01-29T01:50:27-08:00   Error   miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-29T01:50:13-08:00   Error   miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-29T01:49:51-08:00   Error   miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-29T01:49:51-08:00   Error   miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-29T01:49:33-08:00   Error   miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-29T01:49:32-08:00   Error   miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-29T01:49:20-08:00   Error   miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-29T01:49:20-08:00   Error   miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-29T01:49:19-08:00   Error   miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-29T01:49:19-08:00   Error   miniupnpd    could not open lease file: /var/run/miniupnpd.leases-ipv6
2026-01-29T01:49:19-08:00   Error   miniupnpd    could not open lease file: /var/run/miniupnpd.leases