Aric Stewart <[EMAIL PROTECTED]> writes: > However the API seems to lend itself to not only checking a generic > internet connection but also checking conductivity to a specific host. > For this a ping sort of approach seems appropriate. I will work at > taking out the www.ibm.net for a null parameter and instead using > netstat -r -n. Having to parse the output of netstat will be more trouble than it's worth IMO. I think we should not try to be too clever here. I'd suggest simply checking for a network interface that is up and not loopback, using the same ioctls than ifconfig does. -- Alexandre Julliard [EMAIL PROTECTED]
- RE: InternetCheckConnection Stephane Lussier
- Re: InternetCheckConnection David Elliott
- Re: InternetCheckConnection Gerald Pfeifer
- Re: InternetCheckConnection David Elliott
- Re: InternetCheckConnection Gerald Pfeifer
- Re: InternetCheckConnection Marcus Meissner
- Re: InternetCheckConnection Bertho Stultiens
- Re: InternetCheckConnection Gerald Pfeifer
- Re: InternetCheckConnection Andreas Mohr
- Re: InternetCheckConnection Aric Stewart
- Re: InternetCheckConnection Alexandre Julliard
- Re: InternetCheckConnection David Elliott
- RE: InternetCheckConnection Patrik Stridvall
- Re: InternetCheckConnection David Elliott
- RE: InternetCheckConnection Patrik Stridvall
- RE: InternetCheckConnection Patrik Stridvall
- Re: InternetCheckConnection Francois Gouget