One thing to be concerned about is that pinging your broadcast address may not
be as meaningful as you'd like. Pinging 184.108.40.206 will probably yield the same
results, as all multicast aware computers should respond to a ping at that
I don't use multicast very much, in fact I try to avoid it when possible.
Broadcast packets tend to live too long on a network (as long as standard
unicast messages, which almost got me into trouble once...). Since I don't use
broadcast, I'm not sure why you are getting an error binding to the broadcast
On Thursday, December 09, 2004, at 03:38PM, John Wojnaroski <[EMAIL PROTECTED]>
>----- Original Message -----
>From: "Jonathan Polley" <[EMAIL PROTECTED]>
>To: "FlightGear developers discussions" <[EMAIL PROTECTED]>
>Sent: Thursday, December 09, 2004 1:00 PM
>Subject: Re: [Flightgear-devel] Broadcast Address
>> You will want to use multicast. The multicast address range is 220.127.116.11
>thru 18.104.22.168. 22.214.171.124 is reserved, so don't use it. Also,
>multicast has a default time to live (TTL) of 1 hop, so it will be limited
>to devices on the same subnet. I don't know if FlightGear handles receiving
>> Jonathan Polley
>Ooops, should have been a bit more expicit. The machines are running on a
>private LAN that supports my 747 sim. All four machines require FG data.
>While two machines require a full set of data (plus what I've added from
>JSBSim) the remaining two require a smaller subset and I'll probably add a
>fifth to run the MCDUs which requires even a smaller set. Plus there is
>additional data using the opengc protocol which is also redundant.
>Was not conptemplating the idea of going onto the Internet...
>Running Debian with linux-2.4.26 on all machines. The network configuration
>appears okay, in that a "ping 192.168.2.255" from any and all machines
>generates a response from all machines
>Flightgear-devel mailing list
Of COURSE they can do that. They're engineers!
Flightgear-devel mailing list