pfSense

this has been resolved with the latest snapshot. You can close this ticket.

http://forum.pfsense.org/index.php/topic,50971.0.html

Actually it's broken again:
http://forum.pfsense.org/index.php/topic,50971.msg273385.html#msg273385

Confirmed broken again on July 10th snapshot.

I recompiled it after doing a slightly different preparation method this time, so hopefully the next snapshot is better.

Not sure if it is the same issue or not, but I noticed that miniupnpd wasn't working in the 7/13 build, so I updated to the 7/21 build and I'm still seeing it not starting up..

2.1-BETA0 (amd64)
built on Sat Jul 21 15:31:46 EDT 2012
FreeBSD 8.3-RELEASE-p3

Jul 22 10:49:04 miniupnpd⁵⁶⁰⁵¹: DIOCGETSTATUS: Operation not supported by device
Jul 22 10:49:04 miniupnpd⁵⁶⁰⁵¹: DIOCGETSTATUS: Operation not supported by device
Jul 22 10:49:04 miniupnpd⁵⁶⁰⁵¹: Failed to init redirection engine. EXITING
Jul 22 10:49:04 miniupnpd⁵⁶⁰⁵¹: Failed to init redirection engine. EXITING
Jul 22 10:49:12 miniupnpd²⁷⁸⁶: DIOCGETSTATUS: Operation not supported by device
Jul 22 10:49:12 miniupnpd²⁷⁸⁶: DIOCGETSTATUS: Operation not supported by device
Jul 22 10:49:12 miniupnpd²⁷⁸⁶: Failed to init redirection engine. EXITING
Jul 22 10:49:12 miniupnpd²⁷⁸⁶: Failed to init redirection engine. EXITING

Want to confirm that miniupnpd is not working in 7/23 build either.

2.1-BETA0 (amd64)
built on Mon Jul 23 20:21:35 EDT 2012
FreeBSD 8.3-RELEASE-p3

Jul 24 13:19:47 miniupnpd²⁶⁷⁷²: Failed to init redirection engine. EXITING
Jul 24 13:19:47 miniupnpd²⁶⁷⁷²: Failed to init redirection engine. EXITING
Jul 24 13:19:47 miniupnpd²⁶⁷⁷²: DIOCGETSTATUS: Operation not supported by device
Jul 24 13:19:47 miniupnpd²⁶⁷⁷²: DIOCGETSTATUS: Operation not supported by device

2.1-BETA0 (i386)
built on Tue Jul 24 18:28:37 EDT 2012
FreeBSD 8.3-RELEASE-p3

ul 25 16:20:59 miniupnpd¹³⁴⁰⁵: Failed to init redirection engine. EXITING
Jul 25 16:20:59 miniupnpd¹³⁴⁰⁵: Failed to init redirection engine. EXITING
Jul 25 16:20:59 miniupnpd¹³⁴⁰⁵: DIOCGETSTATUS: Operation not supported by device
Jul 25 16:20:59 miniupnpd¹³⁴⁰⁵: DIOCGETSTATUS: Operation not supported by device

Same problem.

Any news on this?

Still broken in:

2.1-BETA0 (amd64)
built on Thu Jul 26 22:35:25 EDT 2012
FreeBSD 8.3-RELEASE-p3

Snapshot from 26 July

Jul 27 20:38:16 php: /pkg_edit.php: miniupnpd: Starting service on interface: lan, opt1
Jul 27 20:38:16 miniupnpd[57202]: DIOCGETSTATUS: Operation not supported by device
Jul 27 20:38:16 miniupnpd[57202]: DIOCGETSTATUS: Operation not supported by device
Jul 27 20:38:16 miniupnpd[57202]: Failed to init redirection engine. EXITING
Jul 27 20:38:16 miniupnpd[57202]: Failed to init redirection engine. EXITING

Regarding tonight's snapshot:

2.1-BETA0 (amd64)
built on Tue Jul 31 18:19:12 EDT 2012
FreeBSD 8.3-RELEASE-p3

miniupnpd seems to be working. I'm not getting errors anymore. Might just be me, and I haven't done thorough testing, but I wanted to pass up the report.

Yeah from testing done from us it seemed just wrong build on previous snapshots.

2.1-BETA0 (i386)
built on Tue Jul 31 19:07:24 EDT 2012
FreeBSD 8.3-RELEASE-p3

