like I often want to know "look when I do HTTP requests on port 9772, is it usually fast or slow?"
-
-
-
If tcpdump emits a timestamp for each packet, maybe you could hack a solution together with awk or something?
-
-
-
same! And how long it spends in each state! Let's write one together?
-
ummmmm yes that sounds really fun okay
-
i wonder if we could do this with tshark and lua
-
-
-
I found this. It might help? http://yconalyzer.sourceforge.net/#mozTocId661228
-
cool thanks!
-
-
-
good idea, sounds like a new bcc/BPF tool. Can start with tcpconnect.py and add tcp_close(), with timing
-
but my servers are not going to have BPF for yeeeeears
-
could do it with ftrace or perf, but will be tricky to pull out the port numbers to test. It is doable.
-
ftrace of TCP dport is doable, but "+2(%si):u16" is obviously kernel & arch specifichttps://gist.github.com/brendangregg/eebe3455fd8e528bb14d193a93d43b59 …
-
-
-
ss will get you most of the way there if you pass in the options to enable TCP_INFO. https://github.com/shemminger/iproute2 … in the misc directory
-
the thing you really want is called either web100 or web10g, but they're ooooold. For modern kernels, TCP_INFO and Netlink are it.
-
-
-
`tshark -z conv,tcp,ip.addr==10.1.1.1&&tcp.port=22` fits the bill?
-
sorry, ==22 +quote, otherwise your shell may eat the && :)
-
-
here's a tool that I've used for that sort of thing beforehttps://github.com/DanielArndt/flowtbag …
-
wireshark can do this,but not a cmd tool
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.