On Thu, 2005-10-13 at 23:30 +0200, Arnt Karlsen wrote: > On Thu, 13 Oct 2005 22:36:43 +0200 (IST), Vassilii wrote in message > <[EMAIL PROTECTED]>: > > > > > + > > > > +Options needed to enable multiplayer game with a server: > > > > Player1: > > > > ---multiplay=out,10,serveraddress,6000 > > > > --multiplay=in,10,myaddress,5500 > > > > I'm confused. The CVS had my patch accepted, I updated from the CVS, > > and I see no occurence of the number 6000 in README.multiplayer now. > > > > > ..this works ok with X in lan's? (X uses port 6000 too.) > > > > Apparently not. > > ..aouch. Ok, the first X session on any box will use port 6000, the > next 6001 etc, similarly 5900, 5901 upwards for vnc etc. > > ..how about putting the server on 5500 "like we have done", and > commandeer 5501 upwards for all clients? > (Assuming they're vacant? Excluding non-FG app ports, > I suspect METAR fetches has an established procedure, > with ports and all.) > Better would be server on 5000, with the telnet "admin" port on 5001.
I'm not sure of the benefit of each client having it's own port. (Perhaps i have misread something) George Patterson _______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
