Re: static NAT problem

From: Gert Doering (gert@greenie.muc.de)
Date: Tue Apr 16 2002 - 06:06:01 EDT


Hi,

On Tue, Apr 16, 2002 at 05:36:37PM +0800, Nick wrote:
> Missed out a very important piece of information which I excluded for
> simplicity sake and placed a static entry to Eth0 instead.
[..]
> router ospf 100
> log-adjacency-changes
> area 0.0.0.99 stub
> network 200.100.233.216 0.0.0.7 area 0.0.0.99
> network 200.100.242.160 0.0.0.15 area 0.0.0.99

As the router doesn't *have* an interface in 200.100.242.*, there is
nothing it can announce.

What you can do is two things:

 - ip route 200.100.242.160 255.255.255.240 null0
 - and "redist static subnets"

or put an IP out of that subnet onto the loopback0 (or on loopback1),
and use "network" to get it announced as an internal LSA.

> So checking our route entries on our access router, I only get a /32 for the
> 200.100.242.161 lo0 interface and not the /28 for the 200.100.242.160.
> Obviously *slap on my head*.

:-)

> Any way to work around this? Will it work if I place a /28 static route
> entry in our access router also.

Of course - you only need a way to get to the box in question...

> However because of the OSPF and the backup
> configuration I cannot configure a hard static entry.

... but for that, it might be easier to do one of the above.

gert

-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:41 EDT