From trending it seems like TRex threads use thread-local PRNGs,
resulting in multiple packets (one from each thread) for the same flow.
Hopefully, without a seed set, each thread will pick a different seed.
We are risking some threads will still pick the same seed occasionally,
but I doubt TRex API has a better way to prevent this issue.
Change-Id: Ie6ed42669d6e2463627760f89d2426d4e6bf0155
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
min_value=self.p1_dst_start_ip,
max_value=self.p1_dst_end_ip,
size=4,
- limit=10000,
- seed=0x0000
+ limit=10000
),
STLVmWrFlowVar(
fv_name=u"dst",
min_value=self.p2_dst_start_ip,
max_value=self.p2_dst_end_ip,
size=4,
- limit=10000,
- seed=0x0000
+ limit=10000
),
STLVmWrFlowVar(
fv_name=u"dst",
min_value=self.p1_dst_start_ip,
max_value=self.p1_dst_end_ip,
size=4,
- limit=100000,
- seed=0x0000
+ limit=100000
),
STLVmWrFlowVar(
fv_name=u"dst",
min_value=self.p2_dst_start_ip,
max_value=self.p2_dst_end_ip,
size=4,
- limit=100000,
- seed=0x0000
+ limit=100000
),
STLVmWrFlowVar(
fv_name=u"dst",
min_value=self.p1_dst_start_ip,
max_value=self.p1_dst_end_ip,
size=4,
- limit=1000000,
- seed=0x0000
+ limit=1000000
),
STLVmWrFlowVar(
fv_name=u"dst",
min_value=self.p2_dst_start_ip,
max_value=self.p2_dst_end_ip,
size=4,
- limit=1000000,
- seed=0x0000
+ limit=1000000
),
STLVmWrFlowVar(
fv_name=u"dst",