Rammbock can move a connection profile in and out of the app using SoftEther
.vpn files and QR codes. That lets you:
- set up a profile once and copy it to another phone,
- share a server with someone else,
- exchange configurations with the SoftEther VPN Client for desktop, which
uses the same
.vpnformat.
All of these live on the configurations screen’s overflow (⋮) menu.
.vpn files
A .vpn file is SoftEther’s standard “connection setting” text file. Rammbock
reads and writes the same format as the desktop client, so files move both ways.
Export to file
- Open a profile’s menu → Export to file.
- Choose where to save the
.vpnfile.
The file contains the host, port, hub, username, connection options, and — for password logins — the stored credential (see What travels below).
Import from file
- On the configurations screen, menu → Import from file (or, on the empty screen, Import .vpn).
- Pick a
.vpnfile. A new profile is added.
If the file isn’t a valid SoftEther .vpn configuration, Rammbock says so rather
than importing something broken.
QR codes
For a quick phone‑to‑phone copy, share a profile as a QR code instead of a file.
Show a QR code
- Open a profile’s menu → Show QR code.
- The other device opens Rammbock and scans it.
⚠️ A QR code can carry saved credentials. If the profile uses a password, that credential is inside the code. Only show it to people you trust — the app warns you of this on the QR screen.
Scan a QR code
- Menu → Scan QR code (or Scan QR on the empty screen).
- Point the camera at the code. The profile is imported.
The scanner accepts Rammbock’s own QR codes and also raw .vpn text encoded in a
code.
What travels in a file
Not every credential can leave the device. Here’s what an export or QR carries:
| Auth method | What’s included |
|---|---|
| Password | Username + the password hash (never the plaintext). |
| RADIUS / NT domain | Username + password (RC4‑obfuscated, as SoftEther stores it). |
| Anonymous | Nothing to carry. |
| Client certificate | Not exported — the private key stays in the system keystore. Re‑select a certificate after importing. |
| Smart card (NFC) | Not exported — the key never leaves the card. Re‑read the card after importing. |
Also carried: server host, port, hub name, parallel‑connection count, and UDP acceleration. See Authentication for more on each method.
When you import a certificate/smart‑card file
If a .vpn file was made with certificate or smart‑card auth, its keys can’t
come along. Rammbock imports the profile as a password profile and shows a
warning telling you to re‑configure certificate or smart‑card auth in the app.
Fix it by editing the profile and choosing the right method — see
Authentication.
Other import warnings you might see:
- “Saved password is missing or malformed — enter it before connecting.”
- “The saved password was erased in this file — enter it before connecting.”
These are non‑fatal: the profile still imports; just fill in the password before you connect.
Compatibility with the desktop client
Because Rammbock uses the genuine SoftEther .vpn grammar:
- A
.vpnyou export from Rammbock can be imported into the SoftEther VPN Client on Windows/macOS/Linux (and edited in a text editor). - A
.vpnexported from the desktop client can be imported into Rammbock.
Certificate/smart‑card credentials still don’t cross over in either direction — those always stay on the device that holds the key.