Wireshark mailing list archives
Re: Wireshark trace file for load runner events
From: "Mahendranath.N" <mahendranath_n () yahoo co in>
Date: Wed, 3 Mar 2010 18:10:20 +0530 (IST)
Hi Martin, Please find the attched wiresharkl files captured during navgation of same flow manually & by load runner. manually we observed 161 entries and when we capture the same process by load runner we observed 369. We made sure there is no extra browser or extra software running n the system. Please find the attchment for both the files. Info ont he extra entries during load runner capture will help us greatly. Regards, Mahendranath --- On Tue, 3/2/10, Martin Visser <martinvisser99 () gmail com> wrote: From: Martin Visser <martinvisser99 () gmail com> Subject: Re: [Wireshark-users] Wireshark trace file for load runner events To: "Community support list for Wireshark" <wireshark-users () wireshark org> Date: Tuesday, March 2, 2010, 8:32 AM Mahendranath, You need to provide a little more info for us to help. I am sure that "Ethernt 2, src : HewlettP_5c:80:39" isn't all that appears the information on the packets you are seeing. The best guess is that "Ethernet 2" is the name of interface and that "HewlettP_5c:80:39" is simply the source MAC address of the packet (where the first 3 bytes of the actual MAC address xx:xx:xx get resolved to HewlettP") I think we would need to see a well-filtered sample of the packets from your manual and Loadrunner scenarios to be able to compare. (Loadrunner tries to "emulate" clients so it simply might be not be a perfect emulator) Regards, Martin MartinVisser99 () gmail com On Mon, Mar 1, 2010 at 6:22 PM, Mahendranath.N <mahendranath_n () yahoo co in> wrote: Hi , I have a scenario and i observed around 160 wire shark calls for manual navigation of that scenario,.The same scenario I am trying to capture by using load runner with Wireshark enabled, but observed 240 calls. Can anyone clarify why there are extra calls for navigating the same scenario by load runner. Each extra call has Etehernet syntax as below : Ethernt 2, src : HewlettP_5c:80:39 It will be great if someone can clarify the above... Regards, Mahendranath ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe -----Inline Attachment Follows----- ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Attachment:
Manual.pcap
Description:
Attachment:
Loadrunner_capture.pcap
Description:
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- Re: Wireshark trace file for load runner events Martin Visser (Mar 01)
- <Possible follow-ups>
- Re: Wireshark trace file for load runner events Mahendranath.N (Mar 03)
- Re: Wireshark trace file for load runner events Martin Visser (Mar 04)