Page 1 of 1

TCP/UDP ports to open behind network Firewall

Posted: Tue Dec 09, 2014 12:27 pm
by Hkklm
Using P3D 2.4
I struggle since days to connect to pilotedge, because I have to know, which TCP /UDP ports will be in use to set up the Firewall of our network correctly. Managed to have a Basic Login, the plane can be seen in the PE map with correct callsign, but no voice Connection in or out is established. So this should be a Problem with the TSP3 UDP Settings of your Network. To do the work right without trying days by accident, please tell me the right port ranges in and out. I am shure, there are plenty enough pilots, searching the same Information, because for largr network-Setups, a dedicated Firewall is mandatory.

Thanks for your help, looking forward to connect properly HK

Re: TCP/UDP ports to open behind network Firewall

Posted: Wed Dec 10, 2014 2:34 pm
by Hkklm
Solved - installed a port sniffer, recording all used UDP and TCP requests by the PEsoftware and used this for firewall settings...working now

Re: TCP/UDP ports to open behind network Firewall

Posted: Wed Dec 10, 2014 3:06 pm
by wmburns
why not list the port numbers in case someone else has the same problem?

Re: TCP/UDP ports to open behind network Firewall

Posted: Wed Dec 10, 2014 3:12 pm
by Hkklm
Could be a firewall safety issue, by I will get the necessary port list the next days from my "paranoid" network guys and will offer it for support, maybe per PM, have to check it before...

Re: TCP/UDP ports to open behind network Firewall

Posted: Wed Dec 10, 2014 3:21 pm
by Rick Stratman
Yea all network guys/gals are a joy to work with :)

Re: TCP/UDP ports to open behind network Firewall

Posted: Wed Dec 10, 2014 8:56 pm
by MervA
Gents, this has been cover elsewhere, see

viewtopic.php?f=14&t=1252&p=16213&hilit ... rts#p16213

Re: TCP/UDP ports to open behind network Firewall

Posted: Wed Dec 10, 2014 11:51 pm
by Hkklm
Thanks, had this information before, but did not work for our dedicated firewall ( not the WIN firewall within a single computer, but a complete security system) ...the "sniff logging" proofed, that there are many TCP and UDP requests and connections in the background linked to PEclient...maybe the two ports we knew before are working for a router, but for our firewall system, it was no solution. Now it IS working, we will analyze it with our " IT watchdogs" the next days, give you the results depending on security issues posted or via PM...but this can be a serious factor, people don't try or stop trying so real impressive initiatives like PE (as I can overview it as an IRME licensed Pilot in Europe but unexperienced in USA skies...)

Re: TCP/UDP ports to open behind network Firewall

Posted: Thu Dec 11, 2014 9:52 pm
by MervA
Ok, roger that, it's one of THOSE systems. ;)


Cya !

Merv

Re: TCP/UDP ports to open behind network Firewall

Posted: Mon Dec 15, 2014 10:41 am
by Keith Smith
9986 UDP for voice, 5558 TCP for data.