Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 Nov 1997 22:22:38 -0500 (EST)
From:      zoonie <zoonie@myhouse.com>
To:        "Daniel O'Callaghan" <danny@panda.hilink.com.au>
Cc:        Scot Elliott <scot@poptart.org>, akl@wup.de, amr@wup.de, isp@freebsd.org
Subject:   Re: RIP vs. OSPF
Message-ID:  <Pine.NEB.3.96.971118221154.1436A-100000@nak.myhouse.com>
In-Reply-To: <Pine.BSF.3.91.971119132323.235G-100000@panda.hilink.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Nov 1997, Daniel O'Callaghan wrote:

> Not true.  RIP v1 (Novell 3.1x) supports fixed-length subnets.  That is, 
> *all* subnets must have the same netmask.  RIP v1 also assumes that all 
> subnets of a network are contiguous, which is not necessarily so, these days.
> 
> RIP v 2 supports variable-length subnet masks and remote subnets, but 
> still is not as good as OSPF.

true, but OSPF is best if you have redundant paths.  i don't exactly
remember the entire network diagram since i deleted it but i don't think
that there were redundant paths....

> I recommend going to OSPF and using default routes on the Novell gateways 
> and static routes *to* the Novell gateways.  Novell fileserver routing is 
> pathetic, particularly 3.x.

assuming that there weren't any redunant paths on the network i would
recommend using RIPv2 myself and go to OSPF if you have redundant paths on
your network for the quicker convergance.  why incur the overhead of OSPF
if there is no good technical reason for it?

i say this from experiance because i worked at a place where we didn't
have any redundant paths on the network but it was setup with OSPF as the
routing protocol....then one day OSPF just took a hike for no reason at
all (this was on cisco IOS 9.1) and i agured the technical merits of it vs
RIP for the network with a friend and co-worker of mine.  i favored OSPF
at the time and my friend favored RIP.  after some discussion and giving
it some thought i really didn't see a reason to run OSPF and incur the
overhead.  that's my 2 cents worth.....





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96.971118221154.1436A-100000>