-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
miniupnpd: duplicate rules with pf backend #719
Comments
i have the same bug on openbsd 7.4 with miniupnpd-2.3.0pl20220601p0.
the only software i have making use of upnp right now is ipfs, which appears to use libp2p for UPNP. |
my apologies for the noise, it seems that this was fixed and openbsd 7.4 simply never updated the available package. everything seems fine with miniupnpd 2.3.5. @Inevitable what version are you running? can you try a new version? |
Ah, of course, relevant troubleshooting info does help I'd bet. It's running on an Opnsense install, so I'd have to see about overriding the default pkg. OPNsense 24.1.3_1-amd64 miniupnpd 2.3.3 Mar 5 2024 |
@Inevitable have you tried to upgrade to miniupnpd 2.3.5 ? |
I've not, seems ports is not yet updated to that version, and as this is a semi-appliance gateway, I'll probably just live with it until it rolls forward. I assume it's fixed though, if others are not reporting on it. If it updates and I still see the behavior I'll report back. Thanks for having a look! |
Updating for posterity/searches. I was able to update to 2.3.6, and can confirm that the behavior is no longer present. Single entries which function as expected! |
Was seeing a constantly expanding list of rules on my gateway (opnsense), and managed to narrow it down to a specific piece of software which requests some pseudorandom port forwards. Checked with the maintainers and they loop the request for keepalive purposes, but were doing so on a short interval. This resulted in repeating duplicate rules slowly stacking up over time in
pf
OPNsense 24.1.3_1-amd64
FreeBSD 13.2-RELEASE-p10
miniupnpd 2.3.3 Mar 5 2024
using pf backend
I'm far from an expert, or able to contribute much in the way of actually fixing the issue, but would guess it's something similar to the previously patched issue with
nft
#582The text was updated successfully, but these errors were encountered: