Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

DMVPN spoke to spoke traffic requirements

I would like some help to clarify DMVPN spoke to spoke traffic requirements.

From http://www.cisco.com/en/US/docs/ios-xml/ios/sec_conn_dmvpn/configuration/xe-3s/sec-conn-dmvpn-dt-spokes-b-nat.html

"

  • If one spoke is behind one NAT device and another different spoke is behind another NAT device, and Peer Address Translation (PAT) is the type of NAT used on both NAT devices, then a session initiated between the two spokes cannot be established.

"

What do they mean by "PEER address translation" ?  Is that the same as Port Address Translation?

Is this referring to a typical home internet cable line, where you have one dynamic public IP from your ISP, and forward udp/500 and udp/4500 (PAT) to a router behind your firewall?

If you could get a business line with a few public IPs for your spoke, and NAT one public IP to one inside IP (static NAT), then spoke to spoke traffic should work?

I have static NAT on my HUB right now  and PAT on two spokes and spoke to spoke traffic always goes through the hub right now.

I've got this config on all routers,

no ip next-hop-self eigrp 1

ip nhrp shortcut

ip nhrp redirect

no ip split-horizon eigrp 1

198
Views
0
Helpful
0
Replies
CreatePlease to create content