pvpgn / pvpgn-server

Next generation of PvPGN server

Home Page:https://pvpgn.pro

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Normal Ladder melee seems to not work at all.

WC3Forever opened this issue · comments

I can connect from any PC on the LAN so far and test every seems good.
Except I cant play or join ladder games with any combination i try.

Also only 1 of the PC's is able to host with port 6112 the rest of the PCs cant host. Why is that? the old blizzard bnet could allow anyone to host all using the 6112 port. Why wont it work that way on the LAN with this server?

commented

Did you set up w3route address_translation.conf correctly?

i havent touched the address_translation file yet. I want to get everything working on the server first within the lan before making it publicly accessible. I would think ladder/melee would come working default.. not sure why its not. Do you have a server with it working? i'm using the newest version of the server out and only for wc3.

commented

You say you connect on LAN but then you also say you need to port forward 6112 which makes no sense. Port forward is only needed for clients connecting on your external IP, not behind the NAT. If your PvPGN and other PC are on the same subnet (lets say 192.168.1.X) it should work out of the box afaik.

Yeah i know but thats what i'm saying it doesn't work out of the box like that. I didnt say port-forward i only said hosting with port 6112 as in thats the port in the wc3 client on all PC's. I was saying when PCs are connecting to a server over the internet they can all use port 6112 to connect to the old bnet server so i would think all my PCs on the LAN could also use the same 6112 port in the wc3 clients. I shouldn't have to change those wc clients on different PCs to different ports within the LAN right?

Also what i was saying is 1 PC out of 4 (on the LAN) is able to host the rest cant for some reason.
No i tested with my sister from a different house last night and she is able to now connect to my server and capable of hosting. I am also able to connect internally but unable to host myself. (but thats probably because i haven't edited anything in the address_translation file yet.)

Also ladder doesn't work at all in any combination tried and that is the main issue i'm trying to solve here.

commented

I will try to build on local machine and try to join ladder from LAN sometime this week. I usually deploy on servers and it works there for sure.

commented

If your friend is joining your local pvpgn through port forwarding and you are joining through LAN you most definitely need to configure address translation. This case is explicitely mentioned in the config documentation. As for deploying on server, it is exactly the same, you just need to know some linux basics and you buy a cheap VPS for a few $$ (can get them for less than 5€ a month).

commented

One thing to clarify, your friend can join your pvpgn so that means you have port forwarded 6112 on your router to point to your pvpgn correct? If you port forwarded 6112->pvpgn then you can't host on 6112 because it conflicts with your game. Try to change your host port in w3 game settings to 6113 and add 6113->your pc host forward.

Then try to host a CG game and check if your ports are actually open for hosting, you can use this tool: https://www.yougetsignal.com/tools/open-ports/

For address translation, put your public IP as w3route address so that way you and your friend will be able to access it.

As for CG no, pvpgn does not track CG games in any way.

commented

This is as far as I could get it to work:

laptop 1: running pvpgn and w3 on 192.168.1.X
laptop 2: joined on mobile hotspot to emulate external client

  1. Port forward 6112, 6200 and 6118
  2. In address_translation.conf:

Expose w3route server:
0.0.0.0:6200 [your public ip]:6200 192.168.1.0/24 ANY

Expose your LAN client to external client:
[your LAN ip]:6118 [your public ip]:6118 192.168.1.0/24,10.0.0.0/8 ANY
127.0.0.1:6118 [your public ip]:6118 192.168.1.0/24 ANY

  1. Open your w3, go to game settings and set host port to 6118
  2. Enter bnet with both clients
  3. Host a custom game with local client
  4. Verify that 6200 and 6118 are open with yougetsignal
  5. Join CG game from client 2. Should work. In bnetd.log you should see that it translated 127.0.0.1 o your public IP
  6. Now port forward client 2 and verify again with a CG game that it can also host
  7. Now that both are verified to be able to host a CG game try a quickgame. You should be able to match and overcome the loading screen. With any luck, you should be able to start the game. If yo get disconnected after loading screen I am not sure anymore what the problem would be, I have not been able to figure out some of the address translation quirks. In some of my experiments a few months ago I came to the conclusion that W3 in some scenarios aborts on translated addresses. Your only option at that point is to host your server somewhere externally.

@WC3Forever same problem happens with ghostbots too, the thing is locally pvpgn runs on 6112 ghostbots/ladder games work on that port too, so even locally you cannot run two things on same port you must change port for ladder/hostbots etc, so for testing i usually set hostport for bots to something other than 6112 and it works, might help you too, and i guess address translation is exactly for this.