| View previous topic :: View next topic |
| Author |
Message |
updogliu
Joined: 15 Feb 2014
Posts: 3
|
 Posted: Sat Feb 15, 2014 11:49 pm Post subject: Do I need miniupnpd to use miniupnpc to do port mapping? |
 |
|
I am trying to add porting mapping on my home rounter (Comcast XFINITY), which has enabled UPnP. I compiled miniupnpc and called
| Code: | | upnpDiscover(10000, nullptr, nullptr, 0, 0, &error); |
It just returned nullptr, and error = 0.
Am I missing something? And how do I diagnose it?
I didn't install miniupnpd. Do I need it for this purpose? |
|
| Back to top |
|
 |
miniupnp
Site Admin
Joined: 14 Apr 2007
Posts: 1589
|
| Posted: Mon Feb 17, 2014 3:04 pm Post subject: |
|
|
indeed it is strange that no device get returned and error = 0.
Does the "upnp-static" program work ?
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
| Back to top |
|
|
pchieffo
Joined: 06 Aug 2014
Posts: 1
Location: Massachusetts, USA
|
| Posted: Wed Aug 06, 2014 2:59 pm Post subject: |
|
|
| I'm seeing the same thing with my Comcast/Xfinity router (Cisco DPC3939). It works right after reboot, but stops working soon after. Once it stops working the only way to get it to respond again is to reboot it. Any suggestions on how best to debug this? |
|
| Back to top |
|
|
miniupnp
Site Admin
Joined: 14 Apr 2007
Posts: 1589
|
| Posted: Tue Aug 26, 2014 6:50 pm Post subject: |
|
|
I believe it is a bug of the router. You should contact Comcast about it.
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
| Back to top |
|
|
jason001
Joined: 18 Jul 2018
Posts: 16
Location: China
|
| Posted: Wed Jul 18, 2018 6:46 am Post subject: same problem |
|
|
whenever I called upnpDiscover, it just returned nullptr, and error = 0.
I could send standard ssdp messages to 239.255.255.250:1900, but received nothing.
I have a router with upnp enabled, and thiswireless router can be seen in the Network, in win7.
I ran upnp_test, and the result is :
TEST 1 - Operating System Support - PASSED
TEST 2 - SSDP Service Running Check - PASSED
TEST 3 - SSDP Service Automatic Check - PASSED
TEST 4 - UPnPHost Service Running Check - PASSED
TEST 5 - UPnPHost Service Automatic Check - PASSED
TEST 6 - UPnP Framework Firewall Exception Check - FAILED
TEST 7 - Adapter #0 - 192.168.0.102 - PASSED
TEST 8 - Get External IP Address (Result: 100.216.19.62) - PASSED
TEST 7 - Adapter #1 - 192.168.52.1 - PASSED
TEST 8 - Get External IP Address (Result: 100.216.19.62) - PASSED
TEST 7 - Adapter #2 - 192.168.121.1 - PASSED
TEST 8 - Get External IP Address (Result: 100.216.19.62) - PASSED
I ran wireshark, and found that the router(192.168.0.1) didn't send any messages to 239.255.255.250:1900.
could you please help me to find out what problems there are, thank you! |
|
| Back to top |
|
|
miniupnp
Site Admin
Joined: 14 Apr 2007
Posts: 1589
|
| Posted: Fri Jul 20, 2018 8:57 am Post subject: |
|
|
The firewall is very likely blocking packets on 239.255.255.250:1900
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
