Dissidia 012: Duodecim Final Fantasy

[xfxradeon]

(11-12-2015 01:36 PM)Shinoda Wrote:  The problem with Dissidia is that for 1 on 1 battles, the Ports it uses are somewhat random. Sniffed couple of match ups. They seem to be within a certain range but couldn't do enough research to figure what the actual range is. That creates the problem with Port Forwarding. Every new matchup gets a port assigned to both players by the server and host (not server) waits for guest (client) to connect to it on that port, turning Host into what is now essentially a server at that point for the duration of the matchup. There's no exact port to Forward or open with Dissidia. Hence DMZ. I'll do more research soon since we're getting deeper into it and I'm not alone looking into this now and share what I find.

The rooms themselves I think use a static port, which is why players can see eachother before a challenge is made. After challenge is accepted, "Challenger" takes the role of server at "port whatever" pro ad-hoc server and/or the game itself give them...

I managed to sniff out 3 ports that went out and back for this :

53672 from client to server through port 80
From server port 80 back to client through 53672

53673 from client to server through port 80
From server port 80 back to client through 53673

and

53671 from client to server through port 80
From server port 80 back to client through 53671

These were transmission requests to connect to the server from the client that I just performed.

Through the Keep Alive TCP connection the client uses is port 53698 to 27312(which this is the Adhoc Pro server at this point.) then from 27312 back out to 53698 to the client. I am assuming that this is then the lobby port.

I need more people to help test with me so I can capture ports that this game is using. I will also be in the chat for direct communication as well.