I did python script to send ARP request from host 1 to another hosts ( host 2, 3, … , host 64 ) and I received the reply and capture the traffic through Wireshrk.
I know the RTT is time for send ARP request and receive ARP reply But my misunderstanding how can I measure the RTT when I send 64 ARP request ?
Let we imagine some cases :
1- Send 1 ARP request , and the information is like the below table , here I think RTT is 1 second because the time for send and receive the ARP is 1 second.
Time-----Sender--Receiver----Protocol--Type
0.000s----A---------broadcast---ARP--Request
1.000s----B---------A-----------------ARP–-Reply
2- Send 2 ARP request , and the information is like the below table , here I don't know how can I measure the RTT ?
Time----Sender---Receiver-------Protocol--Type
0.000s---A---------broadcast------ARP--Request
1.000s---B---------A--------------------ARP-–Reply
1.500s---A---------broadcast------ARP--Request
2.500s---C---------A--------------------ARP-–Reply
3- Also I don't know how can I measure the RTT, when I send 64 ARP request from host 1 to hosts 2,3,4 and so on .
Thank you.
I do not understand the source for the ambiguity.
Your ARP request and reply have the target IP address as the common key allowing for correlation.
This can be done in real time using TSHARK to produce an output stream of ARP requests and replies feeding an application which correlates the request and reply.
TSHARK will include millisecond or better resolution time stamps so it become basic arithmetic.
The harvesting application would ingest the TSHARK stream, it would build a lookup table of request and reply and the timestamps.
So at that point its basic "programming 101" sort of stuff once you have the packet capture set up.
-- Bob
- Badges
- Science topic