Set up Lisar on a compatible router with L2TP/IPsec or OpenVPN

Router compatibility preflight

This preparation checklist does not automatically determine or guarantee compatibility. The exact router model, hardware revision, firmware, VPN client mode, available configuration, and current network remain decisive.

1. Record the router manufacturer, exact model, and hardware revision.
2. Record the installed firmware version.
3. Confirm whether VPN client mode is present. VPN server mode alone is insufficient.
4. Record whether an L2TP/IPsec client option is present.
5. Record whether an OpenVPN client or .ovpn import option is present.
6. Identify the broad context: home, small office, travel, customer-provided virtual router, ISP router, mesh, or other.
7. Identify the approximate downstream-device types and count or range.
8. Identify whether the router is under your administration.
9. Note any already-applicable eligible-plan GeoDNS, DNS AdBlock, or Custom Exit requirement.
10. Record only a non-sensitive visible limitation or question.

Choose the compatible protocol path

Start with L2TP/IPsec where the exact router, firmware, configuration, and network make that setup compatible and appropriate. Use OpenVPN where L2TP/IPsec is unavailable, unsupported, or unsuitable. This is a compatibility rule, not a performance or security ranking.

Use only the exact profile-specific server, account, IPsec, credential, and other setup values or the .ovpn file supplied through the Lisar Panel. Do not guess fields, commands, or values or copy them from another profile.

How downstream devices use the connection

After a compatible router is configured as a VPN client, downstream devices use the router's routed connection. They do not need a separate Lisar tunnel or Lisar application on each device.

Test the routed connection, DNS behavior, and required services on the actual network before relying on the setup. If a change fails, restore the previous known configuration and review the router documentation or request compatibility help.

When router setup is useful

Router setup can be useful when multiple devices need to share a network-level VPN path or when a business needs routing behavior at the network edge.

For a company or office scenario, review the Business page before changing production network equipment. This page documents compatibility and setup choices; it does not offer a paid or managed router service.

Prepare a non-sensitive router summary

You may manually select and copy this plain-text template into a first message through the documented Contact page. The Website does not submit, store, score, or determine compatibility from this information.

Router compatibility preflight

Router manufacturer:
Exact router model:
Hardware revision, if shown:
Current firmware version:

VPN client mode shown: Yes / No / Unknown
L2TP/IPsec client option shown: Yes / No / Unknown
OpenVPN client or .ovpn import shown: Yes / No / Unknown

Setup context: Home / Small office / Travel / Customer-provided virtual router / Other
Approximate downstream-device types and count or range:
Router under your administration: Yes / No / Unknown
Relevant eligible-plan behavior, if already applicable: Standard routing / GeoDNS / DNS AdBlock / Custom Exit / None / Unknown
Current non-sensitive question or blocker:

Do not include passwords, verification or recovery codes, private keys, VPN credentials, .ovpn or other profile files, public IP addresses, internal network topology, identity documents, payment secrets, or other sensitive data.