We call $ upnpc -r 2086 tcp
(or udp) to create the mapping. And $ upnpc -l to check the mapping (for changes) and $ upnpc -d 2086 tcp to remove it. Do those work on your system? On 1/20/19 7:32 PM, Catonano wrote: > > > Il giorno dom 20 gen 2019 alle ore 17:04 Christian Grothoff > <[email protected] <mailto:[email protected]>> ha scritto: > > Have you tried calling upnpc by hand? Does it work then with the port > forwarding? if it does, check how GNUnet calls upnpc, maybe the > command-line syntax has changed / differs on your system!? > > > This is a call to upnpc > > ~$ upnpc -a 192.168.2.45 2086 2086 tcp > upnpc : miniupnpc library test client. (c) 2005-2014 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.2.1:49000/igddesc.xml > st: urn:schemas-upnp-org:device:InternetGatewayDevice:1 > > Found valid IGD : http://192.168.2.1:49000/igdupnp/control/WANIPConn1 > Local LAN ip address : 192.168.2.45 > ExternalIPAddress = 151.45.41.58 > InternalIP:Port = 192.168.2.45:2086 <http://192.168.2.45:2086> > external 151.45.41.58:2086 <http://151.45.41.58:2086> TCP is redirected > to internal 192.168.2.45:2086 <http://192.168.2.45:2086> (duration=0) > > but I don't now how Gnunet is calling it, if it's calling it > > This is on Ubuntu 18.04.1 > > Now I'm a bit tired > > I'll try again tomorrow > > Thanks !
signature.asc
Description: OpenPGP digital signature
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
