NDT-DEV email list created

Status: New
Owner: ----
Labels: Type-Defect Severity-Medium OpSys-All Usability

New issue 81 by : pcap filter fails for IPs  
with reverse but without forward lookup
http://code.google.com/p/ndt/issues/detail?id=81

If a client connects from an IP that has a valid DNS reverse lookup but an  
invalid forward lookup, the pcap filter will fail and the NDT client test  
will fail.

For example:

# host 209.66.96.66
66.96.66.209.in-addr.arpa domain name pointer  
209.66.96.66.available.above.net.
# host 209.66.96.66.available.above.net
Host 209.66.96.66.available.above.net not found: 3(NXDOMAIN)

src/web100-pcap.c creates a pcap filter using the reverse-resolved DNS  
name, i.e.:

   "host 209.66.96.66.available.above.net and port 44656"

But fails to resolve the hostname, and the test fails.

I do not believe that client DNS should cause an NDT test failure.

A fix could be to use the IP (rather than DNS name) for 'host' in the pcap  
filter.

The only risk I can imagine is if there might be problems with IPv4/IPv6.   
Does anyone know of a reason that the pcap filter should NOT use the client  
IP directly?

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings