![]() ![]() In Fireware v12.4 or higher, if you specify IPv6 Addresses as the Gateway Address Family, you must specify IPv6 virtual interface IP addresses. You configure virtual interface IP addresses the same way for either type of BOVPN virtual interface. To configure this type of BOVPN virtual interface, set the Remote Endpoint Type to Cloud or Third-Party Gateway. Fireware supports connections to cloud-based endpoints that support wildcard traffic selectors, for example, Microsoft Azure. You can configure a BOVPN virtual interface between your Firebox and a Cloud VPN or third-party VPN gateway that does not use GRE. To configure this type of BOVPN virtual interface, set the Remote Endpoint Type to Firebox.Ĭloud VPN or third-party gateway without GRE The third-party endpoint must terminate the GRE tunnel, not pass the GRE traffic through the IPSec tunnel. You can configure a BOVPN virtual interface between your Firebox and a third-party VPN endpoint that supports GRE over IPSec. Third-party gateway that supports GRE over IPSec ![]() Fireware supports two types of BOVPN virtual interface connections to third-party VPN endpoints: ![]() You can configure a BOVPN virtual interface between your Firebox and a third-party VPN endpoint. Confirm the IPv4 address is from within the DHCP scope address, in this instance 192.168.16.10.Ĭheck the output of the debug on the ASA, confirm the address assign, in this instance 192.168.16.10, which matches the output above.Virtual Interface IP Addresses for a VPN to a Third-Party Endpoint Login to An圜onnect client, once successfully connected from the CLI of the Windows computer run ipconfig. The screenshot below is from a Microsoft Windows server, with a DHCP scope in the 192.168.16.0/24 network range, as configured on the ASA.įrom the CLI of the ASA turn on debugs debug webvpn anyconnect 255
0 Comments
Leave a Reply. |