View previous topic :: View next topic |
Author |
Message |
philophax
Joined: 11 Jul 2019 Posts: 3
|
Posted: Fri Jul 12, 2019 12:59 am Post subject: Different External IP Addresses on different OSes |
|
|
Salutations,
I experienced some strange behaviors while using upnpc 2.1. I tried it on:
* macOS 10.14.5 (installed through MacPorts, IP 192.168.1.7);
* Windows (VMWare, Server 2019 & 10 1903, built from the source taken from MacPorts, IP 192.168.1.99).
My IGD is a Technicolor TG589Bvn (a.k.a. b-box 3 in Belgium).
1) upnpc -l
* on macOS:
Found valid IGD : http: //192.168.1.1:5000/gLeyorx/ctl/IPConn
ExternalIPAddress = 81.247.169.252
The right IP, my dynamic DNS host refers to it.
* on Windows:
Found a (not connected?) IGD : http: //192.168.1.1:5000/gLeyorx/ctl/IPConn
ExternalIPAddress = 10.135.17.243
Some mappings related to the TV decoder are listed.
2) upnpc -a 192.168.1.99 5900 55999 tcp (IP is Windows host)
* on macOS:
AddPortMapping(55999, 5900, 192.168.1.99) failed with code 718 (ConflictInMappingEntry)
Upnpc fails. I can't figure out where could the conflict be. There is no mapping on this port in my IGD UI.
* on Windows:
external 10.135.17.243:55999 TCP is redirected to internal 192.168.1.99:5900 (duration=0)
Upnpc ran successfully but, of course, the mapping is on the wrong external IP.
3) It seems it is only possible to map ports to the host we are working on.
upnpc -a 192.168.1.7 1021 22222 tcp (IP is mscOS host)
fails on Windows but works on macOS.
After a successful run (on macOS), although port is open on local machine and mapping appears in the IGD UI, nmap returns a closed state for port 22222.
Many thanks in advance for your help. |
|
Back to top |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Sun Aug 11, 2019 5:06 pm Post subject: |
|
|
what it the exact version used on windows ?
you compiled it yourself from sources ? _________________ Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
Back to top |
|
|
philophax
Joined: 11 Jul 2019 Posts: 3
|
Posted: Mon Aug 12, 2019 10:29 pm Post subject: |
|
|
This is miniupnpc 2.1 source taken from MacPorts.
Yes, I installed MinGW then ran mingw32make. I just had to remove the '?' from "GCC ?= gcc" in Makefile.mingw. Everything has been built correctly. |
|
Back to top |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Thu Aug 15, 2019 9:56 pm Post subject: |
|
|
Your windows machine is a VirtualMachine in VMWare :
Are you sure is it configured for Bridged network ? _________________ Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
Back to top |
|
|
philophax
Joined: 11 Jul 2019 Posts: 3
|
Posted: Sun Aug 18, 2019 11:05 pm Post subject: |
|
|
Yes, it is.
I had a try on Windows 10 but not on a VM, using the version built on my VM. The external IP is correct; upnpc did the job correctly. The port mapping is reported in my IGD UI; netstat reports that the port list listening on the right interface; nmap reports that the port is closed (on the external IP). I checked whether another port would be open instead; nmap tells nothing abnormal.
It seems that running upnpc on a VM is a bad idea. Anyone could deal with it.
I guess my IGD is bugged. |
|
Back to top |
|
|
|