Yes. So the bitrate should represent the avarage and peakrate. Than we know
that the intergap is a constant value.
Verstuurd vanaf mijn iPhone
> Op 13 apr. 2018 om 10:12 heeft Vadim Kochan <vadi...@gmail.com> het volgende
>> On Fri, Apr 13, 2018 at 8:51 AM, jack scholte <jack.scho...@gmail.com> wrote:
>> Hi all,
>> Great tools but about:
>> Trafgen, with -b Option i.e. 100 Mbps results in microbursts. Thus a lot of
>> packets with a very small intergap (us) and than some msec nothing. While
>> testing a shaping policy, the queue couldn’t handle the microbursts.
>> Fortunate I was able to use the intergap Option instead of bit rate.
>> Mausezahn: I was not able to use -a with the -b -A -B Option. Also a L3
>> dsfield would-be Nice.
>> Best regards
>> You received this message because you are subscribed to the Google Groups
>> "netsniff-ng" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to netsniff-ng+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> Hi Jack!
> Thank you for suggestions and report! Regarding trafgen -b option you mean
> that is would be better
> if the packets delay was better normalized regarding the rate ?
> Vadim Kochan
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.