Re: [Flightgear-devel] New FlightGear Multiplayer Server
Hi all, http://mpmap02.flightgear.org/ server list shows my server as Hong Kong. The very first mpserver02 was located in Hong Kong. I hope the admin of this page (pigeon: wake up! :) reads this. /me wakes up. Fixed! Let me know if it's alright. Sorry for not being very active these days. Meanwhile, I'm stuck at a rather weird bug while porting the mpmap to the latest google api v3, I think I'm getting there though. Glad to hear there is the new openstreetmap version in the works. Guess I can retire soon ;) Regards, Pigeon. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New FlightGear Multiplayer Server
Hi Lloyd, i wrote a private mail to you on monday but apprently it's lost in space ;) So I repeat, your fgms.conf should look like: # basic setting server.name = mpserver02 server.port = 5000 # you can telnet to this port with this username/password # and see statistics (nice cisco like CLI) server.admin_port = 6002 server.admin_user = fred server.admin_pass = fred server.admin_enable = fred # mpserver01 does this server.tracked = false # mpserver01 is hub server.is_hub = false # don't set this too high server.out_of_reach = 100 # your only relay should be mpserver01 relay.host = mpserver01.flightgear.org relay.port = 5000 # you don't need a crossfeed, it's only interresting for fgms-developers # crossfeed.host = foo.example.com # crossfeed.port = 5002 # you can add static entries of IPs which get blocked, # but it's generally not needed and you can add them via # the admin CLI # blacklist = 123.123.123.123 And now the rest; Am 09.07.2013 23:13, schrieb Lloyd A. Stevens: Thanks for adding my server. I was only seeing local clients until I made the following change to my config file (I am guessing I was supposed to do this): relay.host = mpserver01.flightgear.org fgms will ignore traffic comming from unknown relays and since the multiplayer network is a star topology you should list only mpserver01 as your only relay. Currently mpserver01 is the only HUB, Although multiple HUBs should work I have not tested a multi HUB environment yet. And for those interrested: Current traffic load on mpserver01 is around 10 MBit/s Should other fgms be told that I exist? How would I notify them? You (and all others) can reach all server admins with fgserver at postrobot dot de It's a pseudo mailing list and I try to keep the list of admins up to date as good as I can. I also added the server to this list http://wiki.flightgear.org/Howto:Multiplayer#Servers Other places that need to updated for the new server: Link on above listed page shows Geographic locations of the servers are also available at Google Mapshttps://maps.google.nl/maps/ms?msid=213869436283721436186.000481c029e65 3a30807cmsa=0ll=42.293564,38.671875spn=69.324015,173.144531 I also updated http://mpmap01.flightgear.org/mpstatus/ http://mpmap02.flightgear.org/ server list shows my server as Hong Kong. The very first mpserver02 was located in Hong Kong. I hope the admin of this page (pigeon: wake up! :) reads this. http://mpserver15.flightgear.org/mpserverstatus/ http://mpserver16.flightgear.org/ list shows my server as Kansas (but with correct IP address). http://flightgear.mxchange.org/mpstatus/ list shows my server as Kansas. Who should I contact to update these? Are there any other places the server needs to be updated? The second incarnation of mpserver02 was located in Kansas. So this information is also outdated. Unfortunatly all those links are administerd by different people. Now that the server is active and appears to be working correctly should it be tracked? Should it act as a HUB? From config file (my current settings): ## # Tracking server # set server.tracked = true to use it # only set this to true if the tracking server # admin allows it! server.tracked = false server.tracking_server = 62.112.194.20 server.tracking_port = 8000 ## # if set to true, fgms will act as a HUB server # a HUB server will resend packets received from # relays to all other relays # *only* set to true if you know what you are # doning server.is_hub = false As long as you are not absolutly sure what you are doing you should: - disable tracking - disable HUB setting OLIVER, Thank you for updating the sources and pushing them to gitorious. Even if I had access to do this I would have been unwary of doing it because I would hate to break a compile on linux since I have no way of testing it. I tested the new code on FreeBSD and decimal points are still missing in lines 107 113 I will check this tommorow. Unfortunatly I have no BSD to test. Perhaps one day I have time to set up some virtual machines with different operating systems ;) Best wishes, Oliver -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New FlightGear Multiplayer Server
Thanks for adding my server. I was only seeing local clients until I made the following change to my config file (I am guessing I was supposed to do this): relay.host = mpserver01.flightgear.org Should other fgms be told that I exist? How would I notify them? I also added the server to this list http://wiki.flightgear.org/Howto:Multiplayer#Servers Other places that need to updated for the new server: Link on above listed page shows Geographic locations of the servers are also available at Google Mapshttps://maps.google.nl/maps/ms?msid=213869436283721436186.000481c029e65 3a30807cmsa=0ll=42.293564,38.671875spn=69.324015,173.144531 http://mpmap02.flightgear.org/ server list shows my server as Hong Kong. http://mpserver15.flightgear.org/mpserverstatus/ http://mpserver16.flightgear.org/ list shows my server as Kansas (but with correct IP address). http://flightgear.mxchange.org/mpstatus/ list shows my server as Kansas. Who should I contact to update these? Are there any other places the server needs to be updated? Now that the server is active and appears to be working correctly should it be tracked? Should it act as a HUB? From config file (my current settings): ## # Tracking server # set server.tracked = true to use it # only set this to true if the tracking server # admin allows it! server.tracked = false server.tracking_server = 62.112.194.20 server.tracking_port = 8000 ## # if set to true, fgms will act as a HUB server # a HUB server will resend packets received from # relays to all other relays # *only* set to true if you know what you are # doning server.is_hub = false OLIVER, Thank you for updating the sources and pushing them to gitorious. Even if I had access to do this I would have been unwary of doing it because I would hate to break a compile on linux since I have no way of testing it. I tested the new code on FreeBSD and decimal points are still missing in lines 107 113 -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New FlightGear Multiplayer Server
Hi Lloyd, I have updated mpserver01 and http://mpmap01.flightgear.org/mpstatus/ Thank you for providing me with feedback for BSD. I've updated the sources and pushed them to gitorious so the source should compile out of the boy now. Regards, Oliver Am 06.07.2013 08:33, schrieb Lloyd A. Stevens: I had a bit of trouble getting fgms to build on FreeBSD 9.0. The source I used was from git://gitorious.org/fgms/fgms-0-x.git ERRORS for: fgms-0-x/src/libcli/libcli.cxx /usr/include/malloc.h:3:2: error: #error malloc.h has been replaced by stdlib.h Changes made to fgms-0-x/src/libcli/libcli.cxx #if !defined(__FreeBSD__) # include malloc.h #endif ERRORS for: fgms-0-x/src/server/fg_util.cxx /usr/ports/local/fgms-0-x/src/server/fg_util.cxx:107: error: integer constant is too large for 'long' type /usr/ports/local/fgms-0-x/src/server/fg_util.cxx:109: error: integer constant is too large for 'long' type /usr/ports/local/fgms-0-x/src/server/fg_util.cxx:113: error: integer constant is too large for 'long' type /usr/ports/local/fgms-0-x/src/server/fg_util.cxx:115: error: integer constant is too large for 'long' type Changes made to fgms-0-x/src/server/fg_util.cxx (added decimal points for the listed lines): if (bytes 1125899906842624.) ret_val = (bytes / 1125899906842624.); else if (bytes 1099511627776.) ret_val = (bytes / 1099511627776.); *The server is now running.* The server is located in Los Angeles, California, USA on a multi-homed 100 Mb sustained connection. This is my backup development server and is rarely used. http://ns3.galacticnet.com/stats/ Uptime is greater than 99% (up for 461 days). Intel(R) Pentium(R) 4 CPU 2.66GHz Logfile: 05.07.2013 18:16:38 # This is newmpserver 05.07.2013 18:16:38 # FlightGear Multiplayer Server v0.11.0 started 05.07.2013 18:16:38 # using protocol version v1.1 (LazyRelay enabled) 05.07.2013 18:16:38 # listening to port 5000 05.07.2013 18:16:38 # telnet port 5001 05.07.2013 18:16:38 # admin port 5002 05.07.2013 18:16:38 # using logfile /var/log/fgms.log 05.07.2013 18:16:38 # listening on 64. 05.07.2013 18:16:38 # tracking is disabled. 05.07.2013 18:16:38 # I have 1 relays 05.07.2013 18:16:38 # relay mpserver14.flightgear.org:5000 05.07.2013 18:16:38 # I have 0 crossfeeds 05.07.2013 18:16:38 # I have 2 blacklisted IPs 05.07.2013 18:16:38 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat] 05.07.2013 18:16:38 # My PID is 34144 05.07.2013 18:16:38 Main server started! 05.07.2013 18:53:15 New LOCAL Client: N1035G 108.228.5.67:61421 (Aircraft/danube/Models/danube-osg.xml) current clients: 1 max: 1 The IP is 64.69.45.88. If you want to add this server to http://mpmap01.flightgear.org/mpstatus/ please provide me with correct values for my fgms.conf: server.name = newmpserver server.tracked = false server.tracking_server = 62.112.194.20 server.tracking_port = 8000 server.is_hub = false server.out_of_reach = 1 #relay.host = mpserver01.flightgear.org #relay.port = 5000 relay.host = mpserver14.flightgear.org relay.port = 5000 # crossfeed.host = foo.example.com # crossfeed.port = 5002 blacklist = 123.123.123.123 ~Lloyd Stevens lists.sourceforge.net@boxisp. net (was this the correct place to post this?) (I still can’t get fgms-1-x to compile) -- This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
