While defining streams for NAT, instead of specifying each stream in blaster file, step can be introduced

[ArunPrakashThangaraj]

Is your feature request related to a problem? Please describe.

While preparing the blaster file for multiple NAT streams (say 100 streams with different source-port), I need to include 100 streams in the blaster file manually. Instead, if we have total streams, step, starting source-port, the file looks much simpler.

Describe the solution you'd like
In the following stream-group-id 1, I have 100 streams and the only difference is the source-port. Instead of mentioning each stream here, we can simplify it by having, source-port-start, total-port, step
{
"name": "TCPSTREAM1",
"stream-group-id": 1,
"type": "ipv4",
"direction": "both",
"vlan-priority": 1,
"raw-tcp": true,
"source-port": 65001,
"length": 100,
"nat": true,
"pps": 0.3
},
{
"name": "TCPSTREAM2",
"stream-group-id": 1,
"type": "ipv4",
"direction": "both",
"vlan-priority": 1,
"raw-tcp": true,
"source-port": 65002,
"length": 100,
"nat": true,
"pps": 0.3
},
{
"name": "TCPSTREAM3",
"stream-group-id": 1,
"type": "ipv4",
"direction": "both",
"vlan-priority": 1,
"raw-tcp": true,
"source-port": 65003,
"length": 100,
"nat": true,
"pps": 0.3
},

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.