Aug 1 09:56:03 miniupnpd⁹²⁵⁴: Failed to init redirection engine. EXITING
Aug 1 09:56:03 miniupnpd⁹²⁵⁴: Failed to init redirection engine. EXITING
Aug 1 09:56:03 miniupnpd⁹²⁵⁴: DIOCGETSTATUS: Operation not supported by device
Aug 1 09:56:03 miniupnpd⁹²⁵⁴: DIOCGETSTATUS: Operation not supported by device

Not working.

built on Tue Jul 31 18:19:12 EDT 2012

problem solved

Aug 1 14:40:05 php: : miniupnpd: Starting service on interface: lan, opt1
Aug 1 14:40:05 miniupnpd[7715]: HTTP listening on port 2189

but

Aug 1 14:42:54 miniupnpd[7715]: ioctl(dev, DIOCGETADDRS, ...): Device busy
Aug 1 14:42:54 miniupnpd[7715]: ioctl(dev, DIOCGETADDRS, ...): Device busy
Aug 1 14:42:54 miniupnpd[7715]: ioctl(dev, DIOCGETADDRS, ...): Device busy
etc...etc...etc

it's not!

2.1-BETA0 (i386)
built on Wed Aug 1 03:29:59 EDT 2012
FreeBSD 8.3-RELEASE-p3

Aug 1 15:48:45 miniupnpd⁶⁰³⁸¹: Failed to init redirection engine. EXITING
Aug 1 15:48:45 miniupnpd⁶⁰³⁸¹: Failed to init redirection engine. EXITING
Aug 1 15:48:45 miniupnpd⁶⁰³⁸¹: DIOCGETSTATUS: Operation not supported by device
Aug 1 15:48:45 miniupnpd⁶⁰³⁸¹: DIOCGETSTATUS: Operation not supported by device
etc...etc...etc

We have 1 AMD64 saying its working and 2 i386 saying its not working.

Even tho its started on AMD64 builds, are ports being opened when you go to the status page? I'm thinking its not because another user reported errors after it started

Is this AMD64 or i386?
Yan Triary wrote:

built on Tue Jul 31 18:19:12 EDT 2012

problem solved

Aug 1 14:40:05 php: : miniupnpd: Starting service on interface: lan, opt1
Aug 1 14:40:05 miniupnpd[7715]: HTTP listening on port 2189

but

Aug 1 14:42:54 miniupnpd[7715]: ioctl(dev, DIOCGETADDRS, ...): Device busy
Aug 1 14:42:54 miniupnpd[7715]: ioctl(dev, DIOCGETADDRS, ...): Device busy
Aug 1 14:42:54 miniupnpd[7715]: ioctl(dev, DIOCGETADDRS, ...): Device busy
etc...etc...etc

2.1-BETA0 (amd64)
built on Wed Aug 1 02:42:26 EDT 2012
FreeBSD 8.3-RELEASE-p3

Aug 2 00:50:53 miniupnpd[7715]: ioctl(dev, DIOCGETADDRS, ...): Device busy
Aug 2 00:50:53 miniupnpd[7715]: ioctl(dev, DIOCGETADDRS, ...): Device busy
Aug 2 00:50:54 miniupnpd[7715]: ioctl(dev, DIOCGETADDRS, ...): Device busy
Aug 2 00:50:54 miniupnpd[7715]: ioctl(dev, DIOCGETADDRS, ...): Device busy

Actual

Okay, as a follow-up: I'm getting these same errors too. My initial response was due to miniupnpd actually starting and staying active for longer than a second. Please set this issue back to NEW!

2.1-BETA0 (amd64)
built on Wed Aug 1 02:42:26 EDT 2012
FreeBSD 8.3-RELEASE-p3

Aug 2 00:19:21 miniupnpd⁶¹²²²: ioctl(dev, DIOCGETADDRS, ...): Device busy
Aug 2 00:19:21 miniupnpd⁶¹²²²: ioctl(dev, DIOCGETADDRS, ...): Device busy
Aug 2 00:19:21 miniupnpd⁶¹²²²: ioctl(dev, DIOCGETADDRS, ...): Device busy
Aug 2 00:19:21 miniupnpd⁶¹²²²: ioctl(dev, DIOCGETADDRS, ...): Device busy

get back

