Difference between revisions of "Connectivity"

From DOSBoxWiki
Jump to: navigation, search
(DOSBox Local Network configuration)
(Moved in info from duplicated articles)
Line 1: Line 1:
The below article is directed from a free resource which the link is stated at below line:
+
DOSBox networking works in a client-server architecture, where one machine acts as a server and all the others connect to it as its clients. DOSBox emulates outdated protocols and actually routes them to Internet's own IP protocol (TCP/IP for serial/modem emulation and the even better UDP/IP for IPX emulation).
http://www.dedoimedo.com/games/reviving/dosbox_multiplayer.html
+
  
The name of the author was undisclose, however, speacial thanks to the original author for contributing this information.
+
== IPX emulation ==
 
+
 
+
== Enjoying multiplayer games on LAN in DOSBox - IPX ==
+
 
+
 
+
By now, you have already discovered that I'm a bit of an old games fan. Using DOSBox is probably the simplest, most sensible way of enjoying your old favorites. But so far, I have only shown you the single player mode. DOSBox also allows you to setup multiplayer games.
+
 
+
 
+
If you have more than one computer and would like to enjoy a session of Doom, Warcraft or any other 90s classic, then read on.
+
 
+
This article will show you how to setup multiplayer games using IPX protocol. A follow-up article will demonstrate how to play even older games using direct serial connection.
+
 
+
 
+
 
+
== DOSBox Local Network configuration ==
+
 
+
=== Enable IPX Networking Emulation ===
+
 
First, we must enable IPX networking emulation.
 
First, we must enable IPX networking emulation.
  
Line 25: Line 7:
  
 
You can find the '''dosbox.conf''' by browsing '''Start > All Programs > Dosbox'''
 
You can find the '''dosbox.conf''' by browsing '''Start > All Programs > Dosbox'''
 
  
 
[[Image:Dosbox_config.png]]
 
[[Image:Dosbox_config.png]]
 
  
 
