04-08-2012 03:49 PM - edited 03-04-2019 03:57 PM
Greetings all,
I'm going to be making a change to an existing client's network soon where multicast traffic is used over GRE (no IPSEC) tunnels. The client is adding a new location and is going to have a 10.x.x.x private IP space for the LAN side. The GRE tunnels amongst all sites are 192.168.x.x range.. so I need to NAT out from 10.x.x.x to 192.168.x.x. when sending multicast traffic to the address 225.8.20.x, which all the other sites will be listening for.
So I configured a NAT pool, ip nat inside on the inside interface, ip nat outside on the outside interface, set ip nat inside on the GRE tunnel, and tested it out in GNS3. The NAT is working when I ping from the LAN interface to one of the other Host's tunnel loopback address (can see this via ip packet debugs). However, when attempting to simulate a multicast from the 10.x.x.x LAN to 225.8.20.x, the NAT translation is never taking place. I know this for two reasons:
It seems as if any traffic being sent to that Multicast address is not being NAT'ed. Is there anything special that needs to be done to get hosts to NAT out when sending to Multicast addresses? Thanks!
04-10-2012 08:02 AM
Brian,
As per me you need to configure "ip nat outside" on the GRE tunnel interface as the multicast traffic will be traversing over Inside interface and then on tunnel interface it will get encapsulated. So NAT has to take place before encapsulation happens.
And regarding Natting Multicast traffic, I have personally not implemented it but logically I don't see why it cannot be done, so try configuring "ip nat outside" on tunnel interface and check if that makes any difference or not
Hope it helps
Neeraj
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide