Difference between revisions of "WormNAT2"

From Worms Knowledge Base

Jump to: navigation, search
(update zip filesize)
(move WormNAT2.svg to appropriate location within the page)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{ParentArticle|[[WormKit]]}}
 
{{ParentArticle|[[WormKit]]}}
 +
{{Languages|en|WormNAT2|ru|WormNAT2/ru}}
 
{{Software_infobox
 
{{Software_infobox
 
| icon = WormNAT.gif
 
| icon = WormNAT.gif
 
| name = WormNAT 2
 
| name = WormNAT 2
 
| developer = [[People/CyberShadow|CyberShadow]]
 
| developer = [[People/CyberShadow|CyberShadow]]
 +
| version = 2.3 / August 22, 2015
 
| games = [[Worms Armageddon|W:A]]
 
| games = [[Worms Armageddon|W:A]]
 
| waver = 3.6.28.0+
 
| waver = 3.6.28.0+
 
| language = Delphi
 
| language = Delphi
 
| license = [https://github.com/CyberShadow/WormKit Open-source]
 
| license = [https://github.com/CyberShadow/WormKit Open-source]
| download = [http://worms.thecybershadow.net/wormkit/wkWormNAT2.zip wkWormNAT2.zip (100 KB)]
+
| download = [http://worms.thecybershadow.net/wormkit/wkWormNAT2.zip wkWormNAT2.zip (92 KB)]
 
}}
 
}}
[[Image:WormNAT2.svg|thumb|A crude drawing of how WormNAT2 works]]
 
 
[[WormNAT2]] is a [[WormKit]] module which enables players behind NAT or firewalls to host games which are joinable by everyone. It is a rewrite of the first WormNAT module, which required extensive configuration and that all players have the module installed.
 
[[WormNAT2]] is a [[WormKit]] module which enables players behind NAT or firewalls to host games which are joinable by everyone. It is a rewrite of the first WormNAT module, which required extensive configuration and that all players have the module installed.
  
Line 19: Line 20:
 
* games are hosted as usual, there is no need to configure the game settings with tedious text commands
 
* games are hosted as usual, there is no need to configure the game settings with tedious text commands
  
 +
== Usage ==
 +
 +
If other players time out when trying to join your hosted games, and nobody joins, you can follow these steps.
 +
 +
# In WA -> options (bottom-right) -> "Advanced", enable "Load WormKit modules".
 +
# Ensure no unexpected "wk*.dll" files are in your WA installation folder, where WA.exe is located. The option in step 1 causes WA to load these, so any that you don't know about could cause unexpected behavior that may be disruptive or even dangerous.
 +
# Download wkWormNAT2.zip.
 +
# Extract the contents of wkWormNAT2.zip to your WA installation folder, where WA.exe is located.
 +
 +
After these steps, installation is done. You can now run the game and host as normal using the "Host" button in WormNET and other players should no longer time out when trying to join your games.
 +
 +
If you don't want to connect to other players through a proxy server and still want to be able to host without issues, you can configure hosting manually with the information in the [[Hosting guide|hosting guide]].
 +
 +
[[Image:WormNAT2.svg|thumb|A crude drawing of how WormNAT2 works]]
 
== How it works ==
 
== How it works ==
WormNAT2 works by asking a ''reverse proxy'' (which is running the HostingProxy software) to host the game for the player. A control connection is opened to the proxy server, '''proxy.worms2d.info''' on port 17018. As soon as the connection is established, the proxy assigns a port for the game and sends back the port number through the control connection. WormNAT2 creates the game at the address '''proxy.worms2d.info:''port'''''.  
+
WormNAT2 works by asking a ''reverse proxy'' (which is running the HostingProxy software) to host the game for the player. A control connection is opened to the proxy server, '''proxy.wormnet.net''' on port 9301. As soon as the connection is established, the proxy assigns a port for the game and sends back the port number through the control connection. WormNAT2 creates the game at the address '''proxy.wormnet.net:''port'''''.  
  
 
Once the game is created, every time a new player connects to the proxy, the proxy creates a new listening port for WormNAT2 and sends the port number through the control connection. WormNAT2 then connects to the specified port; the proxy then proceeds to route data between the two connections.
 
Once the game is created, every time a new player connects to the proxy, the proxy creates a new listening port for WormNAT2 and sends the port number through the control connection. WormNAT2 then connects to the specified port; the proxy then proceeds to route data between the two connections.

Latest revision as of 20:12, 31 July 2020

(Up to WormKit)
In other languages: English (en) • русский (ru) • +/-
icon WormNAT 2
Developer: CyberShadow
Latest version: 2.3 / August 22, 2015
Supported games: W:A
Supported W:A version: 3.6.28.0+
Language: Delphi
License: Open-source
Download: wkWormNAT2.zip (92 KB)

WormNAT2 is a WormKit module which enables players behind NAT or firewalls to host games which are joinable by everyone. It is a rewrite of the first WormNAT module, which required extensive configuration and that all players have the module installed.

The advantages of WormNAT2 over WormNAT / HostingBuddy / Hamachi:

  • very easy to set up (extract WormNAT2 DLLs to W:A folder, enable "Load WormKit modules" in Advanced Settings)
  • no configuration is necessary
  • anyone can join games hosted with WormNAT2
  • games are hosted as usual, there is no need to configure the game settings with tedious text commands

Usage

If other players time out when trying to join your hosted games, and nobody joins, you can follow these steps.

  1. In WA -> options (bottom-right) -> "Advanced", enable "Load WormKit modules".
  2. Ensure no unexpected "wk*.dll" files are in your WA installation folder, where WA.exe is located. The option in step 1 causes WA to load these, so any that you don't know about could cause unexpected behavior that may be disruptive or even dangerous.
  3. Download wkWormNAT2.zip.
  4. Extract the contents of wkWormNAT2.zip to your WA installation folder, where WA.exe is located.

After these steps, installation is done. You can now run the game and host as normal using the "Host" button in WormNET and other players should no longer time out when trying to join your games.

If you don't want to connect to other players through a proxy server and still want to be able to host without issues, you can configure hosting manually with the information in the hosting guide.

A crude drawing of how WormNAT2 works

How it works

WormNAT2 works by asking a reverse proxy (which is running the HostingProxy software) to host the game for the player. A control connection is opened to the proxy server, proxy.wormnet.net on port 9301. As soon as the connection is established, the proxy assigns a port for the game and sends back the port number through the control connection. WormNAT2 creates the game at the address proxy.wormnet.net:port.

Once the game is created, every time a new player connects to the proxy, the proxy creates a new listening port for WormNAT2 and sends the port number through the control connection. WormNAT2 then connects to the specified port; the proxy then proceeds to route data between the two connections.

Internally, WormNAT2 operates by monitoring WormNET game creation and closing. Incoming connections are simulated by creating actual connections from within the same process, and routing the data between those connections and connections to the proxy server.

See also

Personal tools