Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Best practices for interpreting network reachability flags?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Best practices for interpreting network reachability flags?

Subject: Re: Best practices for interpreting network reachability flags?
From: Rich Siegel <email@hidden>
Date: Mon, 10 Sep 2007 09:49:07 -0400

On 9/10/07 at 8:17 AM, email@hidden (Allan Nathanson) wrote:

If you only check kSCNetworkFlagsReachable than your application may
attempt to use the network only to be blocked because the modem
service needs to be connected.

Yep, understood. Unfortunately, though: I'm having the opposite problem: apparently I'm getting back (! (flags & kSCNetworkFlagsReachable)) when the network is in fact connected and running. Can you think of anything offhand that would explain that?

Thanks,

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


Follow-Ups:

Re: Best practices for interpreting network reachability flags?
From: Allan Nathanson <email@hidden>


References:  
  >Re: Best practices for interpreting network reachability flags? (From: Allan Nathanson <email@hidden>)




Prev by Date:
Re: Best practices for interpreting network reachability flags?

Next by Date:
Re: Best practices for interpreting network reachability flags?

Previous by thread:
Re: Best practices for interpreting network reachability flags?

Next by thread:
Re: Best practices for interpreting network reachability flags?

Index(es):

Date
Thread