Miniupnpd issues with lastest snapshot
-
Yeah that's the result of some other changes/experimenting we had been doing. It's still not 100%, next snapshot might be better, we'll have to wait and see.
-
Not working with the 8/2/2012 i386 build.
Interesting note - miniupnp does not show up on the packages screen under install OR available yet it will show up within Service Status.
Thank you for all of the work you guys do - I truly love this firewall.
-Fred
-
Not working with the 8/2/2012 i386 build.
Interesting note - miniupnp does not show up on the packages screen under install OR available yet it will show up within Service Status.
Thank you for all of the work you guys do - I truly love this firewall.
-Fred
its not an add-on package.. it comes pre-built with pfSense now.
-
I don't see any errors in the logs, but apparently it still doesn't work:
2.1-BETA0 (amd64)
built on Fri Aug 3 00:17:11 EDT 2012 -
Not working with the 8/2/2012 i386 build.
Interesting note - miniupnp does not show up on the packages screen under install OR available yet it will show up within Service Status.
Thank you for all of the work you guys do - I truly love this firewall.
-Fred
its not an add-on package.. it comes pre-built with pfSense now.
Is it possible that in the move from Package to Feature there may be lingering files that should/would have been uninstalled but didn't because the package ended up getting broken somewhere along the line?
-Fred
-
It has not been a package since before 1.2 even. It is merely configured using the internal pkg system for its gui page. Nothing about it is a package in the binary sense, and that's what this is – an issue with the miniupnpd code/binary.
If someone in this thread has said miniupnpd "package" they meant "package" in the freebsd sense, not in pfSense.
-
I must say i kinda regret trying the 2.1 beta to see if my isp was kind enough to give me ipv6 addresses (witch they don't), and now miniupnpd not working for months..
Wish there was a easy way back to stable without having to set up everything again.
C
-
I'd like to see upnp work more than anyone else, but when people are real dicks about it (see https://redmine.pfsense.org/issues/2527#change-9600 ), it doesn't help. It is rather discouraging.
-
Well I hope you don't get discouraged about it so we'll hopefully have uPnP working soon :)
-
Well it takes more than a single guy with a bad attitude to knock a project off-track, but it still doesn't sit well. Can't please everyone. Especially people who have a faulty expectation of early beta snapshot images.
-
Keep an eye out for the next new snapshot.
-
Keep an eye out for the next new snapshot.
thank you Jim!! I will update my i386 install once its available for download…. I saw the post on redmine this afternoon and its a shame.. Yeah it sucks that upnp stop working but this is why we test and report our findings... I took the chance to use 2.1 beta in production. If something stops working, I can only blame myself and report that there is an issue... Not to flame on you or anyone on the pfsense team. I'll be honest, there are times I want too but we are adults here... At least most of us are anyways...
Thank you for all your hard work!
-
Upnp works again in 2.1-BETA0 (i386)
built on Sun Aug 5 18:24:50 EDT 2012
FreeBSD 8.3-RELEASE-p3.Really nice to have this working again, thanks for all the hard work.
The efforts by the pfsense team in building such a great firewall are appreciated enormously. -
2.1-BETA0 (amd64)
built on Sun Aug 5 17:20:36 EDT 2012
FreeBSD 8.3-RELEASE-p3
Thank you jimp -
We are getting closer :-) It starts, but not interfacing with pf. i386
Aug 6 07:32:31 miniupnpd[44199]: Failed to add NAT-PMP 52225 udp->192.168.0.100:52225 'NAT-PMP 52225 udp' Aug 6 07:32:31 miniupnpd[44199]: Failed to add NAT-PMP 52225 udp->192.168.0.100:52225 'NAT-PMP 52225 udp' Aug 6 07:32:31 miniupnpd[44199]: ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Operation not supported by device Aug 6 07:32:31 miniupnpd[44199]: ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Operation not supported by device Aug 6 07:32:31 miniupnpd[44199]: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device Aug 6 07:32:31 miniupnpd[44199]: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device Aug 6 07:32:31 miniupnpd[44199]: Failed to add NAT-PMP 52225 tcp->192.168.0.100:52225 'NAT-PMP 52225 tcp' Aug 6 07:32:31 miniupnpd[44199]: Failed to add NAT-PMP 52225 tcp->192.168.0.100:52225 'NAT-PMP 52225 tcp' Aug 6 07:31:50 miniupnpd[44199]: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device Aug 6 07:31:50 miniupnpd[44199]: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device Aug 6 07:31:50 miniupnpd[44199]: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device Aug 6 07:31:50 miniupnpd[44199]: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device Aug 6 07:31:50 miniupnpd[44199]: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device Aug 6 07:31:50 miniupnpd[44199]: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device Aug 6 07:31:23 miniupnpd[44199]: Listening for NAT-PMP traffic on port 5351 Aug 6 07:31:23 miniupnpd[44199]: Listening for NAT-PMP traffic on port 5351 Aug 6 07:31:23 miniupnpd[44199]: HTTP listening on port 2189 Aug 6 07:31:23 miniupnpd[44199]: HTTP listening on port 2189 -
Yes it does start and function on amd64, I know that much for sure. i386 is a bit more of mystery. I copied the binary over to my i386 firewall and it works there. I updated my alix and it didn't work there.
-
Can someone else on i386 try this:
killall -9 miniupnpd fetch -o /usr/local/sbin/miniupnpd http://files.chi.pfsense.org/jimp/miniupnpd-i386 chmod 555 /usr/local/sbin/miniupnpdAnd then restart the miniupnpd service in the GUI, and see if it works.
That binary now works on my Alix.
-
I am using pfSense 2.1-BETA0-pfSense (i386) on a Soekris 6501.
I tried the miniupnpd file replacement you mentioned. Activated miniupnpd, and then ran Skype and Transmission. Neither got added - ie. still doesn't work as it should.
However, miniupnpd keeps running - which is a good thing.
Below are the entries from my syslog file…
Aug 6 09:46:27 miniupnpd[12563]: Failed to remove NAT-PMP mapping eport 61079, protocol TCP Aug 6 09:46:27 miniupnpd[12563]: Failed to remove NAT-PMP mapping eport 61079, protocol TCP Aug 6 09:46:20 miniupnpd[12563]: Listening for NAT-PMP traffic on port 5351 Aug 6 09:46:20 miniupnpd[12563]: Listening for NAT-PMP traffic on port 5351 Aug 6 09:46:20 miniupnpd[12563]: HTTP listening on port 2189 Aug 6 09:46:20 miniupnpd[12563]: HTTP listening on port 2189 -
Any way to try that with UPnP rather than NAT-PMP?
-
JMP, turned off NAT-PMP and tried again.
Tried Skype & Transmission and neither was able to create an entry (as they should if it worked ok).
In summary - Still doesn't work as it should, but application is able to run without error.
Log entries & configuration below:
UPnP & NAT-PMP Settings
- Enable UPnP & NAT-PMP - Enabled
- Allow UPnP Port Mapping - Enabled
- Allow NAT-PMP Port Mapping - DISABLED
- Interfaces (generally LAN) - LAN
Aug 6 10:07:40 miniupnpd[53693]: HTTP listening on port 2189 Aug 6 10:07:40 miniupnpd[53693]: HTTP listening on port 2189 Aug 6 10:07:40 php[57805]: /pkg_edit.php: miniupnpd: Restarting service on interface: lan
