miniupnp.tuxfamily.org Forum Index miniupnp.tuxfamily.org
The forum about miniupnp and libnatpmp
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Attempting to install from FreeBSD Ports (10.1)

 
Post new topic   Reply to topic    miniupnp.tuxfamily.org Forum Index -> miniupnpd Compilation/Installation
View previous topic :: View next topic  
Author Message
nreilly



Joined: 29 May 2015
Posts: 1

PostPosted: Fri May 29, 2015 6:09 pm    Post subject: Attempting to install from FreeBSD Ports (10.1) Reply with quote

Hey,

I'm having some issues getting miniupnpd installed on FreeBSD 10.1.

I appear to have similar issues as listed here: topic 607

Code:
May 30 01:54:13 zoop miniupnpd[83505]: ioctl(dev, DIOCGETRULES, ...): Invalid argument
May 30 01:54:18 zoop last message repeated 3 times
May 30 01:54:18 zoop miniupnpd[83505]: ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument
May 30 01:54:18 zoop miniupnpd[83505]: Failed to add NAT-PMP 16402 udp->172.16.1.102:16402 'NAT-PMP 16402 udp'
May 30 01:54:18 zoop miniupnpd[83505]: ioctl(dev, DIOCGETRULES, ...): Invalid argument
May 30 01:54:18 zoop miniupnpd[83505]: ioctl(dev, DIOCGETRULES, ...): Invalid argument
May 30 01:54:18 zoop kernel: arp: 172.16.1.101 moved from 98:d6:bb:0a:4c:00 to 00:26:bb:6d:6f:c7 on bge1
May 30 01:54:30 zoop miniupnpd[83505]: ioctl(dev, DIOCGETRULES, ...): Invalid argument
May 30 01:54:30 zoop miniupnpd[83505]: ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument
May 30 01:54:30 zoop miniupnpd[83505]: Failed to add NAT-PMP 4500 udp->172.16.1.102:4500 'NAT-PMP 4500 udp'
May 30 01:54:30 zoop miniupnpd[83505]: ioctl(dev, DIOCGETRULES, ...): Invalid argument
May 30 01:54:30 zoop last message repeated 2 times
May 30 01:54:30 zoop miniupnpd[83505]: ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument
May 30 01:54:30 zoop miniupnpd[83505]: ioctl(dev, DIOCGETRULES, ...): Invalid argument
May 30 01:54:33 zoop miniupnpd[83505]: HTTP Connection closed unexpectedly
May 30 01:54:33 zoop miniupnpd[83505]: ioctl(dev, DIOCGETRULES, ...): Invalid argument


I've tried adding the PF_NEWSTYLE definition and building pf fails with:

Code:
./genconfig.sh: WARNING: $ipfilter_enable is not set properly - see rc.conf(5).
Using pf
Configuring compilation for [FreeBSD] [10.1-RELEASE] with [pf] firewall software.
Please edit config.h for more compilation options.
$/usr/ports/net/miniupnpd/work/miniupnpd-1.9 # cd pf
$/usr/ports/net/miniupnpd/work/miniupnpd-1.9/pf # make
cc -Wall -g -ansi -DTEST -c testobsdrdr.c
testobsdrdr.c:122:10: warning: format specifies type 'unsigned long long' but the argument has type 'u_int64_t' (aka 'unsigned long') [-Wformat]
                       packets, bytes);
                       ^~~~~~~
testobsdrdr.c:122:19: warning: format specifies type 'unsigned long long' but the argument has type 'u_int64_t' (aka 'unsigned long') [-Wformat]
                       packets, bytes);
                                ^~~~~
2 warnings generated.
cc -Wall -g -ansi -DTEST -c obsdrdr.c
obsdrdr.c:170:6: error: no member named 'type' in 'struct pfioc_trans_e'
        ioe.type = PF_TRANS_RULESET;
        ~~~ ^
obsdrdr.c:170:13: error: use of undeclared identifier 'PF_TRANS_RULESET'
        ioe.type = PF_TRANS_RULESET;
                   ^
obsdrdr.c:268:12: error: no member named 'nat' in 'struct pf_rule'
                pcr.rule.nat.addr.type = PF_ADDR_NONE;
                ~~~~~~~~ ^
