Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No cwnd column exists in flowgrind 0.7.5 output #211

Closed
richi235 opened this issue Oct 12, 2015 · 5 comments
Closed

No cwnd column exists in flowgrind 0.7.5 output #211

richi235 opened this issue Oct 12, 2015 · 5 comments

Comments

@richi235
Copy link

Version: flowgrind 0.7.5 on Debian testing (installed via official Debian repo)

No cwnd column is visible neither in terminal output nor in log-file.
Example:

# ID  begin    end       through transac min IAT avg IAT max IAT uack sack lost retr tret fack reor bkof ca state   pmtu
#       [s]    [s]      [Mbit/s]   [#/s]    [ms]    [ms]    [ms]  [#]  [#]  [#]  [#]  [#]  [#]  [#]  [#]             [B]
S  0  0.100  0.150  10296.105295    0.00     inf     inf     inf    1    0    0    0    0    0    3    0     open  65536
D  0  0.150  0.200      0.000000    0.00   0.003   0.005   0.046    0    0    0    0    0    0    3    0     open  65536

Other tools like ss -i or ip tcp_metrics show the cwnd value.
I remember getting the cwnd value in an older (self compiled) version of flowgrind.

I couldn't find an option in the man page to select or enable the cwnd column or output format.

For me, this issue is quite grave, because the variance of cwnd values is the main data point of my experiments on TCP packet reordering. The easy way of obtaining them was the reason I chose flowgrind in the first place.

@arnd
Copy link
Member

arnd commented Oct 12, 2015

Hi richi,

There should be! Apparently it's broken in this version. Probably because some bug in the freebsd/linux detection. I'll look further. Thanks for the report.

@csamsel
Copy link
Member

csamsel commented Oct 12, 2015

works fine in gentoo

@arnd
Copy link
Member

arnd commented Oct 12, 2015

Hi Richi,

The problem was already fixed in next by alex in commit 4391c57
So you could give the flowgrind version in next a try.
I'll try to make a new release until the end of next week and get it uploaded. However it will take two more weeks after that until it hits testing.

@arnd arnd added this to the flowgrind-0.8 milestone Oct 12, 2015
@richi235
Copy link
Author

Great, thanks.
The experiments for my bachelor thesis will be in 3 weeks so 2 weeks
until the release is no problem. And even if not, self compiling is not that of an issue.
Cool and thanks for the fast reply.

@alexander-zimmermann
Copy link
Contributor

@richi235 Instead of waiting for the new release, you can also checkout the next version from github and compile it from scratch. Should be easy. Alex

@arnd arnd closed this as completed Jun 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants