You need to specify that your next hop is in the global table with the global keyword.
You will also need a route on the global table for your vpn address that specifies the vrf interface as the outgoing interface. --- On Fri, 20/6/08, Garry <[EMAIL PROTECTED]> wrote: From: Garry <[EMAIL PROTECTED]> Subject: [c-nsp] Routing between VRF and non-VRF To: [email protected] Date: Friday, 20 June, 2008, 8:30 AM Maybe I'm missing something here, but what's the "right" way of routing between VRF and non-VRF interfaces? I know that something like this works: ip route vrf MYVRF 0.0.0.0 0.0.0.0 gig1/0 192.168.123.1 Anyway, this requires the data being routed out of the router and towards another one ... I've tried different things to keep the actual transition between VRF and non-VRF on the same router, but have failed, either by the router denying what I tried to put in, or it not working ... docs didn't seem to contain any other info, either, or I didn't find the correct document ... so, what am I missing here? Tnx, -garry _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ __________________________________________________________ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
