[Flightgear-devel] Debugging MultiPlayer

[Martin S. <Mar...@mg...>]

Hi together,
I'd like to get the MultiPlayer setup on my wife's PeeCee up and
running before I recommend use of this feature in The Manual. After
spending a couple of hours with researching the interna of my NAT
gateway last night, I decided to make a simpler setup for testing
purpose and took two computers on the local network today. Actually it
doesn't work as expected, I'm a bit lost and desperately seeking for
suggestions on how to debug.

There are two computers, equipped with FlightGear binary and base
package from the most recent I could get from CVS today:

192.168.48.4, sirius.mgras.de, IRIX N32 binary
192.168.48.5, jive.mgras.de, Linux AMD x86-64 binary


This is how I start FlightGear on 'sirius' (which takes a bit longer to
load  ;-)

fgfs --airport=EDWJ --runway=08 \
--multiplay=out,10,jive.mgras.de,5001 \
--multiplay=in,10,192.168.48.4,5002 --callsign=D-ECLL


....  and afterwards on 'jive':

fgfs --airport=EDWJ --runway=26 \
--multiplay=out,10,sirius.mgras.de,5002 \
--multiplay=in,10,192.168.48.5,5001 --callsign=D-EEQA


Now I would expect at least one, better each of the two pilots to see
the other aircraft idling at the opposite end of the runway - but
nbody's there.

The output of 'tcpdump' on 'jive' looks quite reasonable:

12:02:37.083910 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:37.177510 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:37.282107 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:37.295894 IP sirius.mgras.de.rfe > jive.mgras.de.5001: UDP, length: 384
12:02:37.375389 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:37.483616 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:37.577118 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:37.681702 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:37.684980 IP sirius.mgras.de.rfe > jive.mgras.de.5001: UDP, length: 384
12:02:37.775424 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:37.883775 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:37.977856 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:38.077058 IP sirius.mgras.de.rfe > jive.mgras.de.5001: UDP, length: 384
12:02:38.077807 arp who-has sirius.mgras.de tell jive.mgras.de
12:02:38.079701 arp reply sirius.mgras.de is-at 00:20:48:08:cb:7c
12:02:38.083308 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:38.177063 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:38.283802 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:38.377333 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:38.467070 IP sirius.mgras.de.rfe > jive.mgras.de.5001: UDP, length: 384
12:02:38.483136 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:38.576977 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:38.683704 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:38.776826 IP jive.mgras.de.5001 > sirius.mgras.de.rfe: UDP, length: 384
12:02:38.857072 IP sirius.mgras.de.rfe > jive.mgras.de.5001: UDP, length: 384


Any hint where I should start investigating ?

Thanks,
	Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------