Timeline for Cisco site-to-site vpn multiple subnet route over tunnel
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 25, 2017 at 20:18 | comment | added | Hung Tran |
@Satish The insisde ACL is normal rule allowing traffic from local subnets to reach AWS subnets and ACL-VPN is crypto map ACL for VPN tunnel. They do different things.
|
|
| Oct 25, 2017 at 20:14 | comment | added | Hung Tran | @Satish We often do like this when having multiple local subnets and multiple remote subnets for Site-to-Site VPN between Firewalls. But I am not really sure why that does not properly work with AWS. | |
| Oct 25, 2017 at 19:31 | comment | added | Satish |
Can i do any any in ACL but i think ipsec won't allow that to do
|
|
| Oct 25, 2017 at 19:30 | comment | added | Satish | Did anyone configure site-to-site tunnel with multiple source subnet with single ACL ? it seems only one subnet can be active at the same time, so strange | |
| Oct 25, 2017 at 19:06 | comment | added | Satish |
I have exact same setup i have add multiple subnet in object-group way they explain but still not working, it will bring break ping for 10 network if i ping from 60 network ip, so look like as soon as it see interesting traffic it stop previous one. also why do you have two ACL ? inside and ACL-VPN?
|
|
| Oct 25, 2017 at 8:02 | history | edited | Hung Tran | CC BY-SA 3.0 |
edited body
|
| Oct 25, 2017 at 7:45 | history | edited | Hung Tran | CC BY-SA 3.0 |
added 4 characters in body
|
| Oct 25, 2017 at 7:20 | history | answered | Hung Tran | CC BY-SA 3.0 |