On Sep 30, 2005, at 11:53 AM, Steven M. Bellovin wrote:
In message [EMAIL PROTECTED], Randy Bush
writes:
To get an understanding of routing-protocols, begin with RIP[3] and
perhaps run your own RIP-lab
necromancy will be severely punished.
many hand-on routing workshops start with rip,
Per Gregers Bilse wrote:
Life begins with ARP.
I would have to argue that for majority of things connected to IP
networks, life begins with DHCPDISCOVER.
Pete
[EMAIL PROTECTED] (Per Gregers Bilse) wrote:
My finest Dilbert moment; it's over ten years old now, in fact.
[...]
*g*
It is _so_ true and so happens in probably 80% of the companies.
It got so bad that if there was nothing to report (ie, no outages, no
problems, everything just worked) Boss
On Thu, Sep 29, 2005 at 05:39:30PM -0400, Mark Owen wrote:
Any suggestions?
Start with the OSI[1] model to grasp the fundamentals, next make sure
you have a basic knowledge of how TCP/IP addressing works[2]. To get
an understanding of routing-protocols, begin with RIP[3] and perhaps
run your
Sabri Berisha [EMAIL PROTECTED] writes:
To get
an understanding of routing-protocols, begin with RIP[3] and perhaps
run your own RIP-lab
necromancy will be severely punished.
---rob
On Fri, 30 Sep 2005 05:50:52 EDT, Robert E.Seastrom said:
Sabri Berisha [EMAIL PROTECTED] writes:
To get
an understanding of routing-protocols, begin with RIP[3] and perhaps
run your own RIP-lab
necromancy will be severely punished.
Sayeth RFC1925:
(4) Some things in life can never
To get an understanding of routing-protocols, begin with RIP[3] and
perhaps run your own RIP-lab
necromancy will be severely punished.
many hand-on routing workshops start with rip, though with the
warning you will now learn why not to use rip. it makes it
easy to teach poison reverse, ...
On 30-Sep-2005, at 09:32, Randy Bush wrote:
To get an understanding of routing-protocols, begin with RIP[3] and
perhaps run your own RIP-lab
necromancy will be severely punished.
many hand-on routing workshops start with rip, though with the
warning you will now learn why not to use rip.
On Fri, Sep 30, 2005 at 10:01:34AM -0400, Joe Abley wrote:
Hi,
RIP also has the advantage that a worked, non-trivial example of the
protocol can fit on a whiteboard, which makes it a reasonable way to
teach the concept of a routing protocol to a classroom full of people
who have never
In message [EMAIL PROTECTED], Randy Bush writes:
To get an understanding of routing-protocols, begin with RIP[3] and
perhaps run your own RIP-lab
necromancy will be severely punished.
many hand-on routing workshops start with rip, though with the
warning you will now learn why not to use
On Thu, 29 Sep 2005 17:39:30 -0400
Mark Owen [EMAIL PROTECTED] wrote:
On 9/29/05, Warren Kumari [EMAIL PROTECTED] wrote:
I have met Senior Network Engineers who don't understand longest
match rule (The traffic will take 10/8 instead of 10.0.0.0/24
because it has a better admin distance,
On Sep 29, 2005, at 12:56 PM, Elmar K. Bins wrote:
[EMAIL PROTECTED] (Elmar K. Bins) wrote:
That somehow sums it up quite good.
Folks, I'm taking this back, seeing that the original poster is not
alone.
Makes me wonder as to what current network engineers do know
about the
world
On 9/29/05, Warren Kumari [EMAIL PROTECTED] wrote:
I have met Senior Network Engineers who don't understand longest
match rule (The traffic will take 10/8 instead of 10.0.0.0/24
because it has a better admin distance, I can override these 300
OSPF routes with a single static supernet, etc),
I'd start with Sam Halabi's Internet Routing Architectures book.
In a similar note, I Do care about networks and the like but
fail to fully understand the extensive details of how it all
works. I do not proclaim myself to be an engineer and try to
stick with what I do well. I read rfc,
On 9/29/05, Mark Owen [EMAIL PROTECTED] wrote:
Any suggestions?
Keep reading everything you can get your hands on. When faced with a
question like who owns this router?, don't waste your time signing
up for a mailing list just to make a fool of yourself. Do some
research. Keep reading. And
Any suggestions?
Keep reading everything you can get your hands on. When faced with a
question like who owns this router?, don't waste your time signing
up for a mailing list just to make a fool of yourself. Do some
research. Keep reading. And before you know it, you'll have taught
yourself
On Sep 29, 1:34pm [EMAIL PROTECTED] wrote:
I am sure that there are other, much more scary examples out there,
feel free to send me (humorous) examples, I need a laugh today...
My finest Dilbert moment; it's over ten years old now, in fact.
Boss: Per, I need you to write much more
On Thu, Sep 29, 2005 at 02:45:20PM -0700, Aaron is rumored to have said:
When faced with a
question like who owns this router?, don't waste your time signing
up for a mailing list just to make a fool of yourself. Do some
research. Keep reading. And before you know it, you'll have taught
On Sep 29, 10:42pm [EMAIL PROTECTED] wrote:
I'd start with Sam Halabi's Internet Routing Architectures book.
Grumble ... with reference to the issue of routing between connected
networks, your choice might be too advanced.
Douglas Comer's Internetworking With TCP/IP Vol I has been one of the
Life begins with ARP.
Or RARP, depending !
--
matthew zeier - Curiosity is a willing, a proud, an eager confession
of ignorance. - Leonard Rubenstein
20 matches
Mail list logo
