So I might need a TURN Server in the cloud. This is the All-Server-Releay.
And The windows-service and the Mobile-App will connect as clients to that TURN server.
STUN is way easier to use and better than TURN, also STUN is everywhere and you don't need to own a STUN server, you can use the google one and any other.
Also don't be misinformed by many resources that STUN is only UDP, STUN is
TCP too.
You need to know the difference between the two, well it is complicated a little, so from
https://en.wikipedia.org/wiki/Traver...ays_around_NAT
Code:
TURN does not aid in running servers on well known ports in the private network through a NAT; it supports the connection of a user behind a NAT to only a single peer, as in telephony, for example.
While STUN is
https://en.wikipedia.org/wiki/STUN and in support
TCP per provider.
I think I might need a Service that acts as All-Client-Relay between TURN Server and Windows-Service.
All Relays(at least 2) should not "tunnel" but "Translate"/"foward" the data.
Well you got the idea, but again TURN is different from what you are assuming.
I would suggest to stick IPv6, but from what i read most mobile providers limit its functionality, see, IPv6 come with different routing mechanism and in theory any
IP (IPv6) address should be reached because there is no NAT, no subnet and masking is ownership, which is included.