Omitting pps value in the streams config breaks transmission behaviour
bbluser opened this issue · comments
I'm observing a behaviour in the bngblaster statistics that I cannot explain, I think it's a bug.
The concise description is that if in the streams definition the pps is not set explicitly then the tx-bytes are always zero in the run report, independently of the streams direction, whether "upstream", "downstream" or "both".
The rx-bytes are, however always set. Note though, that the bngblaster manual specifies a default value of 1 for pps, but that does not seem to have an effect if not set explicitly.
To Reproduce
Version: 0.8.21
Compiler: GNU (11.3.0)
1.create a config with a stream - e.q. "direction both" - without setting the pps value there
2. run bngblaster for a while and stop it
3. examine the tx-bytes values for the stream in the run report. They equal to 0.
4. in the config set a pps value to 1 for the stream und rerun bngblaster
5. examine the tx-bytes values for the stream in the run report. They have reasonable values.
Expected behavior
Not setting the pps explicitly should have the same effect as explicitly setting it to 1 - which is the default, says the documentation.
I tried but can't reproduce the bug. Could you share the config and log output if started with -l debug please?
Can you try with latest release 0.8.29, as I changed something here which might be related to your issue.
Closed by inactivity. Please open new issue if issue still occurs with latest version 0.8.36 or newer.