Hello,
We are trying to connect to a remote GIT server, on the internet, setup to be a TCP listen server. GIT is running on the server with IP forwarding to port 80. (GIT is set to listen on port 80 as well.) The client is behind a corporate firewall that blocks UDP packets and basically only lets traffic out thought HTTP port 80.
We tried all conceivable combinations in GIT with no luck. (We poured over the readme/forums and tried the various settings.) The listen server was logging the client's TCP and ICMP forwards as "OK". But he could never ping the GIT server.
Again, the GIT server has IP forwarding for port 80, so as to match the outgoing HTTP request from the client. Maybe this doesn't matter for the server, but the corporate firewall might not like anything other than port 80. BTW - the firewall does not use a proxy.
I did read this post:
viewtopic.php?t=178&highlight=80
Maybe, because the packets are not true HTTP, the firewall blocks the return. But then why was the client getting OK back as well for TCP and ICMP?
The basic idea is like this:
(client) -> (corporate firewall HTTP port 80) -> (GIT listen server) -> (Game Server)
and the return:
(Game server) -> (GIT listen server) -> (corporate firewall HTTP port 80) -> (client)
So that GIT only acts a bi-directional data stream tunnel. Once established, the connection can pass data back and forth through the HTTP connection port.
Is this possible with GIT?
Thanks.