RE: [ros-bugs] [Bug 695] New: Tracert - Wrong outpout

[Murphy, Ged (Bolton)]

>   -----Original Message-----
>  From: ReactOS.Bugzilla(a)reactos.com 
>  [mailto:[e-mail]] 
>  Sent: 05 August 2005 06:52
>  To: ros-bugs(a)reactos.com
>  Subject: [ros-bugs] [Bug 695] New: Tracert - Wrong outpout 
>  
>  
>  http://reactos.com/bugzilla/show_bug.cgi?id=695
>  
>             Summary: Tracert - Wrong outpout
>             Product: ReactOS
>             Version: 0.3.0-SVN
>            Platform: x86 Hardware
>          OS/Version: ReactOS
>              Status: NEW
>            Severity: normal
>            Priority: P3
>           Component: Networking
>          AssignedTo: ros-bugs(a)reactos.com
>          ReportedBy: gerard.gatineau(a)laposte.net
>  
>  
>  Test done with svn 17040
>  
>  The "tracert command" does not display correct result as below
>  
>  Ros Tracert in Ros
>  ------------------
>  
>  Tracing route to www.laposte.net [81.255.54.10]
>  over a maximum of 30 hops:
>  
>    1   164 ms    80 ms    81 ms  
>  aaaAAaaaaaaAaaaa-LIBGCCW32-EH-2-SJLJ-GTHR-MINGW32 [81.255.54.10]
>  
>  Trace complete.
>  
>  The tracert command ( from Ros ) ran in windows displays correctly .
>  It means that the tracert program in Reactos is correct but 
>  the Ros networking
>  support is the problem
>  
>  Ros Tracert in Windows
>  ----------------------
>  
>  Tracing route to www.laposte.net [81.255.54.10]
>  
>  over a maximum of 30 hops:
>  
>    1     1 ms    <1 ms    <1 ms  192.168.0.254 
>    2    83 ms    84 ms    84 ms  192.168.254.254 
>    3    61 ms    59 ms    59 ms  
>  vlq-6k-2-a11.routers.proxad.net [212.27.37.190] 
>    4    62 ms    61 ms    62 ms  
>  p19-6k-2-v800.intf.routers.proxad.net [212.27.50.6] 
>    5    62 ms    62 ms    62 ms  
>  aub-6k-1-v806.routers.proxad.net [212.27.50.162] 
>    6    60 ms    62 ms    61 ms 
>  GE0-3-0-0.noaub101.Aubervilliers.francetelecom.net [193.252.161.97] 
>    7    60 ms    59 ms    62 ms  
>  pos5-0.ntaub301.Aubervilliers.francetelecom.net
>  [193.252.103.86] 
>    8    69 ms    69 ms    70 ms  pos9-0.nrlyo201.Lyon.francetelecom.net
>  [193.252.103.77] 
>    9    73 ms    72 ms    75 ms  pos6-0.ncnic201.Nice.francetelecom.net
>  [193.252.101.157] 
>   10    74 ms    73 ms    74 ms  81.255.54.252 
>   11    76 ms    75 ms    74 ms  www.laposte.net [81.255.54.10] 
>   12    74 ms    76 ms    77 ms  www.laposte.net [81.255.54.10] 
>  
>  Trace complete.
>   

This is because GetNameInfo is not implememted in ROS. I originally used
GetHostByAddr, but if the IP does not have a hostname, it takes a long time
for the function to return, blocking the flow of the program. This is the
reason tracert hasn't been added to the bootcd yet.

Alex's ws2_32 rewrite should solve this. I'm hoping he's used GetNameInfo,
as GetHostByAddr is depricieted anyway now in favour of this.

I also need to do testing with tracert in ROS, as it is currently untested
and will more that likely contain a few bugs. (such confidence I have in my
code :) )

I'm also wondering why node 11 and 12 are the same in the above windows
output. I haven't seen that happen before. Again, I'll look into it.

Ged.



************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk 
<mailto:[e-mail]> and then delete this message. 

Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com