Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] ADNS alternative

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Jaap Keuter <jaap.keuter@xxxxxxxxx>
Date: Fri, 02 May 2008 14:08:50 +0200

Hi,

Looking at the suggestions I see this:
Poslib seems to have been developed until 2005, similar problem as ADNS. It's a C++ lib as well, causing a binding problem. UDNS looks interesting as well. As it's conceptual model is further from ADNS than c-ares is it might take more work to get it interfaced. Another thing not apparent is the cross platform support. There is mention of a Win32 port, but that is stated to be out of date.

Thanx,
Jaap



Graham Bloice wrote:
Gerald Combs wrote:
Jaap Keuter wrote:
Hi list,

I've stumbled upon c-ares (http://daniel.haxx.se/projects/c-ares/) as a possible replacement for ADNS, which we currently have as async DNS resolver library.
Pro's: Still being developed, IPv6 support, multi-platform, MIT license.
Con's: May suffer from same memory allocation issues on Win32 as does ADNS.

Does anyone have further insights into the use of this library?

It looks interesting. The fact that it's documented and actively developed is
encouraging.
_______________________________________________
It also has some Freexxx() functions that seem to handle freeing allocations that the lib makes.

From the web site, they also have a link to other similar libs, Poslib (http://posadis.sourceforge.net/) and UDNS (http://www.corpit.ru/mjt/udns.html) look interesting.

--
Regards,

Graham Bloice



  • Follow-Ups:
    • Re: [Wireshark-dev] ADNS alternative
      • From: Sébastien Tandel
  • Prev by Date: Re: [Wireshark-dev] Question on text2pcap behaviour
  • Next by Date: [Wireshark-dev] Interesting name collision
  • Previous by thread: Re: [Wireshark-dev] [Winpcap-users] RE: ring buffer
  • Next by thread: Re: [Wireshark-dev] ADNS alternative
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation