![]() Now, all that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. Windows 98, click start, run, and type "winipcfg" to get information about your IP address.Windows XP or later: Start Command Prompt and ipconfig into the terminal.For example, this should read something like inet addr:192.168.0.150. Finally, look in the text below the interface name for inet addr:ip.address. In the text that is returned, you should to look for an interface name such as eth0 or wlan0. Linux: Log in as root and run ifconfig in the terminal.If your connection is via an Ethernet connector or by a wireless link. Note Your ISP might not give you the same IP address each time. If your Internet connection is via an ADSL modem that plugs directly into your computer, you should be able to find your IP address by visiting. If you have problems though, it won't hurt to follow through.įirst of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. This section ought to be unnecessary now with recent versions of the FG server. Note This section may contain out of date or inaccurate information. Now, going more slowly for those who are completely lost. Do not pick a callsign that is already used, as that will create problems! Thus, you need to modify the client-side port settings for each additional instance that you are running on the same machine, and map the output port of one instance to the input port of the other instance (and vice versa).Ĭheck this page to see whether your callsign is already in use or not. Because open ports (=mailboxes) cannot be shared. Different processes (even when possibly identical programs) will need to use different port numbers when running. This mailbox is used by the communicating processes to send out and receive "messages". All you need to do is map each I/O port of one instance to the corresponding port(s) of the other instance:Ī socket connection requires not only an IP address, but also a port number for each side of the link - imagine a port number like a "mailbox" sitting at the address. It is possible to set up a local multiplayer network between two FlightGear instances without using a multiplayer server. Advanced usage of multiplayer Local setup for testing port Port that data is either being sent or received through. If direction is set to in, FlightGear will listen to only this IP address. If left blank, FlightGear will listen to all network interfaces. ip.address IP address of network interface being used by FlightGear. out tells FlightGear to send data out through the port. in tells FlightGear to listen to packets of data coming in through the specified port. Do not pick a callsign that is already used, as that will create problems! Please don't leave your callsign as "CALLSIG".ĭirection Either in or out. Check this page to see whether your callsign is already in use or not. Generally speaking, callsigns are of the form X-XXXXX. If your callsign is too long, it will be cut off in the various displays where it is shown. Obviously, -callsign can be anything you wish but it must be limited to 7 (seven) characters in length counting any dashes.
0 Comments
Leave a Reply. |