Messages

Don't torture yourself, downgrade. There are numerous problems with 25. It's a broken release as is FreeBSD 13 in general. It's not worth anyone's while to try and wrestle with its problems until the dev team smartens up and stops mimicking Linux.

Try:

Interface: LAN
Direction: out
Source: any
Destination: 239.255.255.250
Protocol: UDP
Source and Destination port: any
Action: block

Then again these announcements are a mandatory part of a UPnP service. It simply tells devices on the LAN that it is there. As it should according to the standards.

HTH,
Patrick

That's exactly how I defined it. What netmask do you suggest on the dst addy?

You can argue that, but like I wrote, packets keep coming despite the rule that is supposed to block them. If you want to be helpful, you could word your replies in positive terms such as this and this should be done, but you are only writing in negatives such as something does not work, which makes you hard to understand.

Sounds like a gap in OS firewall

miniupnpd loaded itself all on its own, several hours later.

How should I troubleshoot mini upnpd crashes? It used to work fine for months until I reinstalled recently.

The entire 24.7.x line appears to have major issues.

I accidentally hit update, and it began to d/l a version that I did not want. Well, there is no way to stop an update once it started, so I am in a version that I want to have nothing to do with, and there is no downgrade. How's this for a clear-cut use case? To add insult to injury, that version has broken pkg. Guess what I feel? You guess is right.

Zotac zbox CI325

Your box is hugely redundant to your use case. I have 600+ WAN rules plus geoip on a 1x HT Atom with 2gb DDR2, and it never skipped a beat. So it's not the lack of processing power that's killing you, it's something else: Realtek and its drivers or FreeBSD 13 of which I am weary. It's following the downward spiral of other FOSS operating systems, having climbed to its top glory by 10, stagnated at 11, and began to retard at 12.

[MiniUPnPd]

UPnP plugin is installed and active, but isn't it supposed to work as a server rather than actively send out?

NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
LOCATION: http://x.x.x.x:2189/rootDesc.xml
SERVER: FreeBSD/12.1-RELEASE-p20-HBSD UPnP/1.1 MiniUPnPd/2.1.20200510
NT: upnp:rootdevice
USN: uuid:528c8e6c-4a3c-6598-999a-0e9df15ad32::upnp:rootdevice
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1747339380
BOOTID.UPNP.ORG: 1747339380
CONFIGID.UPNP.ORG: 1337

I tried to create a firewall rule to block source LAN iface port 1900/udp. Also tried destination 239.255.255.250. But packets keep coming.
I just don't want this noise on my LAN, which serves no purpose. When my few select applications ask for UPnP, they will tell the plugin that they do. Until then no one is interested in anything it might want to say.

Are you suggesting that OS routes then from the WAN?

Seeing non-stop SSDP packets from the router LAN iface to the LAN. What is the purpose of them? Which function of OS depends on them being sent?

Please also consider zebra coloring by CSS for FW rules and other lists.

v. 25 cannot connect to my provider's PPPoE, so it is not something that I will have an opportunity to review.

By default, OS installs to full disk, which is sub-optimal.
Is there a way to do the opposite of https://forum.opnsense.org/index.php?topic=19250.0 and shrink all of the partitions to their bare minimum?

I have this currently and no faintest idea how to shrink it:


2% / [zfs] (1.1G/64G)
0% /var/log [zfs] (1.8M/63G)
0% /zroot [zfs] (88K/63G)
0% /tmp [tmpfs] (408K/10G)
0% /var/crash [zfs] (88K/63G)
0% /usr/home [zfs] (88K/63G)
0% /var/audit [zfs] (88K/63G)
0% /usr/ports [zfs] (104M/63G)
0% /var/mail [zfs] (112K/63G)
0% /var/tmp [zfs] (88K/63G)
0% /usr/src [zfs] (88K/63G)
0% /tmp [tmpfs] (408K/10G)

What should the procedure be?

It seems like this functionality already exists in some places

Yes! There are good examples of user-friendly UI all over the web admin. All that's necessary is to transplant them to the pain points. So, the effort will be minimal.