Re: Best practices for interpreting network reachability flags?
Re: Best practices for interpreting network reachability flags?
- Subject: Re: Best practices for interpreting network reachability flags?
- From: Rich Siegel <email@hidden>
- Date: Sun, 9 Sep 2007 19:17:38 -0400
On 9/9/07 at 7:05 PM, email@hidden (Allan Nathanson) wrote:
What you are likely running into is a system which HAS a modem service
enabled. In this case, if the system is not currently connected to an
ethernet/wireless network the modem "can" still provide a path off the
system (but you'd have to "connect" first). This is indicated by the
kSCNetworkFlagsConnectionRequired flag.
The test most applications will want to make is the following :
if ((flags & kSCNetworkFlagsReachable)
&& !(flags & kSCNetworkFlagsConnectionRequired)) {
// target is reachable
}
Great, thanks very much for the info. If I understand your
example correctly, though, testing kSCNetworkFlagsReachable by
itself is all I need to do. Is that right? And if so, how do I
reconcile that with the beta reports that their networking is
running correctly and yet kSCNetworkFlagsReachable is off? (I'm
already testing that flag, and _only_ that flag.)
Thanks again,
R.
--
Rich Siegel Bare Bones Software, Inc.
<email@hidden> <http://www.barebones.com/>
Someday I'll look back on all this and laugh... until they
sedate me.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden