I am trying to configure a network that is capable of spoke-to-spoke multicast traffic. The end result will be effectively a multicast bridge for multiple seperate networks.
I have read over the "Multicast over IPsec VPN Design Guide" as well as the relevant sections in the "IPsec VPN Design" book and "The Complete Cisco VPN Configuration Guide" book and I am still at a loss.
I am using a Cisco 1841 router as the VPN hub and two (soon to be more) Cisco 1811 router as the VPN spokes.
Currently I am trying to use DMVPN to configure and IPsec VPN system, but if I am reading the "Multicast over IPsec VPN Design Guide" correctly, spoke-to-spoke multicast traffic is not possible. I am refering to the third paragraph in the overview section on page 29 of that PDF.
I have been able to connect both of the spokes to the hub and send unicast traffic from each spoke to the other and to the hub. I have also been able to send IP multicast traffic from the hub (server) to the spokes (clients). However when I configure the system so that spoke A (server) is sending the IP multicast traffic, the hub receives the traffic correctly, but the spoke B only receives the very first multicast packet of the stream from spoke A.
My main question is this, can an IPsec (or other) VPN support spoke-to-spoke mutlicast traffic. And if so, how will I need to configure it.
Any information that you can provide related to this will be very appreciated.
Thanks for the reply. If am reading that link correctly it allows for the encryption of the IP multicast traffic over a network that already supports IP multicast. I am trying to tunnel between private networks that are attached to public links that do not support IP multicast. I will keep reading over that link, but it doesn't seem like it will do the trick. Thanks for the helpful suggestion though.
You read the document correctly; spoke to spoke multicast is not supported on a DMVPN. Essentially the spoke to hub connection (in the recommended implementation) is a GRE tunnel protected by IPSEC. GRE can tunnel multicast as well as unicast. However, when a spoke wants to communicate to a spoke, it retrieves the end point IP address from the hub and then sets up an IPSEC connection. Straight IPSEc cannot tunnel multicast traffic.
If you need spoke to spoke multicast, your best bet would be to set up a point-to-point GRE tunnel. Of course, that doesn't scale well if you'd like to have adhoc multicast between any of your sites (as you'd have to manually create the full mesh -- which is what DMVPN is supposed to solve for us.)
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...