Packet flooding

Nov 10 03:44 UTC 2006

miss_xtc@linux:~> ping eecs.berkeley.edu
PING eecs.berkeley.edu (169.229.60.27) 56(84) bytes of data.
64 bytes from mx2.EECS.Berkeley.EDU (169.229.60.27): icmp_seq=1 ttl=242
time=143 ms
64 bytes from mx2.EECS.Berkeley.EDU (169.229.60.27): icmp_seq=2 ttl=242
time=408 ms
64 bytes from mx2.EECS.Berkeley.EDU (169.229.60.27): icmp_seq=3 ttl=242
time=374 ms
64 bytes from mx2.EECS.Berkeley.EDU (169.229.60.27): icmp_seq=4 ttl=242
time=332 ms
64 bytes from mx2.EECS.Berkeley.EDU (169.229.60.27): icmp_seq=5 ttl=242
time=291 ms
64 bytes from mx2.EECS.Berkeley.EDU (169.229.60.27): icmp_seq=6 ttl=242
time=286 ms
64 bytes from mx2.EECS.Berkeley.EDU (169.229.60.27): icmp_seq=7 ttl=242
time=246 ms
64 bytes from mx2.EECS.Berkeley.EDU (169.229.60.27): icmp_seq=8 ttl=242
time=207 ms

--- eecs.berkeley.edu ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7003ms
rtt min/avg/max/mdev = 143.615/286.607/408.739/81.524 ms
miss_xtc@linux:~>


miss_xtc@linux:~> head -2000 /usr/share/misc/termcap | wc -c
95719

I divide 95719 bytes by 2000 to get an average of 48 bytes per line. I add
20 bytes for the IP header and another 20 bytes for the TCP header, for a
grand total of 88 bytes. This nearly the same as the size of the ping
packets.

Shit, I forgot where this was going.

response 2 of 2:

Nov 17 04:43 UTC 2006

miss_xtc can also be interpreted as I miss xtc (the drug). So since that time,
I've like managed to:

1)How some idea what RTT does on ping.
2)Learned how to use lsof to get more information ont TCP connections than
what netstat can provide.
3)I can finally deal with funky search and replaces in emacs.
4)I got a grasp over TCP checksums to the point where I can write a simple
SYN flood attack.
5)I forgot what else. You just fucking suck.