AWS does asymmetric routing and is the recommended way of doing it, but you should be able to achieve it over the BGP to preferer one tunnel over the other
It's not directly connected to EVE-ng, I did it this way to represent my topology. If you want to use it with eve-ng you need to do port forwarding on you router on port 500 and 4500 coming from the aws IPs
@@techfrapi I'm using same setup to build ipsec tunnel to aws from fortigate firewall using eve-ng lab but tunnel not coming up. I'm using private ip as wan1 in fortigate to form ipsec with aws. How to achive can you help me ?
great work, well explained . Thank you
Glad you liked it
Can you do any example between Azure & Palo Alto, with 2 VPN's IPSec Active/Active with Gateway BGP? Please
why we need additional rule like ike and ipsec, because while we configure the normal site2site , those rule doesn't need it
Which additional rules exactly
This was great men thank you
You're very welcome
Awesome video
Glad you enjoyed it
Thank you so much!
You're welcome!
Excellent thanks!
Thanks
Would you know how to give one tunnel priority over the other? (active/standby) in Palo? I see you configured the tunnel monitor
AWS does asymmetric routing and is the recommended way of doing it, but you should be able to achieve it over the BGP to preferer one tunnel over the other
how did you connect that aws-lan to eve-ng?
It's not directly connected to EVE-ng, I did it this way to represent my topology.
If you want to use it with eve-ng you need to do port forwarding on you router on port 500 and 4500 coming from the aws IPs
@@techfrapi I'm using same setup to build ipsec tunnel to aws from fortigate firewall using eve-ng lab but tunnel not coming up. I'm using private ip as wan1 in fortigate to form ipsec with aws. How to achive can you help me ?
Thank you very much!
You're welcome!