在GCP VPN和Cisco ASA之间设置隧道时，真实的问题
我正在尝试与一个基于IKEV2配置的Cisco ASA路由器的客户端设置VPN隧道，并将IPSEC隧道模式作为“基于策略的”。我检查了GCP VPN隧道的日志，并且在验证客户的身份方面存在问题。 GCP Cloud VPN使用客户端的公共IP地址来验证身份，但客户端将FQDN用作验证其身份的标准。 GCP期望从客户端获得IP地址，但取而代之的是获得FQDN，这导致未能设置隧道。另外，我读到GCP Cloud VPN不支持IKEV2 FQDN。是真的吗？是否有人在GCP VPN中使用FQDN来验证IKE身份？客户有严格的要求仅通过FQDN验证身份
I am trying to setup a VPN tunnel with a client who is using the Cisco ASA router based on IKEv2 configuration, with the IPSEC Tunnel mode as 'Policy Based'. I checked the logs of the GCP VPN tunnel and I have issue with verifying the identity of the client. GCP cloud VPN uses the public IP address of the client to verify the identity, but the client instead uses the FQDN as a standard to verify its identity. The GCP expects the IP address from client side, but instead it gets the FQDN, which results in a failure to setup the tunnel. Also, I read that GCP cloud VPN does not support IKEv2 FQDN. Is it true? Has anyone used FQDN in the GCP VPN to verify the IKE identity? The client has a strict requirement to verify the identity only via FQDN
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
GCP Cloud VPN不支持IKEV2 FQDN，公共IP地址用作IKE身份。
GCP Cloud VPN does not support IKEv2 FQDN, the public IP address is used as the IKE identity.