All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Sneeringer <james+lartc@vincentsystems.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Rip problems
Date: Mon, 30 Sep 2002 16:42:40 +0000	[thread overview]
Message-ID: <marc-lartc-103340424030002@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103323533124473@msgid-missing>

On Sat, Sep 28, 2002 at 01:46:37PM -0400, Joseph Watson wrote:
| EXPORT_GATEWAY="no"
| SILENT="no"

This should cause the equivalent of "routed -s" to be run.  The "-s" tells
routed to send routing updates.  Check with "ps ax".  You can get further
debugging out of it with "-d" and "-t".

|   When I start routed, the appropriate routes show up in the portmaster after 
| about a 30 seconds, and all works good for about 2 1/2 minutes.  Then the 
| portmaster sets the Metric to 16 for the route to my subnet behind the 
| firewall, and routing quits working.

PortMasters do this when they think they need to remove the route from the
routing table.  They set the "O" flag (for obsolete, I guess) and set the
metric to 16 (because 16 is the largest metric permitted by RIPv1).  The
route will eventually disappear from the table unless another update is
received.

| If I restart routed, we will repeat the 
| process.  If I stop routed during the 2 1/2 mins, it will immediately set the 
| Met to 16.  This tells me that they are communicating because when I shut 
| routed down the metric is set to 16.  But why does this happen exactly at 2 
| 1/2 min??  I am quite confused?

It sounds like routed isn't sending routing updates.  RIPv1 sends the whole
routing table every 30 seconds to the broadcast address (which is why it
takes about 30 seconds for the PortMaster to see the routes).  My guess is
it's only sending out the initial announcement, and when the PM doesn't see
subsequent announcements for a couple minutes, it drops the routes.

If possible, consider using OSPF instead.  RIPv1 is quite obsolete and
generally useless on subnetted networks like yours.  PortMasters have done
OSPF since ComOS 3.5, and you can implement it on Linux with zebra or gated.
For further PortMaster-specific help, consider subscribing to the
portmaster-users@portmasters.com list.  See http://www.portmasters.com/
for more info.

-James

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-09-30 16:42 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
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 [this message]

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-103340424030002@msgid-missing \
    --to=james+lartc@vincentsystems.com \
    --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.