January contest

Posted by stretch in Announcements on Monday, 5 Jan 2009 at 12:00 a.m. GMT

What better way to kick off the new year than with a new packet analysis contest? Following the manner of the last two contests, a packet capture is provided at the end of this post, and you'll have to extract some arbitrary bit of information from it. The challenge this time: find the IOS version running on 172.16.232.10.

The usual guidelines apply:

  • Your answer must include the exact IOS version (for example, "12.3(8)T2," not just "12.3"). The feature set ("IP Base," "Advanced Enterprise," etc.) is not required in your answer.
  • The answer is reachable with the information provided in the capture using only freely available open source tools.
  • Entries must include a brief explanation of how you arrived at your answer; no guessing.
  • One entry per person.
  • Only entries received by email (including those submitted via the contact form) will be accepted. Please do not post your answer in the comments.
  • If you want a book please be ready to provide your mailing address if you are randomly chosen (winners will be notified; your entry doesn't need to include your mailing address).

E-mail your entry to stretch at packetlife dot net (or use the contact form), with the word "contest" in the subject. Entries are due by 23:59 UTC on Thursday, 8 January. The answer and contest winners will be announced in a post the following day. Feel free to leave comments on this post until then, but please refrain from discussing answers or giving hints (comments are moderated).

Book cover

Since the prize for November's contest was Routing TCP/IP volume 1, it's only fitting that the prize this time is Routing TCP/IP volume 2! I've reviewed both volumes (also see my notes) and heavily recommend both.

Copies of these books have been graciously donated by Cisco Press. Three correct entries will be chosen at random and each will win a copy. (Unfortunately, winners of the last contest aren't eligible to win again, but participation in the challenge is of course still welcome.)

Good luck!

Marcio Minicz commented on 5 Jan 2009 at 1:47 a.m.

Good contest. I send my answer.

Giovanni Navarrette commented on 5 Jan 2009 at 5:15 a.m.

That was a fun one..., answer sent.

packeteer commented on 5 Jan 2009 at 6:03 a.m.

as usual I am lost :)

ps. using 'p0f' or 'strings' didn't help

spencer commented on 5 Jan 2009 at 8:24 a.m.

i agree...excellent challenge!

answer submitted.

Francois commented on 5 Jan 2009 at 10:09 a.m.

Nice one!

Bodark commented on 5 Jan 2009 at 10:51 a.m.

Nice challenge, I learned a thing or 2. Keep up the good work!!

Nemako commented on 5 Jan 2009 at 11:58 a.m.

Happy new year and thanks for that funny contest. I send you an email with my answer ;)

Vsaltao commented on 5 Jan 2009 at 2:04 p.m.

Another nice contest.
this one i was able to extract the info needed from the capture
( last one was a little though )

Nick Maio commented on 5 Jan 2009 at 4:35 p.m.

Cool contest....submitted my answer.

Eric commented on 5 Jan 2009 at 4:53 p.m.

I love these contests.

John Burns commented on 5 Jan 2009 at 5:12 p.m.

Great contest answer sent!!

Weiborao commented on 6 Jan 2009 at 3:15 a.m.

That's a great contest, answer sent!

Flo commented on 6 Jan 2009 at 10:49 a.m.

Fun :)

Danail Petrov commented on 6 Jan 2009 at 3:18 p.m.

That was good ;-) Answer sent!!!

Sorin commented on 6 Jan 2009 at 7:22 p.m.

cool contest, keep up the excellent work

Since I've introduces my colleagues to the cheat sheets they become daily visitors !

Dave commented on 7 Jan 2009 at 6:27 a.m.

Very nice contest! I surely learned something here which is always a good thing. :)

Paul Stewart commented on 9 Jan 2009 at 1:49 a.m.

Great contest. I love these things.

Dmitri commented on 9 Jan 2009 at 4:29 a.m.

Nice contest.. Let's try something a bit tougher for next time ;-)

Leave a comment

(optional, will not be published)
(optional)

Comment Tips

  • You can use Markdown syntax for decoration. (Cheat sheet)
  • Links: [Google](http://google.com) or <http://google.com>
  • Use backticks around commands: `ip address 127.0.0.1`
  • Use indentations (tabs) for preformatted text (code blocks)