By default Rammbock sends all your traffic through the VPN (a full tunnel). Routing modes let you change that — tunnelling only some networks and letting the rest use your normal connection, or the other way around. This is called split tunneling.
Set it in the profile editor under Routing mode. Some modes need an IP / network list that you import.
⚠️ Privacy trade‑off. Any split mode sends some traffic outside the tunnel. That traffic uses your normal connection and can reveal your real IP address and be seen by your provider. Only use a list you trust, and only if you accept that trade‑off. Full tunnel is the safe default.
The routing modes
| Mode | What goes through the VPN | Needs a list? |
|---|---|---|
| Full tunnel (default) | Everything. Safest. | No |
| Only VPN network | Only the VPN’s own subnet; everything else uses your normal connection. | No |
| Full tunnel, exclude list | Everything except the networks in your list — those keep using your normal connection. | Yes |
| List only | Only the networks in your list (plus the VPN subnet); everything else uses your normal connection. | Yes |
| Full tunnel, ban list | Not implemented yet. Treated as full tunnel so nothing leaks. | — |
Which mode do I want?
- Route only specific services through the VPN (e.g. a handful of sites or apps that are geo‑blocked) → List only, with a list of those services’ networks.
- Send everything through the VPN except a few services (e.g. a bank or a local service that dislikes VPNs) → Full tunnel, exclude list.
- Just reach machines on the VPN’s own network and nothing else → Only VPN network.
IP / network lists
A routing list is a plain‑text file, one IP address or network per line:
# comments start with # and are ignored; blank lines too
1.2.3.4/17
1.2.3.4/18
1.2.3.44
1234:1234:1234::/37- Both IPv4 and IPv6 are accepted.
- Entries can be single addresses (
1.2.3.44) or CIDR networks (1.2.3.4/17). - Blank lines and lines starting with
#(or;) are ignored. - The file can be large — very large lists are automatically coarsened (nearby ranges merged) to stay within Android’s route‑table limit, so routing still works even for huge lists.
Importing a list
- Choose a mode that needs a list (List only or Full tunnel, exclude list).
- Under IP / network list, tap Select file (or Replace to swap an existing one) and pick your file.
- The editor shows the filename and how many entries were parsed. If a mode needs a list and none is selected, it warns that the mode won’t take effect.
Where to get lists
The app has a “Where to get routing lists?” link (also the Routing lists info screen) that points to ready‑made sources, including:
- iplist.opencck.org — generates per‑service IP/CIDR lists on demand. A good
fit for List only. Use Format: custom, Type: CIDR, Template:
{data}, add the services you want, enable Raw CIDR and Save as file, then submit. - Russia mobile‑internet whitelist (a GitHub repository) — ranges reachable mostly from inside Russia; a good fit for Full tunnel, exclude list so those services keep using your local connection.
About IPv6
IPv6 entries are supported, but not every SoftEther server routes IPv6. If IPv6 sites stop loading while connected, remove the IPv6 ranges from your list or switch modes.
Interactions with other features
- Kill switch: blocks all traffic when the tunnel is down, including the traffic a split mode sends outside the tunnel — so during a reconnect even bypassing traffic is cut off. See Kill switch & LAN protection.
- TunnelCrack protection: only meaningful in Full tunnel; split modes already let local traffic bypass, so LocalNet leaks remain possible.
- Connection‑quality monitoring: pings the VPN gateway, which a split mode may not route through the tunnel — live latency and fast drop detection can misbehave. See Connection resilience.
The editor surfaces each of these as a non‑blocking note when relevant.