Better UX for (very) slow streams

[pstavirs]

For slow (or very slow) streams such as 1 packet per 30s or 1 in an hour or more,

• Clicking on Stop Tx will stop only after the 30s or 1 hour timer is over
• Make it easier to enter such a rate e.g. instead of 0.033 packets/sec, 1 packet every 30s (or 2/min; possible time units - s(ec), m(min), h(our))

Original email:

Also regarding by comment on handling properly slow packet rate (one in 30 Sec, one in 2-3 hour to simulate lets say DHCP renew packet, etc).

Maybe it will be good to have a checkbox between two windows (or somehow inside same one), for fast /slow packet rate. By fast I am referring to more then 1 packet per second.

Anything lower then that will be considered slow. If slow rate is selected then replace packets/Sec with “Packet every xy Sec”. In this mode You can remove the focus on speed and stop the stream immediately when the end user press it.

If let’s say I would like to simulate DHCP Renew every 4 Hour I will set in the new interface 3600x4 Sec and your software will send a prerecorded DHCP renew packet once every 4 hours. And if I would like to stop it it will be immediate and I will not have to wait 4 hour for it to stop like I had to wait 30 Sec to stop my steam simulating PoE LLDP Power Advertisement once every 30 Sec.

[pstavirs]

Possible solutions for timer issue

• Use PcapSession for TxThread (Linux only?)
• Change timer function pointer at start of Tx to one which checks for stop for very slow streams