OPNsense Forum

Archive => 17.1 Legacy Series => Topic started by: Solaris17 on October 11, 2016, 01:45:44 am

Title: UPnP issue
Post by: Solaris17 on October 11, 2016, 01:45:44 am

Attempting to get rid of restriction problems on the consoles in the house I have finally narrowed it down to an issue with UPnP on this build. I ran into a thread here https://forum.opnsense.org/index.php?topic=3469.0 that seemed to have the issue. I reinstalled miniupnpd in an attempt to fix it myself. During completion I get this message in the console readout.

For this daemon to work, you must modify your pf rules to add an anchor
in both the NAT and rules section.  Both must be called 'miniupnpd'.
Example:

# NAT section
# UPnPd rdr anchor
rdr-anchor "miniupnpd"

# Rules section
# uPnPd rule anchor
anchor "miniupnpd"
***DONE***

I am unsure if this is still needed since I saw no reference to this step in the thread mentioned before. I also am not clear on exactly the message is trying to have me do. My current build is.

OPNsense 17.1.a_410-amd64
FreeBSD 10.3-RELEASE-p9
OpenSSL 1.0.2j 26 Sep 2016

Any ideas on what I can attempt next?

Title: Re: UPnP issue
Post by: franco on October 11, 2016, 07:09:43 am

Hi there,

The package message is from FreeBSD and the automatic rules should take care of this.

It's a peculiar case: we did work on miniupnpd code recently, but the last official opnsense-devel cut (17.1.a_410) is the one that does not have any reworks yet.

Try to move to the 16.7.5 package:

# opnsense-update -t opnsense

And see if that improves things.


Cheers,
Franco