VOGONS


playing BLOOD online via dosbox.... ????

Topic actions

First post, by franpa

User metadata
Rank Oldbie
Rank
Oldbie

hi, how do we go about doing this? we both have dosbox 0.72 and the game launches but it seems its not using our external IP...

uh, how do we use setup.exe -.- im entirely clear on it either.

edit: hehe http://forums.transfusion-game.com/viewtopic.php?t=1149 this is helpful 😁 ill test it out since its pretty straight forward.

AMD Ryzen 3700X | ASUS Crosshair Hero VIII (WiFi) | 16GB DDR4 3600MHz RAM | MSI Geforce 1070Ti 8GB | Windows 10 Pro x64.

my website

Reply 1 of 25, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Configure your router instead of using Hamachi...

1+1=10

Reply 3 of 25, by franpa

User metadata
Rank Oldbie
Rank
Oldbie

ok. port 23513 is forwarded for both UDP and TCP to my local address. the following is in my dosbox.conf and the status bar talks about 127.0.0.x.x:xx how do we make it use our external IP without hamachi? is it at all possible? im the host so only i should need to port forward correct?

[autoexec]
MOUNT C E:\BLOOD
ipx=true
ipxnet startserver 23513

i can host other games fine like Worms: Armageddon, Duke Nukem 3D (xDuke port) etc. but for the life of me can't make heads or tails of getting the internet functioning in DOSBox... is it possible?

AMD Ryzen 3700X | ASUS Crosshair Hero VIII (WiFi) | 16GB DDR4 3600MHz RAM | MSI Geforce 1070Ti 8GB | Windows 10 Pro x64.

my website

Reply 4 of 25, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Firewall?
How do people try to connect to you?

1+1=10

Reply 5 of 25, by franpa

User metadata
Rank Oldbie
Rank
Oldbie

uh, ipxnet connect 127.0.0.#.# ? the last 2 digits changes each time i host. and the client tried connecting via my internet IP but it also failed

my firewall is set to allow it... i can as i said above, can setup my router/firewall to allow hosting in other games its just that the procedure for setting it all up in dosbox... i have no clue about what the commands do and/or how to use them properly.

ipxnet /? and ipxnet /help is not particularly helpful.

AMD Ryzen 3700X | ASUS Crosshair Hero VIII (WiFi) | 16GB DDR4 3600MHz RAM | MSI Geforce 1070Ti 8GB | Windows 10 Pro x64.

my website

Reply 6 of 25, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

Network 127.x.x.x is not allowed on the Internet. It is a magic network number, reserved for loopback networks and stuff, so there is NO WAY people will be able to connect to you using that kind of address.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 7 of 25, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

They have to use your internet address to connect.
And you have to take your nonstandard port into account.
ipxnet connect x.x.x.x 23513

1+1=10

Reply 8 of 25, by franpa

User metadata
Rank Oldbie
Rank
Oldbie

yes, but that doesnt work 😮 typing ipxnet startserver doesnt make me use a valid IP ;\ it makes me use 127.0.0.x.x which just doesnt work.

how do i use the ipx commands so that MY ip is correctly used thus allowing others to connect to me via it? the non-standard port is used because it is a port i have forwarded for both TCP and UDP in my router.

if the transfusion article didnt omit example IP's instead of just #.#.#.#.# then im certain it would be tons easier to work out. so 127.#.#.# is not a correct ip? how do i use ipxnet so that it uses something else?

your example HAL is exactly what i do do! its just that it does not work in dosbox ;\ but everything else i use works after doing exactly what you mentioned. i have already tried with my firewall off.

perhapse, the fault was with the other person ^^ i know that they couldnt install hamachi for some weird reason 😮 and uh.....

AMD Ryzen 3700X | ASUS Crosshair Hero VIII (WiFi) | 16GB DDR4 3600MHz RAM | MSI Geforce 1070Ti 8GB | Windows 10 Pro x64.

my website

Reply 9 of 25, by franpa

User metadata
Rank Oldbie
Rank
Oldbie

ok so the issue might be version mismatch since i got One Unit: Whole Blood v1.21 and the other people have v1.11 standard 😀

and yes, most likely the issue was with the other player 😉

AMD Ryzen 3700X | ASUS Crosshair Hero VIII (WiFi) | 16GB DDR4 3600MHz RAM | MSI Geforce 1070Ti 8GB | Windows 10 Pro x64.

my website

Reply 10 of 25, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Let's have a closer look at the output.

