|
Home > Archive > Wolfenstein > August 2005 > Socks 5 support for RTCW ?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Socks 5 support for RTCW ?
|
|
| Skybuck Flying 2005-07-30, 12:32 am |
| Hi,
It seems quake 3 had socks 5 support by setting these variables via the
command line:
+set net_socksEnabled 1
+set net_socksServer <socks 5 server address>
+set net_socksPort <socks 5 server port>
It seems these variables are also still present in RTCW (MP Demo).
I tried setting these variables but nothing different happens.
I simply did a quick check of the executable and it does seem that there is
still some SOCKS 5 code in there... ?
Does anybody know if and how RTCW MP Demo could be made to work via SOCKS 5
protocol/encapsulation by simply adjusting the game variables or commands or
maybe even the executable itself ?!? ;) :D
Failing that it would probably still be possibly to use external SOCKS 5
solutions/software/programs... but first I would like to find out if RTCW
has this supported build in and can somehow be activated ;)
Bye,
Skybuck.
| |
| Skybuck Flying 2005-08-16, 8:39 pm |
| Well I just discovered something very interesting.
Yesterday I ran my own server and while looking at the log it did try to
connect to a socks5 server but it said connection refused etc...
Because I set these commands a few weeks ago they ended up into my wolf
config... and today I started the game and I was logging/sniffing it with
ethereal to look for something else... and to my big surprises RTCW actually
connected to a socks 5 server and simply started relaying all udp packets
to/from the socks 5 relay server.
So to make a long story short... rtcw does support socks 5 and it does work
! :D funny.
So far it worked with a socks 5 server which doesn't require any
authentication... but maybe it also works with a username/password socks5
server with empty username and password (anonymous) login.
This is very funny since I developed my own socks5 client and I was planning
on intercepting the rtcw udp datagrams etc... but since the rtcw socks5
support is now working I guess it's no longer really needed :D ;)
Though I did block the wolfmotd.idsoftware.com (192.246.40.70) server with
port 27951 in my firewall to test something else... I don't know if that has
anything to do with it ;) Probably not 
So far I successfully connected to one game server.. but another game server
failed to connect... maybe that game server has firewall banned the socks 5
relay server... could be ;)
More testing will have to be done =D Though connecting with a socks 5 server
might not work the first time etc and you need to find a good one... because
not all socks5 servers are that good... but when you do find a good one
there is a chance that it will work.... funnnnnnnnyyyyyyyy :D
Bye,
Skybuck.
"Skybuck Flying" <nospam@hotmail.com> wrote in message news:...
quote:
> Hi,
>
> It seems quake 3 had socks 5 support by setting these variables via the
> command line:
>
> +set net_socksEnabled 1
> +set net_socksServer <socks 5 server address>
> +set net_socksPort <socks 5 server port>
>
> It seems these variables are also still present in RTCW (MP Demo).
>
> I tried setting these variables but nothing different happens.
>
> I simply did a quick check of the executable and it does seem that there
is
quote:
> still some SOCKS 5 code in there... ?
>
> Does anybody know if and how RTCW MP Demo could be made to work via SOCKS
5
quote:
> protocol/encapsulation by simply adjusting the game variables or commands
or
quote:
> maybe even the executable itself ?!? ;) :D
>
> Failing that it would probably still be possibly to use external SOCKS 5
> solutions/software/programs... but first I would like to find out if RTCW
> has this supported build in and can somehow be activated ;)
>
> Bye,
> Skybuck.
>
>
| |
| Skybuck Flying 2005-08-16, 8:39 pm |
| This is also where the net_restart command comes in handy ;) in the console
:D
Bye,
Skybuck =D
"Skybuck Flying" <nospam@hotmail.com> wrote in message news:...
quote:
> Well I just discovered something very interesting.
>
> Yesterday I ran my own server and while looking at the log it did try to
> connect to a socks5 server but it said connection refused etc...
>
> Because I set these commands a few weeks ago they ended up into my wolf
> config... and today I started the game and I was logging/sniffing it with
> ethereal to look for something else... and to my big surprises RTCW
actually
quote:
> connected to a socks 5 server and simply started relaying all udp packets
> to/from the socks 5 relay server.
>
> So to make a long story short... rtcw does support socks 5 and it does
work
quote:
> ! :D funny.
>
> So far it worked with a socks 5 server which doesn't require any
> authentication... but maybe it also works with a username/password socks5
> server with empty username and password (anonymous) login.
>
> This is very funny since I developed my own socks5 client and I was
planning
quote:
> on intercepting the rtcw udp datagrams etc... but since the rtcw socks5
> support is now working I guess it's no longer really needed :D ;)
>
> Though I did block the wolfmotd.idsoftware.com (192.246.40.70) server with
> port 27951 in my firewall to test something else... I don't know if that
has
quote:
> anything to do with it ;) Probably not
>
> So far I successfully connected to one game server.. but another game
server
quote:
> failed to connect... maybe that game server has firewall banned the socks
5
quote:
> relay server... could be ;)
>
> More testing will have to be done =D Though connecting with a socks 5
server
quote:
> might not work the first time etc and you need to find a good one...
because
quote:
> not all socks5 servers are that good... but when you do find a good one
> there is a chance that it will work.... funnnnnnnnyyyyyyyy :D
>
> Bye,
> Skybuck.
>
> "Skybuck Flying" <nospam@hotmail.com> wrote in message news:...
> is
SOCKS[vbcol=seagreen]
> 5
commands[vbcol=seagreen]
> or
RTCW[vbcol=seagreen]
>
>
|
| |
|
|