Wireshark-users: Re: [Wireshark-users] Wireshark trace file for load runner events

From: Martin Visser <martinvisser99@xxxxxxxxx>
Date: Tue, 2 Mar 2010 14:02:30 +1100

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


On Mon, Mar 1, 2010 at 6:22 PM, Mahendranath.N <mahendranath_n@xxxxxxxxxxx> 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... 

Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users