I read the new version announcement.
It says speak up now, otherwise we will remove the non threaded name resolver.
I don't hope that this would mean that EtherApe would not resolve ip adresses in the future,
that would render it pretty useless..
* speaking up *
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, EtherApe will always be able to resolve names, but there are two resolvers.
The non-threaded one, pending for removal, talks directly to a DNS server via udp. It works almost everywhere and allows multiple requests even with a single thread. The list of benefits stops here, however and begins a long series of shortcomings. Connecting directly to a DNS server means also not supporting the hosts file, or other resolving methods.
AFAIK everyone uses the threaded resolver, built on the standard OS facilities (gethostbyaddr and friends). The only downside of this approach is having to use multiple threads to resolve names in parallel, but on almost every other aspect is far better than the old one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On my LAN names are not resolved in fact I generally just see IP addresses.
If I'm a VPN all I see is the tunnel IP too and nothing else.
One thing I'd love to see in Etherape is a way to configure and tune name resoltion and ideally add to an etherape specific IP to name map. I'd like to say, this IP I see regulalry, please dispaly htis name instead, as I know it as that.
This would make reading teh bubble charts so much easier for me.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I read the new version announcement.
It says speak up now, otherwise we will remove the non threaded name resolver.
I don't hope that this would mean that EtherApe would not resolve ip adresses in the future,
that would render it pretty useless..
* speaking up *
No, EtherApe will always be able to resolve names, but there are two resolvers.
The non-threaded one, pending for removal, talks directly to a DNS server via udp. It works almost everywhere and allows multiple requests even with a single thread. The list of benefits stops here, however and begins a long series of shortcomings. Connecting directly to a DNS server means also not supporting the hosts file, or other resolving methods.
AFAIK everyone uses the threaded resolver, built on the standard OS facilities (gethostbyaddr and friends). The only downside of this approach is having to use multiple threads to resolve names in parallel, but on almost every other aspect is far better than the old one.
On my LAN names are not resolved in fact I generally just see IP addresses.
If I'm a VPN all I see is the tunnel IP too and nothing else.
One thing I'd love to see in Etherape is a way to configure and tune name resoltion and ideally add to an etherape specific IP to name map. I'd like to say, this IP I see regulalry, please dispaly htis name instead, as I know it as that.
This would make reading teh bubble charts so much easier for me.
I will note it as a feature request. In the meantime, you can add ip addresses to the /etc/hosts file and etherape will resolve them