2,732
edits
Howto:Multiplayer: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
Red Leader (talk | contribs) mNo edit summary |
Red Leader (talk | contribs) mNo edit summary |
||
| Line 28: | Line 28: | ||
==== From Network Settings ==== | ==== From Network Settings ==== | ||
[[File:FGRun Advanced dialog - Network.png|thumb|The <tt>Network</tt> tab of the | [[File:FGRun Advanced dialog - Network.png|thumb|The <tt>Network</tt> tab of the Advanced Options dialog in [[FGRun]] (in [[Changelog 3.2|FlightGear 3.2.0]]).]] | ||
You can also change multiplayer settings in the <tt>Network</tt> tab of Advanced Options. | You can also change multiplayer settings in the <tt>Network</tt> tab of FGRun's Advanced Options. | ||
# On the last page, click {{button|Advanced}}. | # On the last page, click {{button|Advanced}}. | ||
| Line 41: | Line 41: | ||
=== Using multiplayer from the command line === | === Using multiplayer from the command line === | ||
First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these; | First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these; | ||
<syntaxhighlight lang="bash"> | |||
--multiplay=out,10,server.ip.address,5000 | |||
--callsign=anything | |||
</syntaxhighlight> | |||
where 5000 is the port number the server is listening on (which is 5000 for the official servers). | where 5000 is the port number the server is listening on (which is 5000 for the official servers). | ||
If you for some reason need to specify which local port and/or interface FlightGear should use add the following argument: | If you for some reason need to specify which local port and/or interface FlightGear should use add the following argument: | ||
<syntaxhighlight lang="bash"> | |||
--multiplay=in,10,your.ip.address,portnumber | |||
</syntaxhighlight> | |||
where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. You can also leave your.ip.address blank. FlightGear will then listen on all network interfaces: | where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. You can also leave your.ip.address blank. FlightGear will then listen on all network interfaces: | ||
<syntaxhighlight lang="bash"> | |||
--multiplay=in,10,,5000 | |||
</syntaxhighlight> | |||
{{tip|For a local setup between two fgfs instances without any [[Fgms|fgms/multiplayer server]] being involved, you merely need to map each I/O port to the corresponding port of the other instance: | {{tip|For a local setup between two fgfs instances without any [[Fgms|fgms/multiplayer server]] being involved, you merely need to map each I/O port to the corresponding port of the other instance: | ||
| Line 83: | Line 86: | ||
* With '''Windows 98''', click start, run, and type "winipcfg" to get information about your IP address. | * With '''Windows 98''', click start, run, and type "winipcfg" to get information about your IP address. | ||
This section | This section ''ought'' to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through. | ||
Now, all (!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [[FlightGear IRC channel]] for help (details on the flightgear website). | Now, all (!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [[FlightGear IRC channel]] for help (details on the flightgear website). | ||
| Line 307: | Line 310: | ||
Port 5000 is unofficially associated both with FlightGear and the UPnP protocol. | Port 5000 is unofficially associated both with FlightGear and the UPnP protocol. | ||
However, it has been observed (discussion of | However, it has been observed (discussion of {{issue|1617}}) that '''the fact that Fibertel Argentina is using port 5000 for network setup purposes shouldn't imply that they are filtering packets: ''"it should really only be when the packet has reached its destination that the port number has any meaning at all"'''''. | ||
Forum thread full link: http://forum.flightgear.org/viewtopic.php?f=27&t=24754&p=226034#p226034). | Forum thread full link: http://forum.flightgear.org/viewtopic.php?f=27&t=24754&p=226034#p226034). | ||
See {{issue|1617}}. | |||
Besides investigating about '''possible workarounds(?)''' (port forwarding through UDP bidirectional tunnelling) which might or might not add too much network latency or CPU load or constitute a misuse of special purposes networks, the user suggested diversification of port numbers (''"offering two possible port numbers could mean offering twice the chances to connect to the Multiplayer network and would constitute a reasonable prevention measure of part of the possible connection problems of FlightGear users over the internet"''). | Besides investigating about '''possible workarounds(?)''' (port forwarding through UDP bidirectional tunnelling) which might or might not add too much network latency or CPU load or constitute a misuse of special purposes networks, the user suggested diversification of port numbers (''"offering two possible port numbers could mean offering twice the chances to connect to the Multiplayer network and would constitute a reasonable prevention measure of part of the possible connection problems of FlightGear users over the internet"''). | ||