Just compiled the 1.0pre2 version (pre1 has missing counter_hash.h file). Apparently the resolver for ipv6 has a problem with resolving local host (do not confuse with localhost) own ipv6 address. I.e. Here the host where iftop is being run has ip6 addres 2001:470:b4a7::102 (amagi.gbit6.net)
Iftop with dns resolution: amagi.intr.gbit6.net <=> cam.intr.gbit6.net yamato.gbit6.net <=> yamato.gbit6.net http://pool-173-79-27-59.washdc.fios.verizon.net same situation without dns resolution: 10.1.0.102 <=> 10.1.0.101 2001:470:b4a7::102 <=> 2001:470:b4a7::11
It's as if it wrongly uses the fqdn resolved for the remote host. Resolving of remote hosts that have ipv6 addr works properly.
A simple mistake I guess?
Regards Vladimir-M. Obelic
What DNS lookup method did it use? (look for USE_ARES and the 4 following definitions to see which was selected in config.h)
Scott
On Sun, Apr 22, 2012 at 9:47 AM, Vladimir-M. Obelic vobelic@gbit6.netwrote:
Just compiled the 1.0pre2 version (pre1 has missing counter_hash.h file). Apparently the resolver for ipv6 has a problem with resolving local host (do not confuse with localhost) own ipv6 address. I.e. Here the host where iftop is being run has ip6 addres 2001:470:b4a7::102 (amagi.gbit6.net)
Iftop with dns resolution: amagi.intr.gbit6.net <=> cam.intr.gbit6.net yamato.gbit6.net <=> yamato.gbit6.net http://pool-173-79-27-59.washdc.fios.verizon.net same situation without dns resolution: 10.1.0.102 <=> 10.1.0.101 2001:470:b4a7::102 <=> 2001:470:b4a7::11
It's as if it wrongly uses the fqdn resolved for the remote host. Resolving of remote hosts that have ipv6 addr works properly.
A simple mistake I guess?
Regards Vladimir-M. Obelic
It uses USE_GETHOSTBYADDR_R
Vladimir
On Mon, Apr 23, 2012 at 20:29, Scott Bertilson ssb@umn.edu wrote:
What DNS lookup method did it use? (look for USE_ARES and the 4 following definitions to see which was selected in config.h)
Scott
On Sun, Apr 22, 2012 at 9:47 AM, Vladimir-M. Obelic vobelic@gbit6.netwrote:
Just compiled the 1.0pre2 version (pre1 has missing counter_hash.h file). Apparently the resolver for ipv6 has a problem with resolving local host (do not confuse with localhost) own ipv6 address. I.e. Here the host where iftop is being run has ip6 addres 2001:470:b4a7::102 (amagi.gbit6.net)
Iftop with dns resolution: amagi.intr.gbit6.net <=> cam.intr.gbit6.net yamato.gbit6.net <=> yamato.gbit6.net http://pool-173-79-27-59.washdc.fios.verizon.net same situation without dns resolution: 10.1.0.102 <=> 10.1.0.101 2001:470:b4a7::102 <=> 2001:470:b4a7::11
It's as if it wrongly uses the fqdn resolved for the remote host. Resolving of remote hosts that have ipv6 addr works properly.
A simple mistake I guess?
Regards Vladimir-M. Obelic
-
Scott Bertilson -
Vladimir-M. Obelic