azuur wrote:How does the internal / External work? What does that do?
What are you referring to specifically here?
azuur wrote:I have been messing with GIT over pptp, which works great for most parts, but the client is sending the packets with its public IP.
Are you referring to the packets GIT tunnels, or the tunneled packets GIT sends to the other GIT?
The packets GIT sends to the other GIT are sent using normal winsock interfaces and are sent as windows sees fit. The packets GIT captures and tunnels inside of these packets are captured exactly as the application that send them made them. GIT does not modify these packets except for the 'alter source IP for nat' option, which is almost always a BAD idea to use, unless you KNOW for a fact that its what you want.
azuur wrote:I'm going to give it a try through the firewall and see how that works, any tips for 2 clients on a "LAN" game, one behind NAT, the other with a public IP.
This depends on the game. Some games can not at all, in any way, work with that kind of network setup, unless maybe you install a virtual network adapter on the non-NAT one and use the same subnet and IP range as the other computer with NAT, but use a different IP.