Subject: NDT-DEV email list created
[ndt-dev] Issue 165 in ndt: .meta file: Incorrect values for client IP and server IP
- Subject: [ndt-dev] Issue 165 in ndt: .meta file: Incorrect values for client IP and server IP
- Date: Thu, 11 Dec 2014 18:54:01 +0000
Labels: Type-Defect Severity-Medium
New issue 165 by : .meta file: Incorrect values for client IP and server IP
Looking at the NDT raw data in M-Lab BigStore, we're seeing incorrect values in the "server IP address" and "client IP address" fields of the .meta file. It seems that NDT produces two different types of meta files depending on whether it can determine the client hostname.
When a client hostname is available, the relevant fields appear as follows:
server IP address: 126.96.36.199
server hostname: mlab2.yul01.measurement-lab.org
server kernel version: 2.6.32-131.vs230.web10027.xidmas
client IP address: modemcable252.207-179-173.mc.videotron.ca << invalid IP address
client hostname: modemcable252.207-179-173.mc.videotron.ca
When a client hostname is not available, the relevant fields appear as follows:
server IP address: << server IP address missing
server hostname: mlab1.lga01.measurement-lab.org
server kernel version: 2.6.32-131.vs230.web10027.xidmask.2.mlab
client IP address: 188.8.131.52
client hostname: No FQDN name
It seems that this is related to the code in web100srv.c as it appears to be incorrectly treating the rmt_host variable as an IP address when it contains the hostname string.
This occurs with NDT server v184.108.40.206.
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
- [ndt-dev] Issue 165 in ndt: .meta file: Incorrect values for client IP and server IP, ndt, 12/11/2014
Archive powered by MHonArc 2.6.16.