tcpdump

You can use a filter like these in wireshark GUI: ip.addr==127.0.0.1 But not in tcpdump $ sudo tcpdump 'ip.addr==127.0.0.1' syntax error.

It’s when you’re able to grab every piece of data transmitted over a network using a tool called tcpdump.

Do you have complete tcpdump logs to prove this, or are you assuming it works that way Amazon said so?

But doing tcpdump and forgetting to write -s 64 should hardly be a crime.

Ping/traceroute/tcpdump/nc (netcat) are your first best friends on Linux and should be the first place you start when you're debugging by hand.

That is insufficent, try going through TCP/IP Illustrated Vol 1 at least and really learning TCP/IP and use tcpdump to rip apart packets.

I should proxy all traffic from my WiFi to my DSL modem via another PC and do tcpdump on that!

I guess an explicit 'got bad data' message would have shown up better in tcpdump though.

Neat, but you can do the equivalent with tcpdump and grep, right?

As a test I successfully hijacked a Reddit identity using nothing but tcpdump on my router.

In one case, I could have used tcpdump to elevate privileges on a customer's router.

I believe capsicum is/will be used for sandboxing sshd, ping and tcpdump.

In terms of number-of-time executed, in a recent environment that I was in, in which approximately 100 or so people had sudo rights, 90+% of the time it was to allow people in various group to run commands like "tcpdump" or "netstat", without giving them full root rights to the system.