[BACKUP FILE SCRIPT] FASTEST BUILD JUANFI PISOWIFI

MIKROTIK PASSWORD:
username: admin
password: juanfi

BACKUP FILE SCRIPT HAPLITE: DOWNLOAD HERE!

BACKUP FILE SCRIPT HEX: DOWNLOAD HERE!

WHAT IS JUANFI PISOWIFI?

    

💻 Decoding the PISO Wi-Fi Ecosystem: An In-Depth Look at JuanFI and MikroTik Integration

The Piso Wi-Fi Vendo business model thrives on providing affordable, coin-based internet access. While hardware like vending machines and access points form the physical infrastructure, the entire system's functionality and profitability rely on sophisticated hotspot management software. JuanFI is a prominent open-source solution specifically designed to address this need, built around the power and flexibility of MikroTik routers.

I. JuanFI: The Open-Source Engine for Wi-Fi Vendo

JuanFI is a free and open-source software platform developed to manage and automate the operations of a Wi-Fi Vendo (coin-operated internet vending) machine. It is not an operating system or a piece of hardware, but rather a customizable system that integrates with a specific brand of networking equipment to handle user authentication, billing, and traffic management.

The Open-Source Advantage

The core mission of JuanFI, as stated by its developer Ivan Julius Alayan, is to increase digital inclusion by rapidly deploying vendo machines in underserved communities. Its open-source nature provides critical advantages:

1. Cost-Effectiveness: It eliminates proprietary licensing fees, significantly lowering the barrier to entry for small entrepreneurs.

2. Community-Driven Development: The code is transparent, allowing developers to audit, improve, and add features based on real-world operational needs and troubleshooting.

3. High Customization: Operators can modify the captive portal's look, feel, and features to better suit their local market or branding.

II. The Technical Marriage: JuanFI and MikroTik

JuanFI's design is intrinsically linked to the MikroTik RouterOS platform. MikroTik routers are highly favored in the PISO Wi-Fi industry due to their affordability, stability, and powerful feature set, particularly their built-in Hotspot Gateway functionality.

How JuanFI Works with MikroTik

JuanFI essentially operates as the billing and control layer that sits on top of the MikroTik's robust networking layer.

1. MikroTik's Role (The Enforcer): The MikroTik router is configured to direct all client traffic to its built-in Hotspot Gateway. It manages the underlying network protocols, traffic shaping, and firewall rules.

2. JuanFI's Role (The Controller): When a user connects to the Wi-Fi, the router directs them to the JuanFI Captive Portal. JuanFI authenticates the user's coin deposit, generates a time-based voucher (or token), and communicates this voucher back to the MikroTik router via its API (Application Programming Interface).

3. Authentication & Billing: The MikroTik uses the voucher generated by JuanFI to grant access for the specific amount of time purchased, automatically cutting off access once the time expires.

This architectural separation allows the operator to leverage the stability of MikroTik for networking while enjoying the flexible, user-friendly interface of JuanFI for customer interaction and billing.

III. Essential Features and Business Optimization

A key differentiator for high-quality hotspot software is the range of features it offers to maximize profitability and user experience. JuanFI provides several critical components:

• Customizable Captive Portal: The login page is fully editable, allowing the vendor to display local promotions, announcements, and clear pricing tiers (e.g., ₱1 for 6 minutes, ₱5 for 30 minutes).

• Bandwidth Management: JuanFI allows operators to define specific speed limits for different pricing tiers (e.g., higher speed for a ₱10 purchase versus a ₱1 purchase), ensuring fair access and preventing network hogging. This is done by manipulating the Simple Queues feature within RouterOS.

• Voucher Generation and Reporting: The system enables the printing or digital generation of vouchers (for non-coin operation) and provides detailed sales reports, tracking daily cash flow, peak usage times, and overall system profitability.

IV. Conclusion: Driving Digital Inclusion

