Project

General

Profile

Actions

Bug #481

closed

miniupnpd not working

Added by Chris Buechler over 11 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
UPnP/NAT-PMP
Target version:
Start date:
04/04/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

Stopped working after April 1 snapshots apparently.

miniupnpd32272: Failed to init redirection engine. EXITING
miniupnpd32272: DIOCGETSTATUS: Operation not supported by device

Actions #1

Updated by Michel Kenny over 11 years ago

Happening for me too since I updated to v2 beta yesterday (from latest 1.2.3). Let me know if more information is needed.

Actions #2

Updated by Marcus Brown over 11 years ago

This may be relevant . . .
http://osdir.com/ml/openbsd.pf/2005-02/msg00117.html

quote:

There's probably a simple explanation for this... But when I run pftop
it only displays pftop: DIOCGETSTATUS

This means that the kernel you're running and the pftop binary were
built from different pfvar.h headers.

If you're running a 3.6-release kernel now, remove pftop and install the
proper pftop binary package from 3.6-release. A package from 3.5 or
earlier will produce the error you see. Similarly, using a snapshot
package of pftop with a non-snapshot kernel will fail like that.

If you built the kernel from source, make sure that /usr/include/pfvar.h
is the same as /usr/src/sys/net/pfvar.h, i.e. run a full rebuild of the
entire system (kernel and userland), then rebuild pftop from source,
too.

Actions #3

Updated by Michel Kenny over 11 years ago

I just tried the latest version (20100420-054) and the upnp service is starting and is working. It wasn't working as of a few days ago.

Actions #4

Updated by Chris Buechler over 11 years ago

  • Status changed from New to Resolved

Yeah it's been fixed, thanks

Actions

Also available in: Atom PDF