Tag: fun

A bunch of networking jokes

A friend of mine shared a butch of networking jokes. I am going to copy them all here, for historical purposes. Make sure to visit the site for a full version

A pair of jumper cables walks into a bar. Bartender says: “I’ll serve you, but don’t start anything.” – Matthew Norwood

A dhcp packet walks into a bar and asks for a beer. Bartender says , “here, but I’ll need that back in an hour!” @brandoncarroll:

An LSA Type 6 packet walks into a bar and asks the bartender for a drink. The bartender ignores him. – @someclown

An LSA Type 2 packet walks into a bar and asks for a beer. Bartender say’s “here, but don’t leave the area with it.” @someclown

ICMP packet walks into a bar from warehouse and announces – “no more beer” – @fsmontenegro

Sometimes I feel like a multicast packet. Ask 10 differenet people how to get somewhere and get 10 different answers. @jodylemoine

An RTP packet walks into a bar through the wrong entrance. The barman says “You’re not getting any special treatment” – @xchewtoyx

A multicast packet walks into a bar and leaves by four different exits at the same time – @xchewtoyx

“Knock Knock” “who’s there?” “Denial of Service Attack” “Den…?” “Sn(kRzIhAw]BoKaoOv0liZPhl~FaLoaSa*AgSeaLp|ExleT…” – @MattGordonSmith

A BGP Update walks into a CRS-1. He walks back out with a corrupt optional transitive attribute. – @xchewtoyx

A DNS packet walks into a liquor store – where do I find beer “ABC”?. Clerk: aisle 4, top row on the right. @fsmontenegro

An IPv6 packet walks into a bar. Nobody talks to him. @fsmontenegro

A tcp packet walks in to a bar and says “I want a beer”, barman says “you want a beer?” and tcp packet says “yes, a beer” @stevie_chambers

Dhcp pkt stands on a dark street and shouts “does anyone have a beer!?” A bartender of a nearby bar says “sure come on in, lets see the menu. You can have this beer. Patron says “can I have this beer?” Bartender “Aye. But I will need the glass back..er unless you still want it! – anonymous

A Network Engineers tell a joke in a full bar. One man laughs. They start talking about NX-OS and have a blast. @icemarkom

Q. How do you catch an Ether Bunny.
A. With an Ethernet!!

Q. What did the OSPF router say to the other OSPF router ?
A. Hello. Hello. Hello. Hello. Hello. Hello. Hello. Hello.

Five routers walk into a bar. Who gets the car keys? The Designated Router. @scottrobohn

DNS is the root of all problems – @jimbofx

IP packet with TTL=1 arrives at bar. Bartender: “Sorry, can’t let you leave…and you don’t get any beer either…” @fsmontenegro

And some more unpublished jokes from comments

I’d tell you a UDP joke, but you might not get it.

An IPv4 address space walks into a bar and says to bartender: “One strong CIDR please I’m exhausted!”

A class default packet walks into a bar. Barman knocks him down and serves next customer.

An NTP packet calls ahead to make sure the bar’s open. By the time he gets there, it’s closed.

An ICMP Redirect walks into a bar. Everybody moves next door.

A bunch of TCP packets go into a bar, until it’s overcrowded. The next day, half as many go in.

A packet walks into an 802.3x bar. The bartender says, “Be with you in a second.”

An ARP request goes to McDonald’s and asks for a Big Mac.

Part 2. Visit their site, it’s great.  I promise

@mfratto A runt packet walks into a bar, the bartender says “You could use a byte.” –

@samj: OH: “A UDP packet walks into a bar. The bartender doesn’t acknowledge him.”

@etherealmind TCP packet tries to get past the firewall on the way to the bar. Firewall says “hey, you’re out of order”.

@pello FTP-data packet tries to get past the checkpoint firewall when someone changed the bar policy. “Hey, first packet is not SYN”

_johnmcmanus_ a broadcast walk into the bar, everyone stops what they are doing to look

RT @BartSwinnen An IPv4 address space walks into a bar: “A strong CIDR please. I’m exhausted.” #ipv6

An IPv6 NS packet walks into a bar and yells, “Is anyone in here named John Smith?”. When no one answers, he sits down and orders a beer.

@xme an IPv4 packet walks on a bar and orders a CIDR and says “I’m exhausted” ^_^

Brandon Carroll @brandoncarroll talking about the Last of the Bogons.

A Bogon walks into a bar. The Bartender says… Youíre not supposed to be here! :)

A Bogon walks into a bar. The Bartender says….. I thought you were extinct !

A Bogon walks into a bar and says to the Bartender… Take me to your leader!

And some from me.

MTU oversized train enters a tunnel, but gets annihilated


You might be an Network Guy If

Preparing to CCNP SWITCH by the official certification guide involves lots of side research. Previous time, filling my gaps in STP, I found spanning tree poem. Today I was researching about STP again and found an interesting text, which is a joke about telecom guys. By far I know telecom-involved people as the ones who have no any kind of subculture whatsoever. Programmers and Administrators have their jokes, legends, stories, even official days. Telecom guys do not seem to. Or it might be my impression only. Nevertheless, I’m going to collect stuff here which might belong to a “nonexistent” telecom subculture.

You might be an Network Guy If

You know more ip addresses than phone numbers
You regularly mock TV shows for using technology that isn’t part of the feature set available on the devices they have
You correct people who mix up Megabytes and Megabits
You waited eagerly for wireless N to be approved officially.
You can explain everything in your life using 7 layers
You tell people not to use TKIP because of it’s security flaw
You think people should be able to do without DNS for a day, just use IP addresses…
You follow your wife around shopping retail stores and spend your time skimming the ceilings for their APs and mapping out a heat map of the store in your head
You know what TCP/IP stands for, not to mention DNS, HTTP, SNMP, BGP, OSPF, WPA, and DHCP – Sometimes you wonder if you know more acronyms than words
You’ve known what IPv6 was for years
Cmd, telnet, and ssh are useful everyday tools, not just black boxes
Linus Torvalds comes up in everyday conversation
You know jokes about DHCP and LSAs
You cringe when you have to use a Gui to configure a switch or router
Your Amazon wish list consists of routers and ASA firewalls
Dealing with Tier 1 tech support makes you pull your hair out.
You have read the NSA’s security best practices
The routing protocol in your house changes daily depending on what you have been reading
You know what a nibble is
You know what 1000 Terabytes is called
You can intelligently discuss how Egypt shut off their Internet to the country


Funny bugfixes in Nortel 6.2.4 ERS software release

There are few nice bugs in Nortel 6.2.4 ERS release (release notes). There are update surprises:

  • After Upgrading from 6.1.1 to 6.2.1, QoS configurations were lost (wi00838747)
  • Some links get disabled after upgrade from 5.1.x to 6.x (wi00731564)
  • Stack upgrade failure from to with a large config file (wi00882592)
  • After upgrading from 5.1.4 to 6.2.1 EDM routing/IGMP/SNOOPING table expanded indefinitely causing high CPU utilization (wi00886347)

Weird issues, which can be explained by lack of objects interoperability:

  • Unable to add static route under certain conditions, adding the route required a reboot (wi00937754)
  • With autosave enabled on 5632FD, if the power is recycled the fiber connectivity to 470-48T switch is lost (wi00941175)
  • Autonegotiation could not be disabled (wi00824799)
  • Ping or Telnet to any DNS hostname would sometimes cause loss of connectivity to the management VLAN requiring a reboot of the stack (wi00933202)

Very weird bugs, which cause many wtf-like questions on the source code:

  1. Using show running-configuration with 744 VLANs configured, spiked the CPU utilization to 100% for about 12-15 minutes (wi00907462)
  2. Switch does not learn MAC of format xx:59:xx:xx:xx:xx (wi00870510)
  3. Cannot give an IP address to the switch with the last octet as “0” (wi00872983)

I can explain the third bug by an error of checking network address in classless notation. I suppose, the code was checking an IP address in a classful way, i.e. if IP ends by zero, it’s a network address, hence can not be assigned.

How could they create bugs 1 and 2? They should’ve had hard coded numbers 744 and 0x59 (dec89). Why? what was the purpose? What was the algorithm? Can you guess an algorithm by knowing the information above?


That is my team I have played paintball with. There are two girls one of them Is blond. Guess who?