IPXSERVER: Connect from 127.0.0.1
IPX: Connected to server. IPX address is 127:0:0:1:4:34

When you are starting the server, your DOSBox instance runs extra server code, but the rest still is a client that has to connect to the server.
'Connect from 127.0.0.1' just means that your DOSBox has connected to itself. It will always be 127.0.0.1.
The second line comes from the client, saying that it connected to the internal server and which virtual IPX address it got. This has nothing to do with IP.

1+1=10

Reply 11 of 25, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

You might want to start by checking that your firewall allows traffic in on that port:

https://www.grc.com/x/portprobe=23513

The port-probe will also show you which IP-address your opponents should use when connecting to you.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 12 of 25, by franpa

User metadata
Rank Oldbie
Rank
Oldbie
h-a-l-9000 wrote:
Let's have a closer look at the output. […]
Show full quote

Let's have a closer look at the output.

IPXSERVER: Connect from 127.0.0.1
IPX: Connected to server. IPX address is 127:0:0:1:4:34

When you are starting the server, your DOSBox instance runs extra server code, but the rest still is a client that has to connect to the server.
'Connect from 127.0.0.1' just means that your DOSBox has connected to itself. It will always be 127.0.0.1.
The second line comes from the client, saying that it connected to the internal server and which virtual IPX address it got. This has nothing to do with IP.

ah, that makes sense. i followed the transfusion guide and the client fails to connect. i tried it with someone else recently and we got to the point where it said the version mismatched so i assume that A) version mismatch and B) the non-host doesnt have there pc set up right.

that website fails but it could be because my ISP is using a transparent proxy.

AMD Ryzen 3700X | ASUS Crosshair Hero VIII (WiFi) | 16GB DDR4 3600MHz RAM | MSI Geforce 1070Ti 8GB | Windows 10 Pro x64.

my website

Reply 13 of 25, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

Fails? How?

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 14 of 25, by franpa

User metadata
Rank Oldbie
Rank
Oldbie

it just wouldnt connect to me... um if someone here wants to help me test (IE: somone that knows there pc/router is configured right) then buzz me on msn.

AMD Ryzen 3700X | ASUS Crosshair Hero VIII (WiFi) | 16GB DDR4 3600MHz RAM | MSI Geforce 1070Ti 8GB | Windows 10 Pro x64.

my website

Reply 15 of 25, by franpa

User metadata
Rank Oldbie
Rank
Oldbie

ok, i type the following because port 50100 is open correct?
ipxnet start 50100

the client just types ipxnet connect xxx.xxx.xxx:50100 ? or do they exclude the port? either way the client simply fails to connect.

must UDP/emulation be enabled in the conf file? im pretty sure i tested that switch at both values for both me and the client with no impact.

AMD Ryzen 3700X | ASUS Crosshair Hero VIII (WiFi) | 16GB DDR4 3600MHz RAM | MSI Geforce 1070Ti 8GB | Windows 10 Pro x64.

my website

Reply 16 of 25, by MiniMax

User metadata
Rank Moderator
Rank
Moderator
franpa wrote:

ok, i type the following because port 50100 is open correct?

How on Earth would we, or would we not, know if it is open or not?
Is it written in your local constitution?

franpa wrote:

the client just types ipxnet connect xxx.xxx.xxx:50100 ?

And xxx.xxx.xxx is what?? Your shoe size?

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 17 of 25, by ADDiCT

User metadata
Rank Oldbie
Rank
Oldbie

Yeah, this is becoming ridiculous. franpa, maybe you should read up on basic TCP/IP configuration, and try to be a bit more structured with your reports. Looking at how chaotic your posts are, this thread could go on for all eternity.

To be a bit more helpful:
- Set ipx=true in dosbox.conf on _both computers_
- Decide which frigging port above 1024 to use, and use that one from now on, and no other!
- Open that port in the firewalls of all computers you want to have in your virtual network, and forward the port (TCP and UDP, just to be safe) to the computer running the server (probably through the router with which that machine connects to the internet). The client has to connect to the Internet IP of the server, or it's LAN IP if the client's inside your LAN
- Read the DOSBox readme for the _exact_ syntax of the network related commands. There's no damn ":" between the IP adress and the port number!

I didn't try DOSBox' IPX emulation myself yet, but from reading the readme, it all seems very obvious to me. If you have a friend that's been playing multiplayer games over the internet, he may be able to help you.

Reply 19 of 25, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Then create one once you got it working.