All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Watson <jtwatson@datakota.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Rip problems
Date: Sat, 28 Sep 2002 19:10:12 +0000	[thread overview]
Message-ID: <marc-lartc-103324031327732@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103323533124473@msgid-missing>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I have identified the source of the problem, but not the cause of it. Here is a output from
tcpdump that shows the rip traffic from the routed process on the linuxbox.  Again I have
configured routed as follows:

EXPORT_GATEWAY="no"
SILENT="no"

and it gets its information from the network setup on the localmachine.

in the following output, all xx.xx.xx. represent the same class C address.

[root@dwwireless httpd]# tcpdump -ni eth0 udp port 520 and src host xx.xx.xx.52
tcpdump: listening on eth0
12:33:16.427345 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:33:21.658707 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(16) {xx.xx.xx.0}(16) (DF)  <----- restarted routed ------
12:33:22.359761 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-req 24 (DF)
12:33:52.358588 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(1) {192.168.1.0}(1)[|rip] (DF)
12:34:22.359529 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(1) {192.168.1.0}(1)[|rip] (DF)
12:34:52.360541 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(1) {192.168.1.0}(1)[|rip] (DF)
12:35:22.361625 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(1) {192.168.1.0}(1)[|rip] (DF)
12:35:52.362543 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(1) {192.168.1.0}(1)[|rip] (DF)
12:36:22.365285 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(16) {192.168.1.0}(1)[|rip] (DF)
12:36:52.364554 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(16) {192.168.1.0}(1)[|rip] (DF)
12:37:22.365592 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:37:52.366556 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:38:22.367531 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:38:52.368547 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:39:22.369516 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:39:52.370524 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:40:22.371571 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:40:52.372525 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:41:22.373521 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:41:52.374513 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:42:22.375511 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:42:28.221015 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(16) {xx.xx.xx.0}(16) (DF)  <---- restarted routed -------
12:42:28.937439 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-req 24 (DF)
12:42:59.066864 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(1) {192.168.1.0}(1)[|rip] (DF)
12:43:29.067806 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(1) {192.168.1.0}(1)[|rip] (DF)
12:43:59.068802 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(1) {192.168.1.0}(1)[|rip] (DF)
12:44:29.069811 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(1) {192.168.1.0}(1)[|rip] (DF)
12:44:59.070798 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(1) {192.168.1.0}(1)[|rip] (DF)
12:45:29.073590 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(16) {192.168.1.0}(1)[|rip] (DF)
12:45:59.072795 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 3]: {xx.xx.xx.192}(16) {192.168.1.0}(1)[|rip] (DF)
12:46:29.073861 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:46:59.074794 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:47:28.741356 xx.xx.xx.52.520 > xx.xx.xx.62.520:  RIPv1-resp [items 13]: {xx.xx.xx.65}(2) {xx.xx.xx.67}(2)[|rip] (DF)
12:47:29.075708 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)
12:47:59.076795 xx.xx.xx.52.520 > xx.xx.xx.63.520:  RIPv1-resp [items 2]: {192.168.1.0}(1) {xx.xx.xx.0}(1) (DF)

As you can see, routed is expiring the route xx.xx.xx.192 network, and adding one to the hole class C block.
This is obviously wrong, and I don't know why it is changing its routing information in mid swing???

Any Ideas?

- --
Regards

Joseph Watson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9lf6UABydhMNsDgMRAlT4AKDaZwYQHEzVA/VQGuadgeUlwcptsQCgxOyU
LWz1POL9TDTO+LELeMkFS3s=
=yRZe
-----END PGP SIGNATURE-----

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

  reply	other threads:[~2002-09-28 19:10 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 [this message]
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-103324031327732@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.