| Hi Kings,
Well, I think the reasoning behind it is that the Hub does recognize that NAT is in place, but it doesn't know how many nat actions have been taken place. It only knows that NAT is in place.
So what would happen if PBR is in place, with NAT being different when traffic flows to the Hub or traffic flows to another connection (for example, you have a router with SDSL and ADSL lines, and the SDSL is used for normal hub traffic, and ADSL for internet-access).
If the hub would send the external ip-address back, instead of the spoke, then the spoke-to-spoke would never come up (as the PBR tells to route that specific traffic to spoke 2 via the ADSL connection). So the solution is to forward the NHRP request and let the spoke answer it, traffic being sent to the PBR router, which in turn takes the correct answer..
Hope you can understand the explanation a bit.. But NAT could be different for different destinations, and the only one who knows it, is the NAT device that's in between the spoke and the hub..
HTH
Pieter-Jan On 3 okt 2010, at 11:35, Kingsley Charles wrote: Hi PJ
Agree and read that too and that's because NHRP can't be PATed.
But my question was on the way NHRP request and response are being handled. They are different. As per the 3rd link, the hub doesn't reply to the spoke rather forwards to the other spoke for it to reply. Why is it implemented that way? Since the hub has the NHRP mapping, why can't it just reply?
With regards Kings
On Sun, Oct 3, 2010 at 2:03 PM, Pieter-Jan Nefkens <[email protected]> wrote:
Hi Kings,
If you are running DMVPN phase 3, and two spokes are behind NAT with PAT, then it's basically impossible to have spoke-spoke traffic, so traffic between those spokes is still going through the hub.
If you check the configuration guide (the third link in your mail), under the Restrictions for DMVPN: Dynamic Tunnels between spokes behind a nat device, it also states:
"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."
So if you're on a PAT'ed device, it would be impossible, with NAT (without firewalling on the NAT device) of course, traffic would occur, as the translation is already active..
HTH
Pieter-Jan
PS: Who is going to attend Cisco Live in London in January?
On 3 okt 2010, at 10:08, Kingsley Charles wrote:
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
--- Nefkens Advies Enk 26 4214 DD Vuren The Netherlands
Tel: +31 183 634730
Fax: +31 183 690113 Cell: +31 654 323221
<green.gif> Think before you print.
Think before you print.
|