You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2024. It is now read-only.
What steps will reproduce the problem?
1.In the protocol selection chosen etherner II , 802.3 LLC, 802.3 LLC SNAP
2.Try to send this protocol data from fixed source to fixed destination by
giving source and destination MAC respectively
3.Steam data also selected , for example 10000 packets.
What is the expected output? What do you see instead?
Observed result: When i am trying to listen this generated traffic from another
port on the switch , nothing was shown from ostinato. But other communication
works fine on the switch.
Here i am trying to generate extra traffic on ethernet based network switch.
PS: Both source and destination machine running with ostinato and drone.
If this possible sending the data like this on ostinato how much maximum data
it supports in Mbps.
What version and revision of the product are you using (available in the
About dialog)? On what operating system?
Ostinato 0.2
Please provide any additional information below.
Original issue reported on code.google.com by chi...@gmail.com on 13 Oct 2010 at 9:25
The text was updated successfully, but these errors were encountered:
Chirug,
A few questions -
Are you using port mirroring on the switch?
Can you run wireshark on the source machine and check if Ostinato is generating
packets?
Can you save the Ostinato stream and attach it here?
btw you need to run Ostinato (and drone) only on the source machine, not the
destination.
Regards,
Srivats
Original comment by pstav...@gmail.com on 13 Oct 2010 at 12:12
Hi,
can not able to repeat this problem again. Once i got this problem , that time
could not able to save the captured wireshrk files. Any way i will update here
if i repeat the problem.
Original comment by chi...@gmail.com on 19 Oct 2010 at 3:44
Original issue reported on code.google.com by
chi...@gmail.com
on 13 Oct 2010 at 9:25The text was updated successfully, but these errors were encountered: