talk about network interfaces, here we actually need to run tcpdump -i lo0 or tcpdump -i any to see the local traffic.That’s a lot of output, and it’s a little difficult to read. now that we have some simple network traffic on my laptop, we can look at it with tcpdump!.Wireshark is really easy to install on OS X now! Nobody had trouble with this. I didn’t really explain what TCP was, which seemed okay.Īsk everyone to install Wireshark at the beginning of the workshop. I’ve used this quite a bit at work and it’s been great. So a tool that can spy on network requests can be a really good general-purpose debugging tool. Why use tcpdump? We do a lot of web development almost all of our services talk to each other with network requests. I ran it in an hour, which I think was fine for people who already had some familiarity with the tools, but really aggressive if you’re learning from scratch. I basically did a bunch of live demos of how to use tcpdump & strace, and then took questions & comments as people had them. The notes are a bit sparse and it’s very unclear that anybody other than me will find them legible or useful, but I decided to put them here anyway. This is mostly just so I can reuse them more easily next time, but maybe you will also find it interesting.
a couple of people on Twitter asked about it so here are some notes. This week at work, I ran a workshop on tcpdump and strace.
0 kommentar(er)
