"Wireshark Network Analysis" book (the name is still being debated)... low on
sleep... high on ideas...
In my experience, there are two ways to write a book – “carve it” or “birth it.”
When you carve a book, you start with a large piece of granite and painstakingly
shape each part of the book through laborious research on topics you do not
deal with on a daily basis, but you must cover in the tome. The chisel you use is
the size of a toothpick and at times it feels just as fragile against the cold,
unfeeling slab of rock you have decided to mold.
Birthing a book is easier than birthing a human child...
When you birth a book, the entire book is formulating in your head – the table of
contents is taking shape, the tone and depth is coming into focus until… plop!
There it is! You just need to get it out of your head in a clear and concise manner,
get it formatted, proofread and bundled in a warm blanket to show to the world.
The "Wireshark Network Analysis" book has been written by the "birthing"
method.
In essence, I was in labor for 20 years – and yes, damn it, I’d
like a bit of sympathy!
Twenty years ago I presented a session on ARCnet communications to a group
of peer instructors. I delved into the idea of packet structure and the mythical
belief at that time that everyone cared. Somehow though, I related the ARCnet
networking rules and limitations to Sister Gerald, the militant no-nonsense head
of discipline at my Catholic boarding school… and I got a few laughs.
Imagine that… networking can be funny!
(BTW... my spell checker is freaking out over the word "ARCnet"! Ha ha...)
Now – before you think I’m going to mention any of the nuns, my techno-
challenged father, my WoW-addicted son (go Alliance!), my iPhone toting
daughter (who I hope will grow up and make iTunes a less pathetic application)
and my Pavlovian response to a trace file filled with hideous communications
issues and delicious security flaws – this book is not a breezy stroll through the
world of packets.
This book is packed with basic through advanced techniques, tips and tricks to
analyze a variety of network types. It is designed to get you from point A to point Z
(or perhaps I should say point 0x00 to point 0xFF) as fast as possible with a
solid understanding of the processes, protocols, and putrid things that occur
under our noses (or under our feet).
If you don’t have Wireshark loaded on every computer within reach, stop now!
Wireshark is the best girlfriend/boyfriend, wife/husband, mother/father,
sister/brother, dog/cat or lover you have ever had.
* Who is always there to listen to you with a patient and understanding
silence when you are crying in your latte because the users keep
complaining about network performance? Wireshark.
* Who never threatens to fire you if you don’t get those file transfers to occur
at ‘acceptable speeds’ before lunch today? Wireshark.
* Who smiles and sits around all day long just waiting for the moment you
say “I need help”? Wireshark.
That’s right.
So… it’s time to elevate Wireshark from “network wallflower” to network
powerhouse. It’s time to roll up your sleeves(1), get rid of the training wheels, put
on your helmet and reflective gear, tell everyone to get the hell out of your way, get
on that bike – and ride!
By the way – you have no idea how difficult it was to refrain from adding humor
(or at least what I call humor) to this book. It crept in at various points – some I
left in (nestled inside tips throughout the book). Most humorous comments I
simply moved aside for a later book that might focus on the funny side of packet
analysis. I’ll have to wait – that one isn’t even in the early gestational period yet.
Happy New Year to all.
Enjoy life one bit at a time!
Laura
(1) I recently heard a talk show host state that "In difficult times, there are those
who throw up their hands and others who roll up their sleeves"... I am likely the
latter.
