From: Ramin Alidousti <ramin@cannon.eng.us.uu.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Rip problems
Date: Sun, 29 Sep 2002 03:43:57 +0000 [thread overview]
Message-ID: <marc-lartc-103327114710601@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103323533124473@msgid-missing>
On Sat, Sep 28, 2002 at 03:46:37PM -0400, Joseph Watson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Saturday 28 September 2002 03:39 pm, you wrote:
> > >Any Ideas?
> >
> > I've not been following closely, but could this be a RIPv1 vs RIPv2 thing ?
> >
> > (As I understand things, RIPv1 did not support CIDR, but RIPv2 does).
Yes, it's correct, RIPv1 is classful.
> Im not sure, but it worked for the first few minutes and then routed started
> changing the routing tables, and I don't know where this info was coming
> from???
Can you explain what exactly was working in the first few minutes? Did you
actually see a /26 route on the portmaster? There are a few timers in RIP.
The 30 sec you mentioned reminds me of the the update advertisement timer
and the 3 min interval is the holddown timer. What is the topology and where
does the remaining block (C - /26) reside? You said that you have a class C.
Is it a class C or a /24? iaw what is the natural class of your netblock?
Do you also run RIP between the portmaster and that other part? This is
important because if you do you'll end up having two different routes to the
same natural class of your netblock which is not what you want.
> I think I am going to try gated.
A better choice is zebra if you're already familiar with cisco syntax.
Does your portmaster support OSPF?
Ramin
>
> - --
> Regards
>
> Joseph Watson
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
>
> iD8DBQE9lgcdABydhMNsDgMRAkvBAJ9YOpwPcYrY8rIYzXbcDEyYK/PVkgCg2xiG
> bnfpmXr42tUrqFNr8WAMdSI> =+cEd
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-09-29 3:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 17:46 [LARTC] Rip problems Joseph Watson
2002-09-28 19:10 ` Joseph Watson
2002-09-28 19:46 ` Joseph Watson
2002-09-29 3:43 ` Ramin Alidousti [this message]
2002-09-29 5:16 ` Joseph Watson
2002-09-29 18:50 ` Ramin Alidousti
2002-09-30 4:39 ` Joseph Watson
2002-09-30 16:42 ` James Sneeringer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-103327114710601@msgid-missing \
--to=ramin@cannon.eng.us.uu.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.