-
Notifications
You must be signed in to change notification settings - Fork 110
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
time_flow_start_ns and time_flow_end_ns is incorect value #313
Comments
Hi @majid-darvishfard, |
this is output of cloudflare goflow v3.4.2 (2020-03-22T22:12:31+0000-travis)
this is Goflow2 version v2.1.3 output
this is Goflow2 Version 1 output:
I test that on 3 different servers and on 3 different netflow device ; Goflow 2 version 1 and Cloudflare Goflow is okey . goflow2 version 2 start and end time is 8 hours ago.If the time zone is not correct, the other two versions should display the wrong time what is differ between goflow2 version2 and goflow version 1 time calculated? why goflow version 2 time is Nanosecond? |
It's sample pcap file Let me know if you find a solution for this |
Hi Louis If you need more file samples, send me your email |
Thank you But could you have a look if #325 resolves your issue? |
hi
i use GoFlow2 v2.1.3 (2024-03-24T04:51:36+0000) with this options :
goflow2 -addr ":8081" -listen "netflow://10.104.32.2:5678/?count=2&workers=8&blocking=false&queue_size=100000" --format=json
time_flow_start_ns and time_flow_end_ns show eight hours later, but the value of time_received_ns is correct.
its sample output :
"type":"NETFLOW_V9","time_received_ns":1713707202442970005,"time_flow_start_ns":1713677209000000000,"time_flow_end_ns":1713677209000000000
i check with netflow version 1 all time is correct
The text was updated successfully, but these errors were encountered: