From: Kian Wah Lai (kian_wah_lai@az5.net)
Date: Mon Mar 22 2004 - 07:25:58 GMT-3
Yes.
That solved the problem ;) someone told me that a few minutes after I sent
the email. Anyway, thanks.
And sorry for the missing subject
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of R&S
Groupstudy
Sent: Monday, March 22, 2004 6:15 PM
To: Kian Wah Lai; 'Kian Wah Lai'; ccielab@groupstudy.com
Subject: RE:
secondary address on the wan interface of router2?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Kian Wah Lai
Sent: 21 March 2004 06:43
To: 'Kian Wah Lai'; ccielab@groupstudy.com
Subject: RE:
Didn't know they will remove the image. Basically, there is no interface
using the 170.100.59.0/24 subnet and I have no idea how can I advertise it.
OSPF summary address or area range won't work, static routes are not
allowed...
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Kian
Wah Lai
Sent: Sunday, March 21, 2004 2:16 PM
To: ccielab@groupstudy.com
Subject:
Hi,
I have no idea how to do the 3rd part (no idea how to advertise the route).
I got this from Cisco ASET lab 3 and attached is the diagram.
Configure NAT:
. Configure NAT on R2 such that inside hosts leaving VLAN 2 toward the Frame
Relay cloud will be given
an outside IP address in the range 170.100.59.2 through 170.100.59.4 with a
29-bit netmask. Use list
number 20 for this task.
. Make sure that all possible hosts within the VLAN 2 subnet could be
supported by this NAT
implementation.
. Ensure that the other routers see the VLAN 2 170.100.20.x route as well as
the 170.100.59.0/24
network.
. You may not create a loopback interface or a static route to perform any
NAT tasks.
Regards,
Kian Wah Lai
[GroupStudy removed an attachment of type image/jpeg which had a name of R&S
Lab Guide3.jpg]
This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:43 GMT-3