MikroTik Install Script Guide
The current LucidView MikroTik install path is intentionally simple. Use the portal entry point to log in, view the Portal Demo or create an account, then download the current company install script and run it on supported MikroTik routers in the fleet.
A LucidView Enforcer is a supported MikroTik router with the LucidView scripts installed.
Use the current portal script path rather than old profile-specific installer screenshots or archived instructions.
Downloading the Current Company Install Script
Use the current portal entry point. The public website should not send new users through older profile-specific installer pages.
Open the portal entry point.
Go to portal.lucidview.net.
Create the account from the email link.
A prospective reseller, ISP, WISP, MSP, MikroTik administrator or business can create an account without upfront payment. Use the email-based flow, open the email link, then enter the company name when prompted.
If your email has access to more than one LucidView area, the email can contain the relevant links.
Download the company install script.
Download the current LucidView fleet/company install script for the company or operator account.
Keep the downloaded script available for the rollout.
Run that script on the supported MikroTik routers that should start reporting as LucidView Enforcers. The same company script can be used across supported MikroTiks in that fleet.
LucidView normally bills month to month at the end of the month for chargeable use under the public pricing terms, with the 30-day full-service free trial period and fair use applying.
Applying the LucidView Script to Your MikroTik Router
Connecting to the MikroTik Router
Download Winbox.
Winbox is a utility used to configure MikroTiks. Download the latest version from:
mikrotik.com/downloadRun the application.
Double-click the application to run it. Windows may ask for permission to run the program.
Connect the MikroTik to your ethernet port.
Connecting with either the MAC address or IP address is acceptable. The Winbox application will discover the MikroTik automatically — if not shown, give it a few seconds or manually enter the IP address and credentials.
Click on the MAC address to populate the Connect To field. Use the correct login credentials for your MikroTik.
Click Connect.
Once successfully connected, the MikroTik configuration interface will open.
Uploading the Configuration Script
Click on the Files menu icon.
You may see a few existing files listed in the Files view.
Click Upload and upload the install script.
Upload the current company install script downloaded from the LucidView portal.
Click on New Terminal.
Open a new terminal from the MikroTik configuration interface.
Running the LucidView Script
Confirm RouterOS is supported.
The LucidView MikroTik script is designed for supported stable RouterOS releases. Old releases may need a controlled upgrade plan before installation.
Run the script after reboot.
Once the MikroTik has rebooted, open a terminal and run:
/import current-company-install-script.rsc(Use the filename you downloaded earlier.) Press enter and observe the screen for any errors. If errors occur, please contact us.
If no errors are observed, the MikroTik should be configured and ready. Log on to the LucidView portal and confirm the device shows as Online.
Please allow up to 15 minutes after running the script before checking online status.
If LucidView Is Already Installed
Running the current company install script on a MikroTik that already has LucidView installed acts as the uninstall path. This is useful for old LucidView Enforcers.
To refresh an old Enforcer, run the current company script once to remove the old LucidView installation, then run it a second time to install the latest LucidView version.
How LucidView Traffic Flows
The install creates an L2TP client connection from the MikroTik to a LucidView POP. LucidView has regional POPs in South Africa, the United Kingdom, the United States and Australia. On initial install, the Enforcer first connects to red-box.lucidview.net and can land on any POP. Within about 10 minutes, LucidView should move it to the closest/best regional POP for fast DNS.
LucidView uses 1.1.1.1 as the DNS service target on the MikroTik. When the L2TP route to LucidView is up, DNS sent to 1.1.1.1 is routed over the LucidView path and LucidView applies content filtering. MikroTik Traffic Flow / NetFlow metadata is also sent over the LucidView path so reports, dashboard views, Traffic Flow Analyser, policy updates and support visibility can work.
If the LucidView POP or tunnel is unavailable, the Enforcer fails open to public DNS instead of blocking the customer's internet. In fail-open mode, internet access should continue but LucidView DNS content filtering is not applied until the LucidView path recovers.
For ISPs, WISPs and MSPs, this DNS path control can help keep large-platform traffic on local or regional CDN caches. If devices bypass the ISP DNS path with international DNS-over-HTTPS or other external resolvers, services such as Google, YouTube and Facebook may choose international cache paths, using expensive international bandwidth and giving customers a worse experience. LucidView can block known DNS-over-HTTPS, private DNS and alternate DNS circumvention where configured.
LucidView performs its own classifications using cloud intelligence, DNS metadata, MikroTik Traffic Flow / NetFlow metadata, category data, risk signals and network behaviour. Those classifications power the Firewall Content Filter, reports, Traffic Flow Analyser and effective Behaviour-Based IPS-Style Protection.
Normal RouterOS Schedules
After installation, a normal LucidView Enforcer creates three primary RouterOS schedules:
lvcloud_profiles - every 4 minutes
Runs lvcloud_update to keep firewall content-filter policy, profile instructions and operator/ISP policy current.
vpn_dns_failover - every 1 hour
Checks whether the LucidView lvcloud tunnel is running and moves to failover if the local LucidView POP path is unavailable. In failover, the Enforcer fails open to public DNS: internet access should continue, but LucidView DNS content filtering is not applied until recovery.
enforcer_checkin - every 12 hours
Fetches and imports the current public enforcer_checkin.rsc runtime so LucidView can refresh scripts and release normal Enforcer updates.
Special Cases
VLANs
If there are VLANs on your MikroTik, consider adding an intercept per VLAN to direct incoming DNS requests to the IP address of the MikroTik in that VLAN.
For example, if you have a VLAN called VLAN1 with the MikroTik IP configured as 10.31.0.1, add two rules — one for TCP and one for UDP — with the destination NAT action pointing to that IP address.
Two rules are required for every VLAN: one for TCP and one for UDP. Both are necessary for DNS to work correctly. This is also described in more technical detail in the actual script supplied by the LucidView portal. Please contact us if you need assistance.
Testing the MikroTik
Check connectivity from the LucidView Portal.
Click on the installed MikroTik's LucidView ID in the Portal (this can take up to 15 minutes). You will be directed to your Device Status — confirm it shows Online.
Confirm netflow data is being received.
Open the router profile to configure the Content Filter, IPS, Saturation Manager, Scheduled Reports, Dashboard Views and Traffic Flow Analyser.
Enforcer Technical Checklist
Download the PDF technical checklist for reference during setup.
