Renegade Public Forums
C&C: Renegade --> Dying since 2003™, resurrected in 2024!
Home » Technical Support » Win32 FDS » Updated TT Release: WOLProxy v1.2
icon2.gif  Updated TT Release: WOLProxy v1.2 [message #217417] Tue, 05 September 2006 02:41 Go to previous message
Crimson is currently offline  Crimson
Messages: 7429
Registered: February 2003
Location: Phoenix, AZ
Karma:
General (5 Stars)
ADMINISTRATOR
WOLProxy v1.2 Copyright © 2004-2011 Tiberian Technologies

Change log:
2011 Jan 28 - Release v1.2
- Updated for changes to XWIS IP/port

2006 Sept 03 - Release v1.1
- Automatic reconnection to WOL
- Automatic detection of WOL nonresponse to map start command, sends fake response to FDS to prevent it from crashing
- IP banning with wild cards, effective for preventing IP harvesting bots and exploiters. (Not an effective ban for players)

v1.00
- Initial release


CREDITS -
v1.0 - v00d00 (v00d00 Net Services) - initial concept and release
v1.1, 1.2 - Crimson - Auto-reconnect functionality, ip banning

------------------------------------------------------------ --
INSTALLATION INSTRUCTIONS:
* Open your "hosts" file, usually located at C:\Windows\system32\drivers\etc\hosts

* Add the following line to the bottom of the file:
999.999.999.999    xwis.net

CHANGE 999.999.999.999 to your server's PUBLIC IP address!

* Download the software from this thread and unzip it wherever you'd like.

* Launch mirc.exe. You should see a purple message saying that it's listening on 3 ports. If you see an error, make sure that you are not running any other version of WOLProxy. Close the previous version and restart this version.

* Launch or restart your Renegade Servers. You will see relevant messages in the application as the servers connect to XWIS. You will also see messages and errors if XWIS goes offline as it tries to reconnect. Your server will stay online through an outage, even if the map changes on your server.


Known issues:
- When your server reconnects to XWIS, the player count will say 0 in the server listings. There is no way to fix this, as this number is reported by the XWIS server.
- Verbiage in this app remains "WOL" instead of XWIS in order to keep the naming conventions the same
- You will see a lot of errors if XWIS remains offline for more than a few seconds as the FDS tries to send commands to XWIS. An upcoming release will check to make sure that the connection to XWIS is active before attempting to forward communication from the FDS.
- This is written in mIRC. Sorry, but this saved me several hours of work writing from scratch.

I'm the bawss.

[Updated on: Fri, 28 January 2011 21:19]

Report message to a moderator

[Message index]
 
Read Message icon2.gif
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: FDS SERIALS & XWIS
Next Topic: FDS Resources / fixes [updated by Goztow]
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Nov 27 21:23:04 MST 2024

Total time taken to generate the page: 0.01125 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 420.69.
Copyright ©2001-2023 FUDforum Bulletin Board Software