In the "Dynamic Layer-3 VPNs (RFC 2547) Support Using Multipoint GRE (mGRE) Tunnels" document, the following statement is made, "For multipoint GRE tunnels, a tunnel key must be configured. Unlike other tunnels, the tunnel destination is optional. However, if the tunnel destination is supplied, it must map to an IP multicast address." I've tried to implement a tunnel with a multicast address as the destination, but the IOS will not allow the assignment. I've tried different methods and approaches, but nothing seemed to work. I've gone through the various RFC documents for GRE and found nothing that would explicately restrict this. Has anyone actually been able to do this? Thanks in advance.
I've already done something similar, but that's not providing the functionality/capability I need. I'm specifically looking for the method to actually use a multicast address for the multipoint tunnel destination.
What's the functionality that you want to use that the multicast destination address will give you ?
It's not a real multicast destination address that you have to put. It's normal that your IOS doesn't permit this. You have to map a NBMA address to your tunnel destination address (mapping). This will allow your broadcast and multicast request to be send to the destination address of your mapping.
The functionality is having an actually multicast address as the destination of the multipoint tunnel--whether mapped or otherwise. The document states "if the tunnel destination is supplied, it must map to an IP multicast address" and this is a Cisco document. The assumption is that I want to "allow ... broadcast and multicast requests (sic) to be sent (sic) to the destination address..." and that is not what I asked--there already exist plenty of examples and instructions on how to do so. The Cisco document states a multicast address could be a tunnel destination but the Cisco IOS is seemingly not allowing this to occur.
So, I ask again "Has anyone actually been able to do this?"
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...