> > John, > > I seem to recall having this working once. There is an extra flag you > have to enable on the socket to make it actually broadcast.
Yes, that jogs the ole' brain cells. (See Unix Network Programming, H.R.Stevens, page 318) >I don't recall if this had to be enabled at the > plib level or the simgear level? I seem to recall it was working for a > while and then didn't work, but I haven't looked into it for a year or > two. plib's net libs are a bit strange. They seem to tickle a dns > lookup even for local ip address connections. I haven't been able to > figure that one out ... it's ok if you don't have a dns server > configured, but can be an annoyance if you are configured to auto-dial > on any net activity. For some reason it seemed like the workingness of > broadcast was tied to dns availability or something ... but I'm grasping > at fading memories here so I could be way off. > > Curt. > Thanks, that helps -- guess I'll dig around in the plib and Simgear code Part of the question also relates to any penalty imposed on the FG frame rate by adding multiple socket options for each IP address and unique port. Any SWAG on the percentage for each additional socket? linear, geometric, exponential? Or is it in the noise? Given that the current data packet is about 700 bytes, the LAN is a long way from any performance limits, at least for datagrams. Regards John W. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
