Skip to main content

FPT Cloud Native Firewall v1.2.0

I. Highlights​

FPT Smart Cloud adds VPN Client-to-Site to FPT Cloud Native Firewall (NGFW), part of the FPT Security Platform (FSP), providing secure remote access to VPC resources without running your own VPN server.

With VPN Client-to-Site, FSP Admins create and manage VPN Gateways directly on the portal: choose the VPN type (IPsec or OpenVPN), attach the gateway to a Firewall and its associated subnets, manage the list of allowed users, and issue per-user credentials. All VPN traffic stays within FPT Cloud infrastructure in Vietnam.

Key highlights of this release:

  • Portal-managed VPN Gateways — create, view, reconfigure, and delete gateways per Firewall, with no separate VPN server to run.
  • Two VPN types — IPsec (username/password authentication) and OpenVPN (per-user certificate, .ovpn file).
  • Independent VPN user management — add or remove users and issue per-user credentials in the UI without reprovisioning the gateway.
  • Transparent operational state — the Status badge (Running / Not Running) is separate from the operation icon (processing or failed, with a reason).

II. New Features & Improvements​

1. VPN Gateway Management (New)​

a. Description​

Manage the list of VPN Gateways per Firewall from the VPN Client-to-Site menu. Each Firewall can have up to 20 gateways.

b. Features​

  • VPN Gateway list for the selected Firewall with columns: Gateway Name (with operation icon), VPN Type, Status, Accessible Subnets, Client IP Pool, Created At
  • Operational state Running / Not Running separate from the operation icon (spinner while Creating / Updating / Deleting; failed icon with a reason when an action fails)
  • Search by Gateway Name and Client IP Pool; filter by Status and VPN Type (AND logic)
  • Pagination 10 / 25 / 50 / 100 items per page; default sort Created At Newest First
  • State-based actions: Delete (normal gateway), Retry + Delete (Create failed)
  • Firewall selector keeps context across all VPN screens; limit of 20 gateways per Firewall

2. Create VPN Gateway (New)​

a. Description​

Create a VPN Gateway through a single-page form, provisioned asynchronously by the backend.

b. Features​

  • Choose VPN Type: IPsec (default) or OpenVPN (bound to the gateway, cannot change after creation)
  • Gateway Name: letters / numbers / hyphens / underscores, up to 50 characters, unique within the Firewall
  • Accessible Subnets: checkbox list of subnets associated with the Firewall (with VPC badge), supports Search by CIDR/VPC and Select All
  • Tunnel Mode: Split Tunnel (default) or Full Tunnel, shown as cards, applied to both IPsec and OpenVPN (Split: only traffic to Accessible Subnets through the VPN; Full: all client traffic, including internet, through the VPN)
  • Public Endpoint and Client IP Pool are system-assigned (read-only); Client IP Pool is guaranteed not to overlap subnets or other gateway pools
  • DNS Servers: enter IPv4, up to 2, no duplicates
  • Protocol/port fixed by type (shown as read-only help text): IPsec UDP 500 + 4500; OpenVPN UDP, port assigned by the backend at provision time

3. Gateway Detail & Reconfigure (New)​

a. Description​

The gateway detail screen has two tabs (Details / Users) and lets you view the Network Configuration and reconfigure it in place.

b. Features​

  • The Details tab shows the Network Configuration read-only: Accessible Subnets, Tunnel Mode, Public Endpoint, Client IP Pool, DNS Servers, Protocol/Port
  • Reconfigure (Edit) inline: edit only Accessible Subnets, Tunnel Mode, and DNS Servers; Save reprovisions asynchronously (gateway enters Updating, stays Running)
  • For VPN Type IPsec: the Downloads section provides Download CA Certificate (.crt) (distribute to users for the OS Trusted Root store) and Download Client Config Script (.sh) (vpn_client_to_site.sh, quick client setup on Debian/Ubuntu)
  • The Edit button is available only when the gateway is Active / Update failed / Delete failed

4. Manage VPN Users (New)​

a. Description​

Manage the list of users allowed to connect to the gateway on the Users tab, independent of the gateway lifecycle (no reprovisioning).

b. Features​

  • User table by VPN Type: IPsec (Username / Email / masked Password) · OpenVPN (Username / Email / Client Profile .ovpn)
  • Add User (Username + Email) issues the credential immediately in the UI
  • IPsec: password is shown once (one-time reveal) after Add / Reset Password, with a Copy button; then masked ********
  • OpenVPN: each user has their own .ovpn file (Download); Regenerate issues a new certificate and .ovpn, revoking the old one
  • Delete user independently (with confirmation); the current session is disconnected after the backend applies the change
  • Limit of 100 users per gateway; search by Username/Email; pagination

5. Delete VPN Gateway (New)​

a. Description​

Delete a gateway when it is no longer needed, with two-layer confirmation.

b. Features​

  • Confirmation popup warns that all sessions will be disconnected and all users will lose access
  • Requires typing the exact string delete (lowercase) to enable the Delete button
  • Asynchronous delete (gateway enters Deleting); on failure the gateway is kept with a failed icon to retry

III. Upgrade Notes​

  • Gateway prerequisite: the selected Firewall must have at least one associated subnet — a VPN Gateway can only reach associated subnets.
  • VPN Type is fixed after creation: to switch IPsec ↔ OpenVPN, delete and recreate the gateway.
  • IPsec credential is shown once: the password appears only once on Add / Reset Password — save it immediately. To reissue, use Reset Password.
  • Tunnel Mode: Split Tunnel (default) routes only traffic to Accessible Subnets through the VPN; Full Tunnel routes all client traffic (including internet) through the VPN. Applies to both IPsec and OpenVPN; chosen at creation and changeable on Reconfigure.
  • CA Certificate (IPsec): distribute the CA certificate .crt to users to install into their OS Trusted Root store before connecting.
  • Client Config Script (IPsec): download vpn_client_to_site.sh on the detail screen for quick client setup on Debian/Ubuntu; the user runs sudo ./vpn_client_to_site.sh and enters the username/password from the Users tab.
  • Propagation delay: user changes (Add / Reset / Regenerate / Delete) take a few minutes for the backend to apply.
  • Limits: up to 20 gateways per Firewall and 100 users per gateway.
  • See the VPN Client-to-Site User Guide for detailed step-by-step instructions.