Aug 2 11:52:41 miniupnpd[61172]: HTTP listening on port 2189
Aug 2 11:52:41 miniupnpd[61172]: HTTP listening on port 2189
Aug 2 11:52:41 miniupnpd[61172]: no HTTP IPv6 address
Aug 2 11:52:41 miniupnpd[61172]: no HTTP IPv6 address
Aug 2 11:52:41 miniupnpd[61172]: setsockopt(udp, IPV6_ADD_MEMBERSHIP): Can't assign requested address
Aug 2 11:52:41 miniupnpd[61172]: setsockopt(udp, IPV6_ADD_MEMBERSHIP): Can't assign requested address
Aug 2 11:52:41 miniupnpd[61172]: setsockopt(udp_notify IPv6, IPV6_MULTICAST_IF, 0): Can't assign requested address
Aug 2 11:52:41 miniupnpd[61172]: setsockopt(udp_notify IPv6, IPV6_MULTICAST_IF, 0): Can't assign requested address
Aug 2 11:52:41 miniupnpd[61172]: Failed to open sockets for sending SSDP notify messages. EXITING
Aug 2 11:52:41 miniupnpd[61172]: Failed to open sockets for sending SSDP notify messages. EXITING

All this is very very sad :(

Not sure why you'd consider bugs in a beta release sad, if there were no bugs, it wouldn't be beta :-)

My last commit lets it start up properly now -- though I am unsure if it's actually working still. No pf errors, but I didn't do in-depth testing.

Jim P wrote:

Not sure why you'd consider bugs in a beta release sad, if there were no bugs, it wouldn't be beta :-)

My last commit lets it start up properly now -- though I am unsure if it's actually working still. No pf errors, but I didn't do in-depth testing.

See no connection between bugs and beta version. Also bug it's when something working not in the way it meant to. When something is not working at all... it's called not working at all.
Also you could at least specify what version and what build you use. Your logs are worthless without this.

Maxim Luppov wrote:

See no connection between bugs and beta version.

For us, a beta is actually a beta, not a perpetual product like some companies do (Google). When the system is reasonably free of bugs we move to RC and RELEASE status. BETA0 implies it's early beta and as such will have bugs and other issues, no matter what you prefer to call them.

Also bug it's when something working not in the way it meant to. When something is not working at all... it's called not working at all.

If it's not working at all, it's surely not working the way it want meant to. Both are "bugs" in the sense we use it here. There is no distinction. No need to be pedantic, a bug is a bug.

Also you could at least specify what version and what build you use. Your logs are worthless without this.

The newest snapshot as of the time I posted. If I mentioned I committed a change, you can find the commit in the commit log to see the time on it.

Jim P wrote:

Maxim Luppov wrote:

See no connection between bugs and beta version.

For us, a beta is actually a beta, not a perpetual product like some companies do (Google). When the system is reasonably free of bugs we move to RC and RELEASE status. BETA0 implies it's early beta and as such will have bugs and other issues, no matter what you prefer to call them.

Also bug it's when something working not in the way it meant to. When something is not working at all... it's called not working at all.

If it's not working at all, it's surely not working the way it want meant to. Both are "bugs" in the sense we use it here. There is no distinction. No need to be pedantic, a bug is a bug.

Also you could at least specify what version and what build you use. Your logs are worthless without this.

The newest snapshot as of the time I posted. If I mentioned I committed a change, you can find the commit in the commit log to see the time on it.

You can't read???

2.1-BETA0 (i386)
built on Fri Aug 3 01:05:32 EDT 2012
FreeBSD 8.3-RELEASE-p3

Aug 3 16:40:54 miniupnpd⁵⁷⁸⁵⁷: Failed to init redirection engine. EXITING
Aug 3 16:40:54 miniupnpd⁵⁷⁸⁵⁷: Failed to init redirection engine. EXITING
Aug 3 16:40:54 miniupnpd⁵⁷⁸⁵⁷: DIOCGETSTATUS: Operation not supported by device
Aug 3 16:40:54 miniupnpd⁵⁷⁸⁵⁷: DIOCGETSTATUS: Operation not supported by device

Where exactly it's working???

Beta is beta. Bug is bug. And this is NOT working daemon.

And yelling won't fix it any faster, nor will berating/abusing developers. That's a good way to get yourself banned from posting here.

I was testing on amd64.

Jim P wrote:

And yelling won't fix it any faster, nor will berating/abusing developers. That's a good way to get yourself banned from posting here.

I was testing on amd64.

