Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Stop button does not work on Intense Packet Generator tool #320

Open
enski6 opened this issue Apr 25, 2023 · 7 comments
Open

[BUG] Stop button does not work on Intense Packet Generator tool #320

enski6 opened this issue Apr 25, 2023 · 7 comments
Assignees
Labels

Comments

@enski6
Copy link

enski6 commented Apr 25, 2023

What OS and Version?

Windows 10
PacketSender version 8.3.6
Two computers hooked directly together with 10Gb fiber.

Description of issue

While using the Intense Packet Generator tool, setting the speed to 1250 MB/sec the Stop button does not work. In order to stop sending packets I have to close the application.

I am also only able to send packets at a max rate of about 230,000 packets/sec, how can one send at a higher rate?

Thanks

@enski6 enski6 changed the title [BUG] [BUG] Stop button does not work on Intense Packet Generator tool Apr 25, 2023
@dannagle
Copy link
Owner

I can't recreate start/stop GUI problem on my end. I don't have 10G fiber though. Perhaps that level is what messes with the event loop.

There is a command line version that is able to run faster:
https://github.com/dannagle/PacketSender#cliintensetraffic

You can give that one a try.

@enski6
Copy link
Author

enski6 commented Apr 26, 2023

Thanks, in using the CLI version I am only able to get around 90,000 packets/sec by setting the rate to 0. If I use the bps setting the most I could generate was about 1000 packets/sec.
packetsender --rate 0 --num 10000000 -u 192.168.2.100 12345 "hello"

@dannagle
Copy link
Owner

That is odd it is actually slower. I will have to look into that. Can you launch multiple terminal windows with multiple instances running?

@dannagle dannagle added the bug label Apr 26, 2023
@enski6
Copy link
Author

enski6 commented Apr 26, 2023

Yes, I can open another instance and run them simultaneously. 2 instances produced about 150,000 packets/sec total based on Wireshark(packets/time).

@dannagle
Copy link
Owner

dannagle commented Apr 26, 2023

That's good. That tells me I can solve this problem by creating additional threads to help with the sending.

Does it matter if the outgoing data is coming from multiple source ports? I can't use the same socket in multiple threads (well, not easily).

@enski6
Copy link
Author

enski6 commented Apr 26, 2023

Multiple ports are fine. We are just trying to max out packets/sec using small packets to simulate server load.

@dannagle
Copy link
Owner

If you don't mind, will you email me at [email protected] ? I plan to create an alpha build for you to try out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants