Thursday, July 05, 2007
There is a difference between routing and blocking …
One of these days, I'll get this networking stuff down.
I talked to Dan the Network Engineer about the Riverstone router and it's not the Riverstone that's losing its mind, it's me.
Just because I route outgoing traffic to 172.16.0.0/12 to nowhere on our core router, doesn't mean that incoming traffic “from” 172.16.0.0/12 from “The Outside” (and by “The Outside” I mean, “The Internet At Large”) gets routed to nowhere.
Nope, it gets routed to the destination, which is on the other side of the firewall, which is doing its job and dumping the garbage packets.
Notes on an overheard conversation between a customer of the Monopolistic Phone Company and Technical Support on an email issue
“Hello, this is Bob, The Monopolistic Telephone Company Technical Support Technician. How may I help you?”
“Bob, my emails to Earthlink aren't getting through, but I can still receive emails from Earthlink. Can you help me?”
“Well, my father lives way out in the country, and I don't know where or how the equipment is set up out there, but I think that the cows get in between the equipment and block the signal.”
