> > > Running FG under cygwin allows the socket output to be set to the > broadcast address, 192.xxx.xxx.255. But under linux Fg returns an error > > > that make_client_socket failed for the broadcast address. Looks like > cygwin is faking it. > > > > Not necessarily. Did you declare that to be the broadcast address when > > you installed the network onto the adapter ? UDP broadcast works fine. > > You're dealing with a network-aware operating system and if you ask > > it to do something impossible, it is bright enough to not try it. > > > Not so much faking it as using software to simulate broadcast, My > understanding is that unix/linux does not provide a comparable service in > the kernel, so the socket code needs the broadcast option set via the > setsockopt(..) call. When searching thru the plib code I did not see > any reference to the set option call (it's not mandatory).
> Are you saying that UDP broadcast works in FlightGear or as a general > network capability? Both. I routinely use it at work, but I always set the options correctly so I wouldn't have noticed the effect that you are describing with the flag. I recall using UDP broadcast with the FGFS Network layer in the past, but I don't recall whether I had to improve the source code to make it work. In any case, UDP broadcast works fine using netcat if you specify the broadcast option ... and also works fine for UDP unicast with the option set as well ... so I suggest you try just turning it always on in PLIB. Without having time to check the docs this morning, the references I've seen to the broadcast flag are simply giving the socket permission to do broadcast, so programs don't accidentally flood the local network. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
