Comments
-
Figure that VPN route should point to Side B internal network and virtual IP has nothing to do with it :)
-
Thank you, Bruce, Nat tule 172.33.5.0/24 to External did the trick. As for IKEv2 VPN client - disabling NAT in FW rule changed nothing, I am going with support on this one. Cheers
-
Thank you all very much, I was able to create a correct tunnel 172.33.5.0/24<>0.0.0.0/0. I can now see traffic going through remote Firebox. This presents me 2 problems: 1. Regardless I can see ping to google.com allowed at remote firebox it doesn't come back . 2. If I log in through VPN IVEv2 to local firebox and try to…
-
When I tried it I lost an ability to log in via VPN IKEAv2 at Firebox A