[olsr-dev] Windows interface naming
Tue Oct 3 14:16:43 CEST 2006
Yes, I can adapt it in order to remove the dependency on
Windows XP's version of iphlpapi.dll. I will do it as soon
Just a question.
My code searches for the adapter friendly name if the interface
name, passed by configuration file, is different from IFxx/ifxx;
when interface name is IFxx/ifxx the behaviour is just based
on the adapter index (xx) and not on the adapter friendly name.
Of course some ambiguities could occur if in the system there
are some adapters with friendly name like IFxx (e.g.
IFabc, IF01, if_eth0, etc.).
Can we suppose there are no adapters with friendly name
---------- Initial Header -----------
>From : (spam-protected)
To : "OLSR development" (spam-protected)
Date : Mon, 02 Oct 2006 22:02:48 +0200
Subject : Re: [olsr-dev] Windows interface naming
> Hey Sektor,
> Thanks for your patch and sorry for the delay in getting back to you. I
> like your patch and would very much like to get it into olsrd-current!
> However, in its current version, it unfortunately breaks olsrd
> compatibility with anything below Windows XP. GetAdaptersAddresses() has
> only been introduced in Windows XP and does not exist on earlier Windows
> Could you adapt your patch such that it does not create a dependency on
> Windows XP's version of iphlpapi.dll? An idea that comes to my mind is
> to use GetProcAddress("GetAdaptersAddresses") on iphlpapi.dll and, if
> non-null is returned, supply the functionality, otherwise don't. Then
> your functionality will be available on XP and later and versions below
> XP will still work without your functionality.
> olsr-dev mailing list
Salva ora il tuo preventivo Direct Line e assicurati lo sconto extra 5+5% sulla polizza auto entro il 31 Ottobre!
More information about the Olsr-dev