You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 9, 2020. It is now read-only.
Hi, I was playing youtube video to check port traffic output, but I found the traffic is too low for video streaming compare to that iptraf has reported. I checked source code the buffer is in []byte and which means addTraffic is also in byte. Is this correct? does it have anything to do with addTraffic int and trafficStats int64?
The text was updated successfully, but these errors were encountered:
rchen9012
changed the title
traffic for port reported too little
traffic for port reported too low
Apr 2, 2019
int64 represent that number from -9,223,372,036,854,775,808 ~ +9,223,372,036,854,775,807 ,
it's already exceed 1 EB for a port
so how can int64 get overflow when process is running for a long time ?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I was playing youtube video to check port traffic output, but I found the traffic is too low for video streaming compare to that iptraf has reported. I checked source code the buffer is in []byte and which means addTraffic is also in byte. Is this correct? does it have anything to do with addTraffic int and trafficStats int64?
The text was updated successfully, but these errors were encountered: