View previous topic :: View next topic |
Author |
Message |
perazim
Joined: 04 Oct 2012 Posts: 6
|
Posted: Thu Oct 04, 2012 2:09 pm Post subject: upnpc problems on openwrt |
|
|
Running current trunk build of openwrt and included the upnpc client program. This is an openvpn appliance in the form of a customized router that sits behind a second openwrt gateway router that has the upnpd configured and running.
I can run upnpc -s without troubles from a pc on the same LAN subnet of the second router that also has the first router plugged.
However when using a ssh session on the first router to run:
root@Subnet-172:~# upnpc -s
upnpc : miniupnpc library test client. (c) 2006-2011 Thomas Bernard
*** This line deleted so I can post - was web address ***
for more information.
No IGD UPnP Device found on the network !
root@Subnet-172:~#
I don't see any connection to the second gateway router.
The first router is running default NAT and it is the WAN port that is plugged into the second router's LAN port. I have tried entering a rule to open port 1900 without change.
Anybody know what is wrong here?
Thanks,
Perazim |
|
Back to top |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Thu Oct 04, 2012 10:41 pm Post subject: |
|
|
how much network interface do you have on this Subnet-172 machine ?
try upnpc -a eth0 -s _________________ Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
Back to top |
|
|
perazim
Joined: 04 Oct 2012 Posts: 6
|
Posted: Fri Oct 05, 2012 10:12 am Post subject: |
|
|
I have the following interfaces: eth0 -LAN, eth1 - WAN, br-lan - bridged LAN + wireless
I see that there is no -v option to check the version of upnpc so I don't know at this point. It is from the openwrt trunk repository.
The help info states that -m ip/interface sets the ip or interface to use. When I try this I get:
root@Subnet-172:~# upnpc -m eth1 -s
upnpc : miniupnpc library test client. (c) 2006-2011 Thomas Bernard
Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
for more information.
setsockopt: Cannot assign requested address
No IGD UPnP Device found on the network !
root@Subnet-172:~#
When I try upnpc -a eth1 -s, I get the help menu.
Maybe this is an outdated version???
Perazim |
|
Back to top |
|
|
perazim
Joined: 04 Oct 2012 Posts: 6
|
Posted: Fri Oct 05, 2012 10:36 am Post subject: |
|
|
Looking in the openwrt.org repository, I see the following versions:
miniupnpc-1.5-1
miniupnpd-1.5.2.20110309-2
Perazim |
|
Back to top |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
|
Back to top |
|
|
perazim
Joined: 04 Oct 2012 Posts: 6
|
Posted: Sun Oct 07, 2012 10:52 am Post subject: |
|
|
Using "upnpc -m 192.168.1.197 -s" I see that packets go to the gateway router but I still receive the timeout response. Here is a wireshark capture of the exchange. Note the long time after the initial SSDP packets are sent by the client that responses return:
No. Time Source S-Port Destination D-Port Protocol Info
32958 0.000000 192.168.1.197 32958 239.255.255.250 1900 SSDP M-SEARCH * HTTP/1.1
Frame 1: 179 bytes on wire (1432 bits), 179 bytes captured (1432 bits)
Ethernet II, Src: Tp-LinkT_af:c1:53 (f8:d1:11:af:c1:53), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.197 (192.168.1.197), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 32958 (32958), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source S-Port Destination D-Port Protocol Info
32958 2.002116 192.168.1.197 32958 239.255.255.250 1900 SSDP M-SEARCH * HTTP/1.1
Frame 2: 174 bytes on wire (1392 bits), 174 bytes captured (1392 bits)
Ethernet II, Src: Tp-LinkT_af:c1:53 (f8:d1:11:af:c1:53), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.197 (192.168.1.197), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 32958 (32958), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source S-Port Destination D-Port Protocol Info
32958 4.002240 192.168.1.197 32958 239.255.255.250 1900 SSDP M-SEARCH * HTTP/1.1
Frame 3: 175 bytes on wire (1400 bits), 175 bytes captured (1400 bits)
Ethernet II, Src: Tp-LinkT_af:c1:53 (f8:d1:11:af:c1:53), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.197 (192.168.1.197), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 32958 (32958), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source S-Port Destination D-Port Protocol Info
32958 6.004335 192.168.1.197 32958 239.255.255.250 1900 SSDP M-SEARCH * HTTP/1.1
Frame 4: 143 bytes on wire (1144 bits), 143 bytes captured (1144 bits)
Ethernet II, Src: Tp-LinkT_af:c1:53 (f8:d1:11:af:c1:53), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.197 (192.168.1.197), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 32958 (32958), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source S-Port Destination D-Port Protocol Info
37935 13.824269 192.168.1.1 37935 239.255.255.250 1900 SSDP NOTIFY * HTTP/1.1
Frame 5: 445 bytes on wire (3560 bits), 445 bytes captured (3560 bits)
Ethernet II, Src: Tp-LinkT_23:54:b5 (f8:d1:11:23:54:b5), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.1 (192.168.1.1), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 37935 (37935), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source S-Port Destination D-Port Protocol Info
37935 13.824477 192.168.1.1 37935 239.255.255.250 1900 SSDP NOTIFY * HTTP/1.1
Frame 6: 517 bytes on wire (4136 bits), 517 bytes captured (4136 bits)
Ethernet II, Src: Tp-LinkT_23:54:b5 (f8:d1:11:23:54:b5), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.1 (192.168.1.1), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 37935 (37935), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source S-Port Destination D-Port Protocol Info
37935 13.824653 192.168.1.1 37935 239.255.255.250 1900 SSDP NOTIFY * HTTP/1.1
Frame 7: 513 bytes on wire (4104 bits), 513 bytes captured (4104 bits)
Ethernet II, Src: Tp-LinkT_23:54:b5 (f8:d1:11:23:54:b5), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.1 (192.168.1.1), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 37935 (37935), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source S-Port Destination D-Port Protocol Info
37935 13.824791 192.168.1.1 37935 239.255.255.250 1900 SSDP NOTIFY * HTTP/1.1
Frame 8: 493 bytes on wire (3944 bits), 493 bytes captured (3944 bits)
Ethernet II, Src: Tp-LinkT_23:54:b5 (f8:d1:11:23:54:b5), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.1 (192.168.1.1), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 37935 (37935), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source S-Port Destination D-Port Protocol Info
37935 13.825012 192.168.1.1 37935 239.255.255.250 1900 SSDP NOTIFY * HTTP/1.1
Frame 9: 525 bytes on wire (4200 bits), 525 bytes captured (4200 bits)
Ethernet II, Src: Tp-LinkT_23:54:b5 (f8:d1:11:23:54:b5), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.1 (192.168.1.1), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 37935 (37935), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source S-Port Destination D-Port Protocol Info
37935 13.825188 192.168.1.1 37935 239.255.255.250 1900 SSDP NOTIFY * HTTP/1.1
Frame 10: 507 bytes on wire (4056 bits), 507 bytes captured (4056 bits)
Ethernet II, Src: Tp-LinkT_23:54:b5 (f8:d1:11:23:54:b5), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.1 (192.168.1.1), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 37935 (37935), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source S-Port Destination D-Port Protocol Info
37935 13.825365 192.168.1.1 37935 239.255.255.250 1900 SSDP NOTIFY * HTTP/1.1
Frame 11: 509 bytes on wire (4072 bits), 509 bytes captured (4072 bits)
Ethernet II, Src: Tp-LinkT_23:54:b5 (f8:d1:11:23:54:b5), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.1 (192.168.1.1), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 37935 (37935), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
No. Time Source S-Port Destination D-Port Protocol Info
37935 13.825583 192.168.1.1 37935 239.255.255.250 1900 SSDP NOTIFY * HTTP/1.1
Frame 12: 509 bytes on wire (4072 bits), 509 bytes captured (4072 bits)
Ethernet II, Src: Tp-LinkT_23:54:b5 (f8:d1:11:23:54:b5), Dst: IPv4mcast_7f:ff:fa (01:00:5e:7f:ff:fa)
Internet Protocol, Src: 192.168.1.1 (192.168.1.1), Dst: 239.255.255.250 (239.255.255.250)
User Datagram Protocol, Src Port: 37935 (37935), Dst Port: ssdp (1900)
Hypertext Transfer Protocol |
|
Back to top |
|
|
perazim
Joined: 04 Oct 2012 Posts: 6
|
Posted: Sun Oct 07, 2012 8:20 pm Post subject: |
|
|
FYI: I have requested the openwrt package maintainer to update the packages to the latest versions.
Perazim |
|
Back to top |
|
|
perazim
Joined: 04 Oct 2012 Posts: 6
|
Posted: Fri Oct 12, 2012 8:30 pm Post subject: |
|
|
Resolved this issue. The reply to the initial packet was being dropped by the openwrt NAT firewall on WAN. It took several attempts to finally figure this out and correct it by placing a rule for this in iptables.
I have a follow-up question if you will:
Your mail page states that NAT-PNP was added to MiniUPnP. Does this mean that two different protocols are supported by unpnc? If so, I have opened the NAT firewall for a response from the gateway router from its port 1900. Do I also need to accommodate a response from the gateway router for a second port?
Thanks,
Peraziim |
|
Back to top |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Sat Oct 13, 2012 10:55 pm Post subject: |
|
|
perazim wrote: |
Your mail page states that NAT-PNP was added to MiniUPnP. Does this mean that two different protocols are supported by unpnc? If so, I have opened the NAT firewall for a response from the gateway router from its port 1900. Do I also need to accommodate a response from the gateway router for a second port?
|
miniUPnPd does support NAT-PMP, but miniUPnPc does not !
See http://miniupnp.free.fr/libnatpmp.html _________________ Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
Back to top |
|
|
zapy
Joined: 24 Jan 2011 Posts: 5
|
Posted: Fri Mar 22, 2013 2:08 pm Post subject: |
|
|
hi guys!
i dunno but i seem to have a similar problem with an application that uses miniupnp and my pfsense firewall!
The software is HLSW, a RCON and Game Server Browser, when enabeling upnp it seems it finds the router and all but it dosnt add the mappings.
Now i wonder if this is a router problem or HLSW problem with an old upnp library.
pFsense i am using is: 2.0.2-RELEASE (i386)
built on Fri Dec 7 16:30:14 EST 2012
If this isn't related to the the user with the first problem, break this out and create a new thread.
I am on IRC #pfsense @ freenode as well
edit.
The creator of hlsw used a pretty old version but he didn't know which version, he was going to try and update it to a newer one this weekend though.
Heres a wireshark dump:
Code: | NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: upnp:rootdevice
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::upnp:rootdevice
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:device:InternetGatewayDevice:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:device:InternetGatewayDevice:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:device:WANConnectionDevice:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:device:WANConnectionDevice:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:device:WANDevice:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:device:WANDevice:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:service:WANIPConnection:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:service:WANIPConnection:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:service:WANPPPConnection:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:service:WANPPPConnection:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:service:Layer3Forwarding:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:service:Layer3Forwarding:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: upnp:rootdevice
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::upnp:rootdevice
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:device:InternetGatewayDevice:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:device:InternetGatewayDevice:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:device:WANConnectionDevice:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:device:WANConnectionDevice:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:device:WANDevice:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:device:WANDevice:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:service:WANIPConnection:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:service:WANIPConnection:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:service:WANPPPConnection:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:service:WANPPPConnection:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=60
lOCATION: http://192.168.1.1:2189/rootDesc.xml
SERVER: FreeBSD/8.1-RELEASE-p11 UPnP/1.1 MiniUPnPd/1.7
NT: urn:schemas-upnp-org:service:Layer3Forwarding:1
USN: uuid:b83134d4-7795-641b-9dcc-d71328c5120::urn:schemas-upnp-org:service:Layer3Forwarding:1
NTS: ssdp:alive
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 1
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1337
|
(edited for lisibility) |
|
Back to top |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Sat Mar 23, 2013 9:44 am Post subject: |
|
|
@zapy your wireshark capture includes NOTIFY SSDP packets from the pfSense router, but no M-SEARCH request from your client (HLSW)
make sure it tries to discover UPNP on the right network interface, or that firewall isn't preventing it to send packets _________________ Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
Back to top |
|
|
zapy
Joined: 24 Jan 2011 Posts: 5
|
Posted: Sat Mar 23, 2013 11:37 am Post subject: |
|
|
miniupnp wrote: | @zapy your wireshark capture includes NOTIFY SSDP packets from the pfSense router, but no M-SEARCH request from your client (HLSW)
make sure it tries to discover UPNP on the right network interface, or that firewall isn't preventing it to send packets |
firewall as in software firewall? the windows firewall is off, just uses the router as fw.
i enabled port tcp/udp 1900 from lan -> wan in the router dest any on both sides, no luck.
can choose network card in the hlsw application, and i only have one active card, second one is a vpn connection thats offline if i not use it. |
|
Back to top |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Sat Mar 23, 2013 2:38 pm Post subject: |
|
|
Have you tried the upnpc command line tool ? _________________ Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
Back to top |
|
|
zapy
Joined: 24 Jan 2011 Posts: 5
|
Posted: Thu Mar 28, 2013 7:35 pm Post subject: |
|
|
miniupnp wrote: | Have you tried the upnpc command line tool ? |
hi, sorry for late reply.
i couldnt find that tool?
edit* found it
Code: | H:\Users\Rikard\Desktop\upnpc-exe-win32-20121009>upnpc-static.exe -s
upnpc : miniupnpc library test client. (c) 2006-2012 Thomas Bernard
Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
desc: http://192.168.1.2:49153/wps_device.xml
st: uuid:00000000-0000-1000-0000-204e7f5afb08
desc: http://192.168.1.2:49153/wps_device.xml
st: upnp:rootdevice
desc: http://192.168.1.1:2189/rootDesc.xml
st: urn:schemas-upnp-org:device:InternetGatewayDevice:1
Found valid IGD : http://192.168.1.1:2189/ctl/IPConn
Local LAN ip address : 192.168.1.100
Connection Type : IP_Routed
Status : Connected, uptime=1024s, LastConnectionError : ERROR_NONE
Time started : Thu Mar 28 20:19:46 2013
MaxBitRateDown : 100000000 bps (100.0 Mbps) MaxBitRateUp 100000000 bps (100.0 Mbps)
ExternalIPAddress = 83.251.2.235
Bytes: Sent: 15831687 Recv: 58862626
Packets: Sent: 42977 Recv: 66428 |
Code: | H:\Users\Rikard\Desktop\upnpc-exe-win32-20121009>upnpc-static.exe -l
upnpc : miniupnpc library test client. (c) 2006-2012 Thomas Bernard
Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
desc: http://192.168.1.2:49153/wps_device.xml
st: upnp:rootdevice
desc: http://192.168.1.2:49152/wps_device.xml
st: upnp:rootdevice
desc: http://192.168.1.1:2189/rootDesc.xml
st: urn:schemas-upnp-org:device:InternetGatewayDevice:1
Found valid IGD : http://192.168.1.1:2189/ctl/IPConn
Local LAN ip address : 192.168.1.100
Connection Type : IP_Routed
Status : Connected, uptime=1051s, LastConnectionError : ERROR_NONE
Time started : Thu Mar 28 20:19:46 2013
MaxBitRateDown : 100000000 bps (100.0 Mbps) MaxBitRateUp 100000000 bps (100.0 Mbps)
ExternalIPAddress = 83.251.2.235
i protocol exPort->inAddr:inPort description remoteHost leaseTime
0 UDP 8034->192.168.1.102:8034 'NAT-PMP 8034 udp' '' 2977
1 TCP 8034->192.168.1.102:8034 'NAT-PMP 8034 tcp' '' 2977
2 TCP 36014->192.168.1.102:36014 'uTorrent (TCP)' '' 0
3 UDP 36014->192.168.1.102:36014 'uTorrent (UDP)' '' 0
GetGenericPortMappingEntry() returned 713 (SpecifiedArrayIndexInvalid)
|
Code: | H:\Users\Rikard\Desktop\upnpc-exe-win32-20121009>upnpc-static.exe -r 12345 TCP
upnpc : miniupnpc library test client. (c) 2006-2012 Thomas Bernard
Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
desc: http://192.168.1.2:49153/wps_device.xml
st: upnp:rootdevice
desc: http://192.168.1.2:49152/wps_device.xml
st: upnp:rootdevice
desc: http://192.168.1.1:2189/rootDesc.xml
st: urn:schemas-upnp-org:device:InternetGatewayDevice:1
Found valid IGD : http://192.168.1.1:2189/ctl/IPConn
Local LAN ip address : 192.168.1.100
ExternalIPAddress = 83.251.2.235
InternalIP:Port = 192.168.1.100:12345
external 83.251.2.235:12345 TCP is redirected to internal 192.168.1.100:12345 (duration=0) |
|
|
Back to top |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
|
Back to top |
|
|
|
|
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
© 2007 Thomas Bernard, author of MiniUPNP.
|