9 messages in net.nether.puck.cisco-nsp[c-nsp] MPLS, L2TPv3 Layer 2/3 VPN Ne...
FromSent OnAttachments
Eric KaganJan 4, 2005 6:56 am 
John OsmonJan 4, 2005 11:39 am 
Nick ShahJan 4, 2005 6:41 pm 
choo...@pacific.net.sgJan 4, 2005 9:14 pm 
Nick ShahJan 4, 2005 9:26 pm 
choo...@pacific.net.sgJan 4, 2005 10:02 pm 
Jon LewisJan 4, 2005 10:51 pm 
Oliver Boehmer (oboehmer)Jan 5, 2005 3:15 am 
Chris CappuccioJan 5, 2005 10:15 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[c-nsp] MPLS, L2TPv3 Layer 2/3 VPN Network OptionsActions...
From:Jon Lewis (jle@lewis.org)
Date:Jan 4, 2005 10:51:23 pm
List:net.nether.puck.cisco-nsp

On Wed, 5 Jan 2005, choo@pacific.net.sg wrote:

I'm looking into providing internet access to MPLS/VPN. Has anyone tried to enable internet access on a MPLS/VPN? Any experience to share?

I think the challenge would be how to provide internet access and MPLS/VPN over a same physical link, especially when the vpn is running on non-unique private IP address.

We do MPLSVPN service, and for VPNs where they want internet access for the VPN (most of them), we typically have them use a separate CPE and circuit for the internet connection. In a few cases, where circuit cost has been an issue, we'll do frame over PTP T1 and use one PVC for the main site's VPN connection and another PVC for internet...running NAT on their CPE.

One thing I've been curious about but haven't had the time/gear to lab is whether MPLS VPN (vpnv4 BGP/LDP) will play nice with the "confederation per pop" style of BGP confederations. We're currently a mix of partially meshed and multiple route reflectors, and it's getting to be a bit of a mess to maintain.