[bf1942] BF1942 / BFV servers not showing in ASE

[Steven Hartland]

RE: [bf1942] BF1942 / BFV servers not showing in ASEI wish that where the issue but unfortunately its not. As you said is
game port + 123 is the query port regardless of the value given to
game.ASEPort, which although not optimal is liveable with.

Here's and example of the real issue:
game port = 20000
query port = 20123

When the server is running it announces this fact to the masters server by
sending a "heartbeat" packet via is query port when the master receives
this packet it sends a "status" packet to the query port to get the
information about the server for the list.
This is where it all falls down. Even though the server's query port is
1. The source of the heartbeat
2. Listed in the "heartbeat" packet
The master is sending said "status" packet to the default ASE query port
23000. Not surprisingly it doesn't get a response and hence the issue.

In summary:
1. game.ASEPort is broken; not too much of an issue more of an annoyance
2. bfv currently announces itself as bf1942 again not right but at least the
server is listed.
3. none standard port server are not being listed due to a bug on the ASE
master code not due to a library issue as far as I can see.

For a full packet trace of this happening see my forum post:
http://www.udpsoft.com/forum/topic.cgi?forum=3&topic=1491&start=20

    Steve / K

----- Original Message ----- 
  From: Andy Berdan 
  To: 'bf1942 at icculus.org' 
  Sent: 29 April 2004 13:32
  Subject: RE: [bf1942] BF1942 / BFV servers not showing in ASE


  -----BEGIN PGP SIGNED MESSAGE----- 
  Hash: SHA1 

  > Yer I understand that but is not the issue. 
  > The issue is servers using none standard ports. 

  If you're referring to the game.ASEPort setting, that is broken. 

  UDPSoft did not provide an interface for us to specify the port, so it is always game_port+123, regardless of the game.ASEPort setting.  If firewall ports have been set up according to the game.ASEPort setting, they obviously won't be set up for the right port (thereby blocking ASE communications).

  BTW, because of this, I have disabled the game.ASEPort setting for the time being.  On a good note, UDPSoft did provide a new version of the library after I asked them for this feature.  However, it will likely not be available in the patch, due to testing reasons (I may include it in the linux patch, but I'm rather hesitant about having platform-specific features).

  > When this is done the heartbeat packet contains the details 
  > of the ASE port for the server but the master is still 
  > querying the default port hence any servers on none standard 
  > ports ( which haven't been added manually ) don't get listed. 

  I'm not sure about the heartbeat packet... I'd guess that that should have the right information, since it's all UDPSoft's code.  If it's broken, there's nothing DICE can really do about it, besides wait for a code drop.

  Andy. 
  -----BEGIN PGP SIGNATURE----- 
  Version: GnuPG v1.2.4 (MingW32) 

  iD8DBQFAkPXM8G0w7PWWOXwRAvaiAJ0dqrbURAG7Kmol4VnVflf4+lz9AACfVGzm 
  Iuz2IAcVdqbDV0Q445Yc46c= 
  =h1Rv 
  -----END PGP SIGNATURE----- 


================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 

In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to postmaster at multiplay.co.uk.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/bf1942/attachments/20040429/8abbd6c1/attachment.htm>