This sounds like a great idea for generic checking for a network
connection.
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.
I also read the documentation about FLAG_ICC_FORCE_CONNECTION as saying
that if the flag was set then the api tried to force the connection, if
not then it just used the connection as is, but did a ping either way.
Because forcing a connection seemed to be a windows dialup sort of thing
I have just ignored it so far.
-aric
Andreas Mohr wrote:
>
> On Wed, Jul 26, 2000 at 04:31:38PM +0200, Bertho Stultiens wrote:
> > Try:
> > $ netstat -r -n
> >
> > This should give the routing tables as well. Netstat can be used on
> > solaris too afaik.
> Only to complete the picture:
>
> rshx11:~> uname -a
> HP-UX rshx11 B.10.20 A 9000/715 2013100679 two-user license
> rshx11:~> netstat -r -n
> Routing tables
> Destination Gateway Flags Refs Use Interface Pmtu PmtuTime
> 127.0.0.1 127.0.0.1 UH 0 218 lo0 4608
> 134.108.51.11 127.0.0.1 UH 0 34 lo0 4608
> default 134.108.48.254 UG 1 193124 lan0 1500
> 134.108.48.0 134.108.51.11 U 7 13558 lan0 1500
>
> Andreas Mohr