obsdrdr.c:268:28: error: use of undeclared identifier 'PF_ADDR_NONE'; did you mean 'PF_ADDR_RANGE'?
                pcr.rule.nat.addr.type = PF_ADDR_NONE;
                                         ^~~~~~~~~~~~
                                         PF_ADDR_RANGE
/usr/include/netpfil/pf/pf.h:102:4: note: 'PF_ADDR_RANGE' declared here
          PF_ADDR_RANGE };
          ^
obsdrdr.c:269:12: error: no member named 'rdr' in 'struct pf_rule'
                pcr.rule.rdr.addr.type = PF_ADDR_ADDRMASK;
                ~~~~~~~~ ^
obsdrdr.c:336:12: error: no member named 'rdr' in 'struct pf_rule'
                pcr.rule.rdr.proxy_port[0] = iport;
                ~~~~~~~~ ^
obsdrdr.c:337:12: error: no member named 'rdr' in 'struct pf_rule'
                pcr.rule.rdr.proxy_port[1] = iport;
                ~~~~~~~~ ^
obsdrdr.c:338:39: error: no member named 'rdr' in 'struct pf_rule'
                inet_pton(AF_INET, iaddr, &pcr.rule.rdr.addr.v.a.addr.v4.s_addr);
                                           ~~~~~~~~ ^
obsdrdr.c:339:12: error: no member named 'rdr' in 'struct pf_rule'
                pcr.rule.rdr.addr.v.a.mask.v4.s_addr = htonl(INADDR_NONE);
                ~~~~~~~~ ^
obsdrdr.c:543:21: error: no member named 'rdr' in 'struct pf_rule'
                        *iport = pr.rule.rdr.proxy_port[0];
                                 ~~~~~~~ ^
obsdrdr.c:583:32: error: no member named 'rdr' in 'struct pf_rule'
                        inet_ntop(AF_INET, &pr.rule.rdr.addr.v.a.addr.v4.s_addr,
                                            ~~~~~~~ ^
obsdrdr.c:679:31: error: no member named 'rdr' in 'struct pf_rule'
                        if(iport) *iport = pr.rule.rdr.proxy_port[0];
                                           ~~~~~~~ ^
obsdrdr.c:683:22: error: no member named 'rdr' in 'struct pf_rule'
                                *iaddr = pr.rule.rdr.addr.v.a.addr.v4.s_addr;
                                         ~~~~~~~ ^
obsdrdr.c:841:19: error: no member named 'rdr' in 'struct pf_rule'
        *iport = pr.rule.rdr.proxy_port[0];
                 ~~~~~~~ ^
obsdrdr.c:883:30: error: no member named 'rdr' in 'struct pf_rule'
        inet_ntop(AF_INET, &pr.rule.rdr.addr.v.a.addr.v4.s_addr,
                            ~~~~~~~ ^
obsdrdr.c:1017:17: error: no member named 'rdr' in 'struct pf_rule'
                        (int)pr.rule.rdr.proxy_port[0],
                             ~~~~~~~ ^
obsdrdr.c:1046:18: error: no member named 'rdr' in 'struct pf_rule'
                       pr.rule.rdr.port_op, pr.rule.rdr.opts);
                       ~~~~~~~ ^
obsdrdr.c:1047:48: error: no member named 'rdr' in 'struct pf_rule'
                printf("  %s\n", inet_ntop(AF_INET, &pr.rule.rdr.addr.v.a.addr.v4.s_addr, buf, 32));
                                                     ~~~~~~~ ^
18 errors generated.
*** Error code 1

Stop.
make: stopped in /usr/ports/net/miniupnpd/work/miniupnpd-1.9/pf


Any thoughts?
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1391

PostPosted: Sun May 31, 2015 8:26 pm    Post subject: Reply with quote

well you should check with the FreeBSD miniupnpd port maintainer.
I don't know which version of pf FreeBSD 10.1 is using
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    miniupnp.tuxfamily.org Forum Index -> miniupnpd Compilation/Installation All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
Protected by Anti-Spam ACP
© 2007 Thomas Bernard, author of MiniUPNP.