For NAT, sure, it will work, you simply decide to NAT or not NAT based on
destination address ranges. ie. if a packet is going to an intranet
customer, there's no need for the customer to NAT. If a packet is going to
the internet, then NAT is done, and your VRF table for that VPN simply
consists of the global address space allocated to that customer. No big
deal....
On the dial-up part, being that the packets are tunneled from the NAS
(called LAC in L2TP) to the home gateway (called LNS in L2TP), then an IP
packets can be treated within MPLS just like any other conversation can.
Nothing out of the ordinary there. Don't "overthink" the problems. :)
Scott
-----Original Message-----
From: Vinod Anthony Joseph Cherunni [mailto:vac@dsqworld.com]
Sent: Saturday, October 14, 2000 9:16 AM
To: smorris@mentortech.com
Cc: cisco-nsp@puck.nether.net
Subject: RE: [nsp] REG: MPLS VPN route exchange
Hi,
Thanks once again for the help, Regarding the Internet connectivity part,
Let me put down an assumption.
Assume a customer needs corporate Intranet VPN services around the globe
within his enterprise, & he is using an private IP address space such as
"192.168.x.x", Now If he also needs Internet access, for which he would also
want to avail some kind of hosting for which he would require a Valid IP
address space, Now assume he is alloted something like "202.54.7.0". He
would typically start using this address also for all his servers that need
to be on the Internet. In such as case NAT will not help, How would I
provision Internet routes ie how will the VRF table be populated.
On the Dial-up front, I have heard that Dial-up can be used as an access
mechanism to an MPLS network. Assume a corporate user part of an Intranet
VPN on my MPLS network, needs mobile dial-up access, Using L2TP will result
in Tunnel creation / management. Is there any way wherein, MPLS can be used.
Kindly advice
With warm regards,
Vinod.
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:19 EDT