It seems like some of the more challenging things to do on an ASA involve some sort of traffic being redirected out the same interface it was received on. This article addresses the requirement for spoke to hub to spoke communication for LAN to LAN VPNs. This is less efficient and should not be used when there are massive amounts of traffic between to spokes. However if your design requires fewer peers, a more compact configuration and you prefer a simple solution, this article can help you achieve those goals. Although this article specifically addresses the LAN to LAN VPN type, the methods used here can work with other types of VPNs as well (e.g. Anyconnect and IPSec Remote Access).
Popular Posts
Live Tweets
- I use an HP5650b ProBook with W7 Premium. Keyboard acts strange (even after replacing). Like left shift, alt,... http://t.co/JKg1uuiv 1 day ago
- Just reminding everyone--what it means to be a CCIE @networkingnerd http://t.co/PNgKBdBR 3 days ago
- If you struggle with the concept of BGP Synchronization, this video may help. http://t.co/n9iceMQn 4 days ago
- ASA L2L VPN Spoke to Spoke Communication http://t.co/1SGloGPO 4 days ago
- Heard these words of wisdom today--"If you're not going to help, at least don't be a hindrance" 5 days ago
-
Recent Posts
Recent Comments
- Paul Stewart, CCIE 26009 (Security) on ASA VPN with Address Overlap
- Jim Thornton on ASA VPN with Address Overlap
- Paul Stewart, CCIE 26009 (Security) on No SSH After Upgrading to 8.4
- Shoaib Merchant on No SSH After Upgrading to 8.4
- Paul Stewart, CCIE 26009 (Security) on Egress Interface Selection on the Cisco ASA



