I also experience some troubles. The connection seem unstable overal.
I got it to work with the deault settings + some local fgcom standalone instance to listen to myself and that worked. until it didn't.
I looks like the connection is not that stable and once it got hanged up, its hard to reestblish.
To test that i did a ping test to the fgcom server and it showed sporadic packet loss.
I own a dedicated server and tried it there too - with a better result (packet loss was way more seldom)
So i tried the following:
- establish a ssh TCP session with local port forwarding, and attaching a UDP listener and sender to fgcom server to it:
- Code: Select all
local: ~$ ssh myServer -L 6000:localhost:6001
myServer:~$ mkfifo /tmp/fgcom_fifo; nc -v -l -p 6001 < /tmp/fgcom_fifo | nc -u fgcom.flightgear.org 4569 > /tmp/fgcom_fifo
- locally i also did this fifo/udp/tunnel thing:
- Code: Select all
local:~$mkfifo /tmp/fgcom_fifo; nc -l -u -p 4569 < /tmp/fgcom_fifo | nc localhost 6000 > /tmp/fgcom_fifo
This looked stable so far. Sometimes the nc connection breaks and then i need to restart that piece.
Somehow, but still, the connections sometimes break and could not be reestablished. I don't know why.
The main problem with this is that: you cannot be sure the connection is there when you try to communicate and debugging all that while on approach is a little hard.
The system should be reliable, so the underlying infrastructure is out of the equation, so only mistuned radios etc remain....
I guess this is a result of using UDP for communication.
Is the central fgcom server overloaded from traffic or something?