From: kongck (kongck@xxxxxxxxxxxxxx)
Date: Mon Dec 20 1999 - 22:03:09 GMT-3
pay attention to DLSW with NAT,
look at http://www.cisco.com/warp/customer/697/6.html
--- Stanislav Sinyagin <SSinyagin@mtu.ru> wrote:
> Hi all
>
> Here's an untypical scenario I came across during my
> studies, in
> someone's old papers. I implemented it in my test
> lab, and I think
> that would be useful for you too. Who provides the
> best (the easiest,
> the most reliable, the most concise...) solution ?
>
> R4---------R3---------R2
> E0 E0 S0 S0
> DCE
>
> The routers are connected in chain, the actual
> interface types ate
> unneccessary. R2 and R2 run OSPF area 0. R3 acts as
> a NAT gateway. R4
> is in inside NAT area, R2 is the outside network.
>
> In inside NAT area, the hosts have the network
> 10.0.0.0/23.
> They should be seen from the outside as
> 137.1.4.0/23.
> Also R4's loopback, 10.0.4.4, should be seen as
> 137.2.4.4 in the
> outside world.
> The outside world should see in its OSPF the
> 137.1.4.0/23 and
> 137.2.4.4/32 routes, and no route from 10.0.0.0/8
> should be seen in
> the outside OSPF.
>
> R4 should ping and telnet any router in the outside
> world.
> There should be no statics on R4.
>
> Between R4 and R2 loopbacks there should be an DLSW
> link. Also (I
> didn't test it) I think there's no problem of
> installing a tunnel
> between them.
>
> Have fun,
> Stan
>
> --
> Stanislav Sinyagin MTU-Inform, Moscow
> Tel. (+7) (095) 258 7878 Fax (+7) (095) 258 7870
> E-mail: SSinyagin@mtu.ru http://www.mtu.ru
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:59 GMT-3