I'm yelling at you, not at the developers. And it's very easy to see difference, like between bugged and not working daemon. But not for you obviously. Also banned must be those, who posting wrong conclusions and useless logs of who knows what. Cheers!

Maxim Luppov wrote:

I'm yelling at you, not at the developers. And it's very easy to see difference, like between bugged and not working daemon. But not for you obviously. Also banned must be those, who posting wrong conclusions and useless logs of who knows what. Cheers!

...and I'm a developer, one of the people trying to debug this and work on it, and you are really making want to ignore the problem for a while. There is zero cause for your attitude here. Goodbye.

Jim, you have my vote to ban him.. Or lock this bug report so only myself and the developers can comment on since I was the one that submitted the bug report a couple of months ago..

Now I see why UPnP still doesn't work. That's because you are "working on it". :D Yes, ban me again, you big scary developer. That's how you solve all your problems, do you?
As I said all this is very very sad. Cheers 1 more time!

Odd that it works on one of my systems but I updated my Alix and it does not work on there. More feedback from others is needed.

starts for me on i386 now.

With version:

2.1-BETA0 (i386)
built on Sun Aug 5 18:24:50 EDT 2012
FreeBSD 8.3-RELEASE-p3

the service starts but:

Aug 6 08:07:32 miniupnpd⁴⁵⁰⁹⁶: HTTP listening on port 2189
Aug 6 08:07:32 miniupnpd⁴⁵⁰⁹⁶: HTTP listening on port 2189
Aug 6 08:07:32 miniupnpd⁴⁵⁰⁹⁶: Listening for NAT-PMP traffic on port 5351
Aug 6 08:07:32 miniupnpd⁴⁵⁰⁹⁶: Listening for NAT-PMP traffic on port 5351
Aug 6 08:08:25 miniupnpd⁴⁵⁰⁹⁶: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device
Aug 6 08:08:25 miniupnpd⁴⁵⁰⁹⁶: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device
Aug 6 08:08:25 miniupnpd⁴⁵⁰⁹⁶: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device
Aug 6 08:08:25 miniupnpd⁴⁵⁰⁹⁶: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device
Aug 6 08:08:25 miniupnpd⁴⁵⁰⁹⁶: ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Operation not supported by device
Aug 6 08:08:25 miniupnpd⁴⁵⁰⁹⁶: ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Operation not supported by device
Aug 6 08:08:25 miniupnpd⁴⁵⁰⁹⁶: Failed to add NAT-PMP 2170 tcp->192.168.10.11:2170 'NAT-PMP 2170 tcp'
Aug 6 08:08:25 miniupnpd⁴⁵⁰⁹⁶: Failed to add NAT-PMP 2170 tcp->192.168.10.11:2170 'NAT-PMP 2170 tcp'

oh right forgot to check that is actually works, i get similar output as above.

Next new snapshot might have a better chance at being OK. If you can't wait and want to try the new binary before the snapshot goes up, see http://forum.pfsense.org/index.php/topic,50971.msg279298.html#msg279298

Works with that binary, you're the man! ;)

With snapshot running on ALIX 2D13:

2.1-BETA0 (i386) 
built on Sun Aug 5 18:24:43 EDT 2012 

miniupnp is started with no error:

Aug 6 16:05:59    miniupnpd[4571]: HTTP listening on port 2189
Aug 6 16:05:59    miniupnpd[4571]: HTTP listening on port 2189
Aug 6 16:05:59    miniupnpd[4571]: Listening for NAT-PMP traffic on port 5351
Aug 6 16:05:59    miniupnpd[4571]: Listening for NAT-PMP traffic on port 5351

Started but not working:

Aug 6 20:48:04    miniupnpd[24527]: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device
Aug 6 20:48:04    miniupnpd[24527]: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device
Aug 6 20:48:04    miniupnpd[24527]: ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Operation not supported by device
Aug 6 20:48:04    miniupnpd[24527]: ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Operation not supported by device

With snapshot running on ALIX 2D13:
[...]

miniupnp is started with no error:
[...]

jim thank you for staying on top of this!!! Works great now

miniupnpd²⁵⁰⁷: DIOCGETSTATUS: Operation not supported by device

after upgrade freebsd to 10.0 release #0 and ports\pkg reinstall

There aren't any official images for FreeBSD 10.x yet. This ticket was for 2.1 only (and is very old).