rec.autos.simulators

try looking at www.vroc.net they should have some help there

See you soon on vroc

--
The first ever pinball ezboard !!
http://pub7.ezboard.com/bpinball

"Don't touch that please, your primitive intellect wouldn't understand
alloys and compositions and,......things with molecular structures,....and
the....." - Ash

What worked for me was while you had VROC open, hit Ctrl o (or bring up the
options) then check the path of your GPL.  While mine was set right, I
clicked like I was going to chose another folder (which it won't let you do)
then clicked on the correct one.  Shut down VROC, opened it back up, and was
able to ping, host and join races.

If that doesn't work, make sure you have the current IP racelist (check the
VROC site)

Good luck

Billy

blue, and red?  R U running

Ahh, connected through another PC on the LAN... that might be the
problem. Is this using Microsofts Internet Connection Sharing (useless),
or are you using a proxy?

If you are using a proxy, I suggest you set up port forwarding for
the appropriate ports which VROC uses (not sure which ones, do a quick
search on www.google.com). If youre using the built in windows internet
connection sharing, then I'm not sure its possible, use a proxy instead.

I might be barking up the wrong tree here mind, but its worth a shot.

"Don't touch that please, your primitive intellect wouldn't understand
alloys and compositions and,......things with molecular structures,....and
the....." - Ash

readme11.txt

5. MULTIPLAYER - FIREWALLS
--------------------------

With GPL 1.0.0.0 it was difficult, if not impossible, to configure a firewall that would allow a GPL
client or server to run behind it.  This should now be fixed.  GPL now uses a range of 21
consecutive ports ([32766..32786], by default) for client/server communications, and  ports 6970 for
status broadcast and 6971 for ping responses.

To run from a machine with a private IP address behind a Linux firewall, you need to use a
combination of IP masquerading and IP autoforwarding.  The following three rules can be used.

ipfwadm -F -a accept -m -S a.a.a.a/m.m.m.m -D 0.0.0.0/0
ipautofw -A -r udp 6970 6971 -h a.a.a.a -v -u
ipautofw -A -r udp 32766 32786 -h a.a.a.a -v -u

where a.a.a.a is the address of the machine behind the firewall, and m.m.m.m is the netmask.  If you
run a server behind the firewall, clients should connect to the IP address of the firewall.

If you want to run more than one server behind a firewall, you'll need to give each of the servers
its own port range for client/server communications, and also include these port ranges in the
ipautofw rules.  In core.ini on each of the additional server machines, add the following:

[ Communications ]
net_server_port = A

You might use A=32787 for the second server, A=32808 for the third server, etc.

If you want to allow machines outside your firewall (VROC, for example) to query the status of
multiple GPL servers, you must also make provisions for this.  The best way we've found to do this
is to use an ipautofw rule for GPL's ping port (port 6971) that causes the firewall to forward
incoming GPL ping requests to the directed broadcast address of the network behind the firewall.
Use the rule

ipautofw -A -r udp 6970 6971 -h b.b.b.b -v -u

where b.b.b.b is the directed broadcast address of the network behind the firewall.

Broadcast address?  What's that?  A broadcast is a message that you want every system on the network
to see.  The broadcast address is the address that all machines on the same network listen to for
this message.  In this case, the ipautofw command is saying that you want all udp packets on ports
6970..6971 to go to all the machines behind your firewall.

How do I determine the broadcast address?  Easy:  Address | (NOT NetMask)
Take your ip address and convert it to binary:
 Decimal->172.15.134.123
 Binary->10101100.00001111.10000110.01111011
Take your netmask and convert it to binary, then invert the 0 and 1's:
 Decimal->255.255.255.0
 Binary->11111111.11111111.11111111.00000000
 Invert->00000000.00000000.00000000.11111111
Take your address and bitwise-or in the inverted netmask address:
 10101100.00001111.10000110.01111011
 00000000.00000000.00000000.11111111
 -----------------------------------
 10101100.00001111.10000110.11111111
Finally, convert back to decimal
 Binary->10101100.00001111.10000110.11111111
 Decimal->172.15.134.255
So that b.b.b.b would be 172.15.134.255 in this example.

If you (or your network administrator) do not want to broadcast these packets, you'll need to assign
each GPL server its own ping port in core.ini

[ Communications ]
bcast_ping_port = B

For example, you might use B=6972 for the second server, B=6973 the third server, etc.  You will
also need to include these ports in your ipautofw rule, and tell anyone that might want to ping
these servers about these other ports.

"Don't touch that please, your primitive intellect wouldn't understand
alloys and compositions and,......things with molecular structures,....and
the....." - Ash