Good call, xlsior! It makes far more sense to try the most common connections first and count down from 255 to the computer's ip. Although counting up from the computer's IP should mean that the probing remains within the designated netblock, in case probing outside of it sets any ultra-paranoid network admin alarm bells ringing, though this is probably a ridiculous precaution. If it doesn't determine the IP it will likely venture outside the block anyway, especially with a 65535 check. And if one's network was really that paranoid, network games would have a pretty hard time of it. The speed increase and likely reduction in traffic is probably worth the trade-off. I can always put in a feature in the 'advanced' options for the server allowing the user to specify the broadcast IP if so desired. Weird, I tend to do my thinking out loud/on the fly as well... sometimes it makes for some amusing grammar. As well as obscenely excessive use of "guess", "probably" and "suppose".
And yeah, I've run the thing a few times without the UDPtimeouts, and it seems to work fine in every case, and several, several times faster than even the lowest timeout of 1ms. so it's probably better off without it. I guess I'd need an ultra ultra crap LAN to try it on to be sure, and mine's only quite crap.
And yeah, I've run the thing a few times without the UDPtimeouts, and it seems to work fine in every case, and several, several times faster than even the lowest timeout of 1ms. so it's probably better off without it. I guess I'd need an ultra ultra crap LAN to try it on to be sure, and mine's only quite crap.