From: Joseph Watson <jtwatson@datakota.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Rip problems
Date: Sat, 28 Sep 2002 17:46:37 +0000 [thread overview]
Message-ID: <marc-lartc-103323533124473@msgid-missing> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I am running a portmaster for dialup customers. This portmaster has a T1
connected to it, and is the gateway to the internet. Behind it I have a
class C network divided up into 4 subnets, netmask 255.255.255.192 or /26.
One of the subnets is behind my linuxbox (the 192 network). The portmaster
is running rip(1), so I installed routed on the linux box, and configured it
to share its information.
ie.
EXPORT_GATEWAY="no"
SILENT="no"
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. 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?
Any suggestions would be great.
- --
Regards
Joseph Watson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9lesTABydhMNsDgMRAuZzAKCDKkKGviW6PYX4YxDyTfyzikNhHQCeLiSz
+cONh6fjWlgOY4eirljT0CI=
=vgXh
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-09-28 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 17:46 Joseph Watson [this message]
2002-09-28 19:10 ` [LARTC] Rip problems 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
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-103323533124473@msgid-missing \
--to=jtwatson@datakota.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.