Inside the file, search for an entry labeled [ipx]. Below the explanation comment (marked with #), change the configuration line from ipx=false to ipx=true as shown in the example below.
 
Inside the file, search for an entry labeled [ipx]. Below the explanation comment (marked with #), change the configuration line from ipx=false to ipx=true as shown in the example below.
Line 38: Line 18:
  
 
You might find it hard to believe, but this is ALL of the tampering with the configuration files you will need.
 
You might find it hard to believe, but this is ALL of the tampering with the configuration files you will need.
 
  
 
=== Start IPX server ===
 
=== Start IPX server ===
Line 46: Line 25:
 
On the server machine, execute the following command:
 
On the server machine, execute the following command:
  
  ipxnet startserver
+
  ipxnet startserver [UDP port]
  
 
See screenshot below:
 
See screenshot below:
Line 52: Line 31:
 
[[Image:dosbox_lan_02.png]]
 
[[Image:dosbox_lan_02.png]]
  
 +
UDP port is optional. Otherwise it defaults to 213 (the assigned IANA port for IPX tunnelling). If you want another port, for example, port 19900, type:
 +
ipxnet startserver 19900
 +
 +
If you change the default, it's customary to choose something above 1024 as anything below is considered reserved. In Linux specifically, only root (or superuser) can use port numbers lower than 1024.
 +
 +
Whatever UDP port is chosen (including the default), '''it must be forwarded and open to the outside network if a server is hidden behind a router (NAT)'''.
  
 
=== Start client(s) ===
 
=== Start client(s) ===
Line 57: Line 42:
 
On each one of the clients, run the following command to connect to the server:
 
On each one of the clients, run the following command to connect to the server:
  
  ipxnet connect <IP >
+
  ipxnet connect <IP> [UDP port]
  
 
Specifically, in my case:
 
Specifically, in my case:
Line 67: Line 52:
 
[[Image:dosbox_lan_03.png]]
 
[[Image:dosbox_lan_03.png]]
  
You now have the network running.
+
Port is optional. The same rules apply as in [[#Start IPX server]]. For example:
 +
ipxnet connect 192.168.2.100 19900
  
 +
You now have the network running. You can confirm it by:
 +
  IPXNET STATUS
 +
If you want to check the speed and/or see the list of server and all clients, type:
 +
  IPXNET PING
  
'''Start your games'''  
+
'''Start your game'''  
  
Yes, that's it! I have tested this setup on a network where both clients sit behind a router and run a personal firewall. Everything worked (and works) flawlessly. The one thing you may have to do is allow DOSBox network access in your firewall rules.
+
If you're done, but want to remain in DOSBox, the clients can optionally use the following commands:
 +
  IPXNET DISCONNECT
 +
and only after all clients disconnect (or you'll risk locking them up), the server can type:
 +
  IPXNET STOPSERVER
  
== How to Obtain Computer's IP ==
+
== Modem emulation==
There are many several ways to obtain a computer's IP address in a local network.
+
First, define [[Configuration:SerialPort]].
  
Below are one of the common way:
+
If you change the default TCP port, it's customary to choose something above 1024 as anything below is considered reserved. In Linux specifically, only root (or superuser) can use port numbers lower than 1024.
 +
 
 +
Whatever TCP port is chosen (including the default 5000), '''it must be forwarded and open to the outside network if a server is hidden behind a router (NAT)'''.
 +
 
 +
==The game's modem options==
 +
You must enter the game's modem options and:
 +
* Define the same COM number as you chose in DOSBox. If the game is hardcoded to a certain COM number, this must be the one you choose in DOSBox.
 +
* Choose the highest modem's speed the game allows.
 +
* <sup>''For [[#Emulating making a call|clients only]]''</sup> If there's an address book, you can define the server in advance. Actually, some games might refuse to call anyone that's not listed in advance in the address book.
 +
* The other game's modem options don't matter in DOSBox.
 +
 
 +
Exit the settings, enter the game itself and find the call/answer menu entry.
 +
 
 +
===Emulating answering a call===
 +
Some games may want you to define an auto-answer command in advance, while others may want you to answer manually when the call comes in. Some may allow both modes.
 +
 
 +
In the first mode, the server should choose the "wait for calls" option in their game. If the game wants you to type a manual command, use "ATS0=1" (answer on first call).
 +
 
 +
In the second mode, the server should choose the "answer call" option when the game announces a call is coming in. If the game wants you to type a manual command, use "ATA".
 +
 
 +
===Emulating making a call===
 +
The client should choose the "make a call" option in their game. Then supply the server's hostname or IP address.
 +
 
 +
If the game wants you to type a manual command, use "ATDT<IP>". For example, if the server is "hosty" <1.2.3.4>, type:
 +
ATDT1.2.3.4
 +
or
 +
ATDThosty
 +
 
 +
== How to obtain computer's IP address==
 +
===The quick and advanced way===
 +
If you're not afraid of the command prompt (surely if you use DOSBox without a frontend), browse to '''Start > All Programs > Accessories > Command Prompt'''. Once there, type "ipconfig".
 +
 
 +
===The long but user friendly way===
  
 
Go to "My Network Place"
 
Go to "My Network Place"
Line 84: Line 109:
  
 
[[Image:Network_settings1.png]]
 
[[Image:Network_settings1.png]]
 
  
 
Right Click the Network that you are using and choose "Status", then, you will be able to obtain the computer's IP address in a local network.
 
Right Click the Network that you are using and choose "Status", then, you will be able to obtain the computer's IP address in a local network.
 
  
 
[[Image:Network_settings2.png]]
 
[[Image:Network_settings2.png]]
  
 
+
==External links==
 
+
* [http://www.dedoimedo.com/games/reviving/dosbox_multiplayer.html dedoimedo.com] (the original article plus screenshots from actual multiplayer games)
== Setting up Modem ==
+
- empty -
+
no article yet, please help in editting this section.
+

Revision as of 12:47, 23 December 2009

DOSBox networking works in a client-server architecture, where one machine acts as a server and all the others connect to it as its clients. DOSBox emulates outdated protocols and actually routes them to Internet's own IP protocol (TCP/IP for serial/modem emulation and the even better UDP/IP for IPX emulation).

IPX emulation

First, we must enable IPX networking emulation.

Find and open the dosbox.conf file (the configuration file for DOSBox); it should be located in the DOSBox directory.

You can find the dosbox.conf by browsing Start > All Programs > Dosbox

Dosbox config.png

Inside the file, search for an entry labeled [ipx]. Below the explanation comment (marked with #), change the configuration line from ipx=false to ipx=true as shown in the example below.

[ipx]
# ipx -- Enable ipx over UDP/IP emulation.

ipx=true

You might find it hard to believe, but this is ALL of the tampering with the configuration files you will need.

Start IPX server

Power on DOSBox on all the computers that you want to participate in the LAN games. One of these computers will have to act as a server. The rest will be clients.

On the server machine, execute the following command:

ipxnet startserver [UDP port]

See screenshot below:

Dosbox lan 02.png

UDP port is optional. Otherwise it defaults to 213 (the assigned IANA port for IPX tunnelling). If you want another port, for example, port 19900, type:

ipxnet startserver 19900

If you change the default, it's customary to choose something above 1024 as anything below is considered reserved. In Linux specifically, only root (or superuser) can use port numbers lower than 1024.

Whatever UDP port is chosen (including the default), it must be forwarded and open to the outside network if a server is hidden behind a router (NAT).

Start client(s)

On each one of the clients, run the following command to connect to the server:

ipxnet connect <IP> [UDP port]

Specifically, in my case:

ipxnet connect 192.168.2.100 

See screenshot below:

Dosbox lan 03.png

Port is optional. The same rules apply as in #Start IPX server. For example:

ipxnet connect 192.168.2.100 19900

You now have the network running. You can confirm it by:

 IPXNET STATUS

If you want to check the speed and/or see the list of server and all clients, type:

 IPXNET PING

Start your game

If you're done, but want to remain in DOSBox, the clients can optionally use the following commands:

 IPXNET DISCONNECT 

and only after all clients disconnect (or you'll risk locking them up), the server can type:

 IPXNET STOPSERVER

Modem emulation

First, define Configuration:SerialPort.

If you change the default TCP port, it's customary to choose something above 1024 as anything below is considered reserved. In Linux specifically, only root (or superuser) can use port numbers lower than 1024.

Whatever TCP port is chosen (including the default 5000), it must be forwarded and open to the outside network if a server is hidden behind a router (NAT).

The game's modem options

You must enter the game's modem options and:

  • Define the same COM number as you chose in DOSBox. If the game is hardcoded to a certain COM number, this must be the one you choose in DOSBox.
  • Choose the highest modem's speed the game allows.
  • For clients only If there's an address book, you can define the server in advance. Actually, some games might refuse to call anyone that's not listed in advance in the address book.
  • The other game's modem options don't matter in DOSBox.

Exit the settings, enter the game itself and find the call/answer menu entry.

Emulating answering a call

Some games may want you to define an auto-answer command in advance, while others may want you to answer manually when the call comes in. Some may allow both modes.

In the first mode, the server should choose the "wait for calls" option in their game. If the game wants you to type a manual command, use "ATS0=1" (answer on first call).

In the second mode, the server should choose the "answer call" option when the game announces a call is coming in. If the game wants you to type a manual command, use "ATA".

Emulating making a call

The client should choose the "make a call" option in their game. Then supply the server's hostname or IP address.

If the game wants you to type a manual command, use "ATDT<IP>". For example, if the server is "hosty" <1.2.3.4>, type:

ATDT1.2.3.4

or

ATDThosty

How to obtain computer's IP address

The quick and advanced way

If you're not afraid of the command prompt (surely if you use DOSBox without a frontend), browse to Start > All Programs > Accessories > Command Prompt. Once there, type "ipconfig".

The long but user friendly way

Go to "My Network Place"

Click on "View My Network Connections"

Network settings1.png

Right Click the Network that you are using and choose "Status", then, you will be able to obtain the computer's IP address in a local network.

Network settings2.png

External links

  • dedoimedo.com (the original article plus screenshots from actual multiplayer games)