JuanFI represents a significant technological enabler in the Philippine micro-enterprise sector. By leveraging the low-cost, high-performance capabilities of MikroTik and providing a free, adaptable software layer, it empowers small business owners to provide necessary internet access to communities. The system's success is a direct measure of its effectiveness in closing the digital divide by making internet connectivity affordable and ubiquitous.

WHY BACK UP SCRIPT FILE IS IMPORTANT?

I. The Two Pillars of MikroTik Backup

RouterOS offers two primary backup formats, each vital for a complete disaster recovery plan:

1. Binary Backup (.backup): Created using the /system backup save command. This is a complete snapshot of the router's memory, including the device identity, users, passwords, and interface settings. It is the fastest method for a full restore but can generally only be used on the exact same model and RouterOS version of the device.

2. Configuration Export (.rsc): Created using the /export command. This generates a human-readable text file containing the entire configuration as a sequence of executable commands. It is crucial for cross-platform restoration (restoring a configuration onto a different model or version) or for auditing changes in a version control system like Git.

II. Anatomy of an Automated Backup Script (Email Example)

The most robust backup strategy involves a scheduled script that creates both file types and sends them off-site via email. This process requires a few prerequisite configurations and the script itself.

A. Prerequisite: Configure Email Tool

The router must be configured to use an external SMTP server (like Gmail's or your company's) before it can send emails.

/tool e-mail set address=smtp.gmail.com port=587 \
    start-tls=yes from="router@yourdomain.com" \
    user="your_email@gmail.com" password="your-app-password"

B. The Backup and Email Script

This script creates both backup types, names them dynamically, sends them via email, and then deletes the local files (a security best practice).

# 1. Define variables for dynamic naming and recipient
:local sysname [/system identity get name]
:local date [/system clock get date]
:local time [/system clock get time]
:local recipient "admin@yourdomain.com"
:local backupName "$sysname-$date-$time"

# 2. Create the Configuration Export (.rsc)
/export file="$backupName.rsc" show-sensitive
:delay 2s

# 3. Create the Binary Backup (.backup)
/system backup save name="$backupName"
:delay 2s

# 4. Send the backups as attachments
/tool e-mail send \
    to=$recipient \
    subject="MikroTik Backup: $sysname $date" \
    body="Automatic backup from $sysname complete." \
    file="$backupName.rsc,$backupName.backup"

# 5. Clean up local files for security
:delay 5s
/file remove "$backupName.rsc"
/file remove "$backupName.backup"
:log info "Automated backup to email for $sysname completed."

III. Advanced Maintenance and Retention Policy

Leaving old backups on the router's flash memory can exhaust storage space, potentially leading to system instability or preventing future backups. An efficient system requires a cleanup script scheduled to run periodically.

Cleanup Script: Deleting Old Files by Age

A cleanup script identifies files based on the creation timestamp and deletes those older than a specified retention period (e.g., 30 days).

/system script add name="cleanup-backups" policy=ftp,reboot,read,write,policy,test \
    source={
        :local now [/system clock get time]
        :local retention 30d # Time limit to keep files
        
        /file for i from 0 to [ :len [ /file find ] ] - 1 do={
            :local file [/file get $i]
            :local filename [ :tostr [/file get $i name] ]
            
            # Check if file is a backup or .rsc file and is older than retention period
            :if (($filename ~ ".backup" || $filename ~ ".rsc") && \
                ([/system clock get date-time] - [/file get $i creation-time]) > $retention) do={
                /file remove $filename
                :log warning "Removed old backup: $filename"
            }
        }
    }

Scheduling the Automation

The final step is to use the System Scheduler to call the scripts at regular intervals (e.g., daily at a low-traffic time).

/system scheduler add \
    name=Daily-Backup-Job \
    start-time=03:00:00 \
    interval=1d \
    on-event="/system script run backup-email-script-name" \
    policy=ftp,reboot,read,write,policy,test,sniff,sensitive