... ok ... again... ... just read the pdf link for comsocks/tune brewder posted more carefully...
... however, I'm
not sure, maybe you should wait for someone else to have a look
at this - try it
only and
only if you want to waste some time -
Ok then ... the first config is supposed to enable you to use the ingame server browser,
if it doesn't work, try the second one to connect to a single vengeance server ...
... both configs assume that 192.168.1.1 is the box w. comsocks, and 192.168.1.2 is
the client with vengeance ...
Configuration A)You'll have to make a port mapping for each port veng/merc uses - using dxport, which you already do, will minimize your work:
Create one port-mapping for each port from 2302 to (and including) 2311,
call them mwvengudp1-mwvengudp10
Sample:
----
Port Mapping's Name: mwvengudp1
Proxy IP Adress Port: 0.0.0.0:2302
Destination Name or IP:192.168.1.2 Port: 2302
Transport: udp
rule: generic
Bi-directional udp-mapping: check
----
... then you'll have to do it again for tcp
Create one port-mapping for each port from 2302 to (and including) 2311,
call them mwventcp1-mwvengtcp10
Sample:
----
Port Mapping's Name: mwvengtcp1
Proxy IP Adress Port: 0.0.0.0:2302
[0.0.0.0 stands for any address, as you don't want to this for every server you want to connect to]
Destination Name or IP:192.168.1.2 Port: 2302
Transport: tcp
----
... then add another one:
---
Port Mapping's Name: moredirectplay1
Proxy IP Adress Port: 0.0.0.0:6073
Destination Name or IP:192.168.1.2 Port: 6073
Transport: tcp
---
... and another one:
---
Port Mapping's Name: moredirectplay2
Proxy IP Adress Port: 0.0.0.0:9110
Destination Name or IP:192.168.1.2 Port:9110
Transport: udp
rule: generic
Bi-directional udp-mapping: check
---
... and another one:
---
Port Mapping's Name: moredirectplay3
Proxy IP Adress Port: 0.0.0.0:47624
Destination Name or IP:192.168.1.2 Port:47624
Transport:tcp
---
... and finally one for zonematch:
---
Port Mapping's Name: zonematch
Proxy IP Adress Port: 0.0.0.0:27999
Destination Name or IP:192.168.1.2 Port: 27999
Transport: uhhh dunno ... anyone?
---
Configuration B ) This should at least enable to connect to a single vengeance server, you need to
have it's IP "vengserverIP" however - it will work the same way with mercs.
Create one port-mapping for each port from 2302 to (and including) 2311,
call them vservudp1-versvudp10
Sample:
----
Port Mapping's Name:vservudp1
Proxy IP Adress Port: 192.168.1.1:2302
Destination IP: vengserverIP [insert actual IP here
]
Destination Port: 2302
Transport: udp
rule: generic
Bi-directional udp-mapping: check
----
... then you'll have to do it again for tcp
Create one port-mapping for each port from 2302 to (and including) 2311, call them vengtcp1-vengtcp10
Sample:
----
Port Mapping's Name: vengtcp1
Proxy IP Adress Port: 192.168.1.1:2302
Destination Name or IP:vengserverIP Port: 2302
Transport: tcp
----
... then add another one:
---
Port Mapping's Name: moredirectplay1
Proxy IP Adress Port: 192.168.1.1:6073
Destination Name or IP:vengserverIP Port: 6073
Transport: tcp
---
... and another one:
---
Port Mapping's Name: moredirectplay2
Proxy IP Adress Port: 192.168.1.1:9110
Destination Name or IP:vengserverIP Port:9110
Transport: udp
rule: generic
Bi-directional udp-mapping: check
---
... and another one:
---
Port Mapping's Name: moredirectplay3
Proxy IP Adress Port: 192.168.1.1:47624
Destination Name or IP:vengserverIP Port:47624
Transport:tcp
---
... now you should be able to connect to a single server, using
192.168.1.1 instead of the servers actual IP address. Start dxport, start veng ...
@brewder et al: looking at the comsocks/comtune manual, mainly the section on half-life and
quake, it seems comsocks needs the servers IP address for udp mappings - if that's the case, I'd say only Configuration B ) can possibly work?
)
aahhh.
