From: Michael Popovich (m.popovich@xxxxxxxxx)
Date: Fri May 24 2002 - 01:30:47 GMT-3
That brings up a good question.
If you have a requirement that you can't have routes to null0 does that mean
you can't create static routes to null0 or you can't have the routing
protocols create a route to null0 or both.
If you can't have any null0 routes at all what are options with regards to
redistributing and summarizing that we can use that do not create routes to
null0.
We have heard one with regards to OSPF in using area x range instead of the
summary address. Does anyone have any others?
MP
----- Original Message -----
From: "Jeongwoo Park" <jpark@wams.com>
To: <ccielab@groupstudy.com>
Sent: Thursday, May 23, 2002 10:36 PM
Subject: Work-around on using null interface
> Hi
> I was wondering what could be equivalent to using null interface.
> I was redistributing ospf route 170.100.100.6/27 into igrp with the
summary
> address of 170.100.100.0/24.
> Once you summary under ospf, it is a must that you should use null
> interface( ip route 170.100.100.0 255.255.255.0 null 0). Since using null
> interface is considered static route, what could be the substitute for
that?
> I tried with distribute-list, but didn't work.
>
> Thanks
>
> JP
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:59:07 GMT-3