Re: Network Device Informations

[Federico Montesino Pouzols]

        Returning -1 seems a good option. If there were another way to
fix this problem, we could always add a patch for that later.

        The new code is alreay in the 1.1 CVS branch.

        I am sure CC++ works well under Win98, and it should on Win95.

On Thu, Nov 14, 2002 at 07:38:28AM -0500, David Sugar wrote:
> 
> I think the -1 MTU returned from something (like win95) which cannot 
> return a mtu is find...
> 
> On Thu, 14 Nov 2002, Prochnow, Christian wrote:
> 
> > Hi,
> > 
> > The ioctl() calls made in enumNetworkDevices() should work under Linux, 
> > Solaris and FreeBSD cause this is a common UNIX ioctl. The structures used 
> > are also UNIX-common. 
> > ioctl() are very different between unices if we want to query IPv6 devices 
> > also - but Common C++ doesnt support IPv6 at all, right ?
> > So adding IPv6 support to Common C++ and to the NetworkDeviceInfo class 
> > should 
> > be a TODO item for future releases.
> > 
> > So what dou you think of the MTU issue ?
> > Does anyone know if Common C++ works under Win95 ?
> > And when - do you think we should break compatibility with Win95 cause of 
> > this 
> > MIB functions ? Or should the Win95 implementation simply return "-1" as 
> > MTU. 
> > I think querying the MTU is a common-task for UDP-message oriented 
> > protocols. 
> > 
> > I'm using Common C++ to develop Finance Realtime Applications for my 
> > employer 
> > (a German company) which mainly runs Linux on their Servers and Windows on 
> > their Workstations.
> > Cause i'm actively using Common C++ now, and also did a portable 
> > application 
> > framework (P::Classes) in the past i would like to continue contributing to 
> > the Common C++ Project.
> > 
> > Regards,
> > Christian Prochnow
> >