cyprex wrote:I have tried that and neither option works. There are far more ports involved than 80 and 9999.
I believe the problem is with the GIT Advanced Configuration.
Could those of you who have gotten it working post a screenshot of their advanced configuration menu?
Clueless wrote:anyone figured out the correct config for nfs:u2 and is able to provide some screenshots ?
Shaamaan wrote:PS. What does "Alter source IP (for NAT)" do, and how do I use it?
--------------------------------
Notes specific to TCP/IP and UDP
--------------------------------
Since TCP, UDP, and ICMP packets are all routable over the Internet, it is
normally not necessary to forward anything but broadcast UDP packets, which
are not routed over the Internet. The default option under Advanced
Configuration will have "Don't Send Unicast" checked, which will make GIT only
forward packets sent to addresses like 255.255.255.255. Some games will use a
mix of TCP and UDP, where the clients locate the game via UDP broadcast
packets, but then connect directly to the game server via TCP. This will work
fine with GIT as long as the game server is not firewalled or using NAT.
If the game server is firewalled, you must open up the game port on the
firewall to allow incomming traffic to the server. If the game server is
using NAT, you can adjust for this in the Advanced Configuration window by
selecting the "Alter Source IP" checkbox, and filling in the hostname or IP
address of both your internal address and external address.
For example, I have seen successful setups for Warcraft 3 under all of the
above connections at once. The game server was both behind a firewall and
using NAT, while the clients were also behind a firewall. The firewall on
the server side was configured to allow incoming connections for port 213 (for
GIT) and port 6112 (for WC3) and was set to map its internal address of
10.1.1.2 to its real external address using GIT. Only UDP broadcast packets
were tunneled with GIT. Once the clients located the WC3 server address,
they connected directly to it via TCP and played normally from there.
ErMeglio wrote:Hi to all...thanks for all those information but I must say I wasn't able to make it working.
I explain my config:
I have and ethernet modem connected to adsl with
internet ip let's say: 82.55.192.111
ethernet modem ip: 192.168.1.1
wireless router with ip on wan : 192.168.1.5
router ip on wired/wireless lans: 192.168.123.254
the wireless pc I want to use git and nfsu2 on has ip 192.168.123.103
Users browsing this forum: No registered users and 133 guests