All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreani Luca <landreani@seltatel.it>
To: lartc@vger.kernel.org
Subject: [LARTC] I: troubles with RIPd
Date: Fri, 14 Jun 2002 08:12:17 +0000	[thread overview]
Message-ID: <marc-lartc-102404361709298@msgid-missing> (raw)

> Hi,
> 
> I'm trying to test RIP but I have some problems:
> 
> 1. 	I connect two linux boxes running zebra and ripd, with a cross
> ethernet cable.
> 
>    	 looking at the sniffer (ethereal) all seems to go well, because I
> can see both boxes sending the Ripv2 response message in   	broadcast
> and receiving them. The fact is that on both the ripd.conf file I put the
> command "redistribute kernel" but only one 	box updates its routing
> table. Why the other box doesn't?
> 
> 2.	Substituting one of the linux boxes with a cisco2600 router, things
> get worst. The cisco router send a ripv2 request packet 	and then
> continues to send CDP packets without redistributing its static routes.
> Does anybady know a simple configuration  	for the cisco2600 rip? On
> cisco web siteI found all but this.
> 
> my zebra.conf:
> 
> hostname Router-A
> password zebra
> enable password zebra
> interface lo
> description Router-A loopback
> ip route 0.0.0.0/0 192.168.100.1
> log file zebra.log
> 
> my ripd.conf
> 
> hostname ripd-r1
> password zebra
> router rip
> network 192.168.100.0/24
> redistribute kernel
> log stdout
> 
> my cisco configuration
> 
> router rip
> version 2
> network 192.168.100.0
> redistribute static
> 
> Many thanks for help,
> 
> Luca Andreani
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2002-06-14  8:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-102404361709298@msgid-missing \
    --to=landreani@seltatel.it \
    --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.