![]() So traffic generated on their side of the VPN always reaches us without issues.ģ)Child SAs are only being negotiated on re-keys, I'm assuming the first time they are created is under the AUTH packet, as per the RFC. The issue is weird and I've isolated the following things:ġ)If the negotiation is triggered on the ASA side, everything works as expected (so, as a workaround, they are bouncing the tunnel on their side, generating traffic to us (if we are the first to generate traffic it won't work) and that's allowing us to connect)Ģ)If we initiate the connection, we are unable to reach the other side of the VPN but, they are able to reach our network. ![]() This VPN is with a third party gateway, a Cisco ASA and we are using IKEv2. After this upgrade, we lost connectivity with one of our VPNs. Last week we upgraded our security gateway from R77.30 to R80.20.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |