kernel routes via RIP

C. Martin Capriotti

unread,

May 23, 1996, 3:00:00 AM5/23/96

to

Hi all,
I want gated to announce kernel routes via RIP:

export proto rip {
proto kernel {all;};
} ;

That didn't work, so I used static routes announcing the kernel
ones to gated and used:
export proto rip {
proto static {all;};
} ;
but I get nothing.
I'm using Linux 1.2.8, 1.2.13 and 1.3.45

Martin

R Bezuidenhout

unread,

May 24, 1996, 3:00:00 AM5/24/96

to

Hi ...

Is it possible that you could give some more info ... e.g. ...
Does all the interfaces have the same netmask ??? because if
they don't Gated with RIPv1 will not export any RIP !!

Another thing ... is your IP forwarding enabled ???

I hope this helps ....

Reinier

--
########################################################################
# #
# Reinier Bezuidenhout Company: Mikomtek CSIR, ZA #
# #
# Network Engineer - NetSec development team #
# #
# Current Projects: NetSec - Secure Platform firewall system #
# http://www.mikom.csir.co.za #
# #
# E-mail: rbez...@mikom.csir.co.za #
# #
########################################################################

Acee Lindem

unread,

May 24, 1996, 3:00:00 AM5/24/96

to

"C. Martin Capriotti" <mca...@unrctu.edu.ar> writes:
>
> Hi all,
> I want gated to announce kernel routes via RIP:
>
> export proto rip {
> proto kernel {all;};
> } ;
>
> That didn't work, so I used static routes announcing the kernel
> ones to gated and used:
> export proto rip {
> proto static {all;};
> } ;
> but I get nothing.
> I'm using Linux 1.2.8, 1.2.13 and 1.3.45
>
> Martin
>

Add a metric to your export statements. The default metric for
routes exported into RIP is 16. For example:

export proto rip {
proto static {all metric 1;};
} ;

will cause static routes meeting other RIP V1 advertisement criteria
to be advertised.

The reason for default metric of infinity is that one should always
specify a metric when exporting between protocols with incompatible
metrics. It would be better if the GateD parser would recognize
situation where and metric is required and flag while allowing
situations where no metric is required (e.g., RIP to RIP or DIRECT
to RIP).

Acee

Brian Topping

unread,

May 24, 1996, 3:00:00 AM5/24/96

to

R Bezuidenhout wrote:
> ...because if

> they don't Gated with RIPv1 will not export any RIP !!

Aieeee! I think this is what I was getting stung by. Is there any way around this?

Can I explicitly define the interfaces with their netmasks and get RIP back up?

Thanks, and have a great weekend all!

-B

C. Martin Capriotti

unread,

May 24, 1996, 3:00:00 AM5/24/96

to

On Fri, 24 May 1996, R Bezuidenhout wrote:

> Hi ...
>
First, thanks for your interesting

> Is it possible that you could give some more info ... e.g. ...

> Does all the interfaces have the same netmask ??? because if

> they don't Gated with RIPv1 will not export any RIP !!
>

No, they're differnet but I am using RIP2

> Another thing ... is your IP forwarding enabled ???
>

Yes, IP multicating too... and in gated.conf:

rip yes {
interface all ripin ripout version 2;
};

> I hope this helps ....
>
> Reinier
>

> >

> > Hi all,
> > I want gated to announce kernel routes via RIP:
> >
> > export proto rip {
> > proto kernel {all;};
> > } ;
> >
> > That didn't work, so I used static routes announcing the kernel
> > ones to gated and used:
> > export proto rip {
> > proto static {all;};
> > } ;
> > but I get nothing.
> > I'm using Linux 1.2.8, 1.2.13 and 1.3.45
> >
> > Martin
> >
> >
> >
>
>

> --
> ########################################################################
> # #
> # Reinier Bezuidenhout Company: Mikomtek CSIR, ZA #
> # #
> # Network Engineer - NetSec development team #
> # #
> # Current Projects: NetSec - Secure Platform firewall system #
> # http://www.mikom.csir.co.za #
> # #
> # E-mail: rbez...@mikom.csir.co.za #
> # #
> ########################################################################
>

Martin