Re: [Flightgear-devel] socket output problems

[John W. <ca...@mm...>]

Just to be sure....

The machine running the demo software is at 192.168.1.3. What is the 
address of the FG machine?

The startup script for the demo lets you set the socket address where 
you want to receive data from FG and the IP and socket address where you 
want to sent control data back to FG.

On the FG side, you need to set (as a minimum) the  address and socket 
of the machine running the demo

What address/network are you using to handle the other network services? 
If different than the 192.168.1.0 network you will have to use a second 
card and set up your routing tables accordingly.

At scale4x we had one card configured for connecting to the Internet at 
eth0 and a second card at eth1 configured to communicate with the sim.

For the moment, let's assume one card behind a gateway/firewall that 
provides NAT for accessing the Internet and a private LAN at 192.168.1.0.

In flightgear:  --opengc=socket,30,192.168.1.3,6000,udp
                       --native-ctrl=socket,30,<IP address of demo 
machine>,<receiving socket>,udp

In the demo startup script  --network=6000,<FG socket that receives ctrl 
data>,<IP address of FG machine>

Regards
John W




Justin Smithies wrote:

>How Curtis as im trying to run Johns Glass cockpit software demo on the same 
>machine and i cant get FG to send data to it.
>
>Ive set his software to use port 6000 and my i.p. 192.168.1.3 it runs up and 
>appears to be awaiting data.
>
>Then i run FG with
>
>fgfs --opengc=socket,out,30,192.168.1.3,6000,udp
>
>And all i get is Error writing data.
>
>But if i issue FG with a dummy i.p like 192.168.1.6 no errors, so that just 
>confuses me as you said the error was because it got no reply from the 
>running service.
>There is nothing on 192.168.1.6 .....
>
>Anymore ideas ?
>
>Justin Smithies
>
>
>On Wednesday 15 February 2006 21:44, Curtis L. Olson wrote:
>  
>
>>Justin Smithies wrote:
>>    
>>
>>>Ah sorted im going to have to run the glass cockpit on an other pc i cant
>>>use my own i.p.
>>>      
>>>
>>There's no reason you can't have FlightGear send udp packets to another
>>application on the same machine.  You may or may not want to do that,
>>but it certainly is possible.
>>
>>Curt.
>>    
>>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
>_______________________________________________
>Flightgear-devel mailing list
>Fli...@li...
>https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
>  
>