Re: [Flightgear-devel] new MP server / Netherlands
On Thu, Jan 28, 2010 at 3:23 PM, Brant Gipson ioncannon21...@gmail.com wrote: Contact the domain owner to get a subdomain like mpserver12.flightgear.org Posting here usually qualifies as contacting the domain owner :D By the way, I think something should be done about 02. It is way too overused and seems to have some intermittent relaying problems (even though it is supposed to have IP filtering now). I don't know if the problems are caused by the overload or not, though. What do you think about renaming it to 12? I suggest leaving its slot unused for some time (so that people would realize it is down), and adding the new server (which seems to have plenty of bandwidth) in 03's slot (which has been down for a long time). Eventually some other server could become 02. Reason: I think a lot of people ignore the location of the servers and instead just start from 01 until they find a working one and then just stick to it. So when 01 is down, I expect people to switch to 02 and they stay there even after 01 is back. The situation is made worse by the relay problem - people switch to 02 to see other pilots reliably. Not to mention the rumor that some mac version defaults to 02. My suggestion applies only as long as we don't have a better solution to the MP server choice problem, of course. -- Csaba/Jester -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] new MP server / Netherlands
Hi, internal balancing would be nice. Here is an example conservation between FGFS and FGMS: FGFS: Connects to 01. FGMS01: Reports back that it is full (10 pilots online, e.g.) and includes 03 in its response. 01 knows, that 03 has 3 pilots online FGFS: Reconnects to 03 FGMS03: Reports 3 online pilots and accepts the 4th one Is that possible? Then we don't need people to force to change their configuration and still have some kind of balancing. This, of course, requires some inter-server-communication where they report the amount of online pilots to each other. Regards, Roland signature.asc Description: This is a digitally signed message part -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] new MP server / Netherlands
From: Csaba Halász: By the way, I think something should be done about 02. It is way too overused and seems to have some intermittent relaying problems (even though it is supposed to have IP filtering now). I don't know if the problems are caused by the overload or not, though. What do you think about renaming it to 12? I suggest leaving its slot unused for some time (so that people would realize it is down), and adding the new server (which seems to have plenty of bandwidth) in 03's slot (which has been down for a long time). Eventually some other server could become 02. Reason: I think a lot of people ignore the location of the servers and instead just start from 01 until they find a working one and then just stick to it. So when 01 is down, I expect people to switch to 02 and they stay there even after 01 is back. The situation is made worse by the relay problem - people switch to 02 to see other pilots reliably. Not to mention the rumor that some mac version defaults to 02. I'm not certain about either of the below two statements, so take them with a grain of salt: (1) 02 is filtering out North American IPs as a solution for the excessive bandwidth issues. However, is this not also filtering out relay information from 05 and 07? (2) Doesn't a lot of the original documentation, as well as maybe wiki articles or forum how-tos, etc., use mpserver02 as the example value to put into that slot? Maybe we need to do a thorough search of all of the MP-related documentation? Of course, if the concept of just filling in 02 is that pervasive, then leaving that number unassigned for a while will definitely drive home the point of Find one that works best for you. What about adding a button to FGRun which, when pressed, will ping all of the available MP servers and automatically fill that slot with the one which returned the fastest? Cheers, -R. (MD-Terp) Robert M. Shearman, Jr. Transit Operations Supervisor, University of Maryland Department of Transportation also known as rm...@umd.edu From: Csaba Halász csaba.hal...@gmail.com To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Sent: Thu, January 28, 2010 12:21:59 PM Subject: Re: [Flightgear-devel] new MP server / Netherlands On Thu, Jan 28, 2010 at 3:23 PM, Brant Gipson ioncannon21...@gmail.com wrote: Contact the domain owner to get a subdomain like mpserver12.flightgear.org Posting here usually qualifies as contacting the domain owner :D By the way, I think something should be done about 02. It is way too overused and seems to have some intermittent relaying problems (even though it is supposed to have IP filtering now). I don't know if the problems are caused by the overload or not, though. What do you think about renaming it to 12? I suggest leaving its slot unused for some time (so that people would realize it is down), and adding the new server (which seems to have plenty of bandwidth) in 03's slot (which has been down for a long time). Eventually some other server could become 02. Reason: I think a lot of people ignore the location of the servers and instead just start from 01 until they find a working one and then just stick to it. So when 01 is down, I expect people to switch to 02 and they stay there even after 01 is back. The situation is made worse by the relay problem - people switch to 02 to see other pilots reliably. Not to mention the rumor that some mac version defaults to 02. My suggestion applies only as long as we don't have a better solution to the MP server choice problem, of course. -- Csaba/Jester -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] new MP server / Netherlands
On Thu, Jan 28, 2010 at 6:40 PM, Rob Shearman, Jr. rmsj...@yahoo.com wrote: I'm not certain about either of the below two statements, so take them with a grain of salt: (1) 02 is filtering out North American IPs as a solution for the excessive bandwidth issues. However, is this not also filtering out relay information from 05 and 07? It has some filter that is supposed to keep out unwelcome users, but it isn't working too well. It does make an exception for 05 and 07, though. (2) Doesn't a lot of the original documentation, as well as maybe wiki articles or forum how-tos, etc., use mpserver02 as the example value to put into that slot? Maybe we need to do a thorough search of all of the MP-related documentation? Yeah, would be good to just use mpserverXX as a placeholder. Of course, if the concept of just filling in 02 is that pervasive, then leaving that number unassigned for a while will definitely drive home the point of Find one that works best for you. That was my intention :) What about adding a button to FGRun which, when pressed, will ping all of the available MP servers and automatically fill that slot with the one which returned the fastest? The trouble is, checking ping is not enough. A half-working automatic solution may be even worse than none at all, because people would think it works and care even less about mp server selection. How about adding an on-screen message (ie. not in the terminal) while starting in mp mode, something like: You are now connected to serverXX. Please make sure this is the right one for you. -- Csaba/Jester -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] new MP server / Netherlands
Csaba Halász schrieb: By the way, I think something should be done about 02. It is way too overused and seems to have some intermittent relaying problems (even though it is supposed to have IP filtering now). I don't know if the problems are caused by the overload or not, though. What do you think about renaming it to 12? Maybe we should be careful with such changes without contacting pigeon who is also running the mpmap02 server. Anyway number 11 and 12 are not listed in the map script (goes from 01 to 10 at the moment as I can see). -gral -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] new MP server / Netherlands
On Thu, Jan 28, 2010 at 11:13 PM, HB-GRAL flightg...@sablonier.ch wrote: Csaba Halász schrieb: By the way, I think something should be done about 02. It is way too overused and seems to have some intermittent relaying problems (even though it is supposed to have IP filtering now). I don't know if the problems are caused by the overload or not, though. What do you think about renaming it to 12? Maybe we should be careful with such changes without contacting pigeon who is also running the mpmap02 server. Of course. He is reading this, I assume :) Also, I have mentioned the relay problems to him on IRC already. Anyway number 11 and 12 are not listed in the map script (goes from 01 to 10 at the moment as I can see). Not sure which script you mean, but 11 is up. -- Csaba/Jester -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] new MP server / Netherlands
The MP conversation is interesting. Why should people choose between one or another MP Server : 1. Because it is written in the doc (Wiki, ...) 2. Because they check their latency from their location (which is the best option). 3. Because they choose it based on its location. I don't really know how this is handed in other games, but the easier would be : One domaine name to enter in the config file (mpserver.flightgear.org (no number). Then, following the latency, attribute the gamer to the proper mpserver. However, it is not that easy and has to be thought more thoroughly as there might be consequences on this. But that would be the easiest IMHO. - Mail Original - De: Csaba Halász csaba.hal...@gmail.com À: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Envoyé: Vendredi 29 Janvier 2010 00h06:54 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [Flightgear-devel] new MP server / Netherlands On Thu, Jan 28, 2010 at 11:13 PM, HB-GRAL flightg...@sablonier.ch wrote: Csaba Halász schrieb: By the way, I think something should be done about 02. It is way too overused and seems to have some intermittent relaying problems (even though it is supposed to have IP filtering now). I don't know if the problems are caused by the overload or not, though. What do you think about renaming it to 12? Maybe we should be careful with such changes without contacting pigeon who is also running the mpmap02 server. Of course. He is reading this, I assume :) Also, I have mentioned the relay problems to him on IRC already. Anyway number 11 and 12 are not listed in the map script (goes from 01 to 10 at the moment as I can see). Not sure which script you mean, but 11 is up. -- Csaba/Jester -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] new MP server / Netherlands
Olivier JACQ wrote: The MP conversation is interesting. Why should people choose between one or another MP Server : 1. Because it is written in the doc (Wiki, ...) 2. Because they check their latency from their location (which is the best option). 3. Because they choose it based on its location. I don't really know how this is handed in other games, but the easier would be : One domaine name to enter in the config file (mpserver.flightgear.org (no number). Then, following the latency, attribute the gamer to the proper mpserver. I kinda agree as I've written and have the code for http://biasva.com/bias/ (and am thinking about to GPL this as a virtual airline application for FlightGear, ie livery, pilots and flightplans etc). Vatsim and IVAO contain (they had an argument so are similar forks) have a status.txt file to all the MP servers, and then one can pick one (with 5 minute update) http://usa-s1.vatsim.net/data/status.txt This was an issue as my algorithm in parsing above and an error decided to pick the first one always which led to being succesfully banned permerantly. This lead to a new algorithm that picked a server that did not include the first one (sighs). However in the FG scenario then its 10 frames per second and a slightly different role What I envisage it booting up Fg with --multiplay=auto I think the solution maybe would be to create and index of current MP servers online and their latency. That would allow flightgear as an application to decide and indeed to swap servers mid flight as circumstance applies. To create the Index server, I am already researching/playing using google appengine cloud, to maintain a global the index, however GAE does not accept sockets, and only TCP traffic. This however could be a patch on mpservers and status. ie keepalive psuedo. Using google appengine and its globally distribnuted by nature would accomodate this, and also would be light traffic. just a thought pete -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] new MP server / Netherlands
The easiest way for balancing serverload is, in my opinion, a round robin dns entry. So users simply connect to mpserver.flightgear.org, which resolvs to mpserver01, mpserver02 etc in round robin. A more sophisticated solution is, that the server checks the connecting client IP and sends back a connect to mpserverXX message to the client based on IANA/RIPE/APNIC etc IP-lists. However, this needs greater changes to the server code. Btw: there are two pages showing active servers: http://mpmap01.flightgear.org/mpstatus lists all servers configured as relays of mpserver01 http://pigeond.net/flightgear/mpstatus/ lists all servers hardcoded into the scripts Regards, Oliver -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
