Ethereal-dev: Re: [Ethereal-dev] Problem with get_host_ipaddr in addr_resolv.c for win32
Guy Harris wrote:
To deal with the broken inet_aton(), we should perhaps always arrange to
use our own inet_aton() if ADNS is being used and it has a broken
inet_aton(). (We already have our own inet_aton(), which the configure
script uses on systems that lack inet_aton(); the configure script
should also check for a broken inet_aton(), just as it checks for a
broken inet_pton(). On Windows, with an MSVC++ build, we can presumably
just forcibly build with our own inet_aton() if we're building with ADNS
until an ADNS release without the bug is released, at which point we
should require that release.)
For some reason MSVC++ builds of Ethereal appear *always* to use our own
inet_aton(); does Windows not have inet_aton()?
So that's not an issue for MSVC++ builds. We should still perhaps add
the configure script checks in question.
To deal with the "gethostbyname()" timeouts, perhaps we should use ADNS
to resolve names in "get_host_ipaddr()" if ADNS is configured and enabled.
But "gethostbyname()" timeouts should occur for NetBIOS name resolutions
only if either
1) you're using WINS and your WINS server is down
or
2) you're not using WINS.
The main NetBIOS problems are with "gethostbyaddr()", as there's no
NetBIOS Name Server query that supplies an address and asks for the name
- you have to send a NetBIOS "get status" query (or whatever it's
called) to the IP address in question and see what name it reports, and
if that host is down or is unreachable or isn't running any
NetBIOS-over-TCP code, that will fail only after a timeout.
Are NetBIOS timeouts with "gethostbyname()", rather than
"gethostbyaddr()", really common enough that this is a problem (or any
more of a problem than, for example, DNS or NIS or Netinfo or... timeouts)?
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
