🚀 The Ultimate Speed Guide: Optimizing Your PisoWiFi Vendo (x86 & Raspberry Pi)
Is your PisoWiFi dashboard taking forever to load? Does your system hang for minutes during boot? This guide will walk you through the essential fixes to eliminate "Network Wait" loops, CPU lag, and database sluggishness.
1. Fix the "Network Wait" Loop (The 15-Minute Hang)
By default, Linux waits for every VLAN and interface to be "online" before starting the dashboard. If one link is slow, your whole system hangs. We can fix this by telling the system to continue as soon as your main internet source is ready.
Why a Permanent Override is Necessary
Files in /run/ are temporary and wiped every reboot. To make the 2-second timeout stick, we must use a permanent systemd override.
Create the override directory:
Create and edit the override file:
Paste the following configuration:
(Save and exit by pressing Ctrl+O, Enter, then Ctrl+X).
(Note: Replace eth0 with your actual internet source interface. This prevents the system from hanging while waiting for VLANs or secondary ports.)
Reload and Verify:
2. Disable Boot-Time Update Lag
Ubuntu and Armbian often attempt to download updates the moment they detect an internet connection. This consumes bandwidth and CPU power right when your WiFi portal needs to start.
Run these commands to disable the daily background updates:
3. CPU Optimization for Instant Portal Loading
When running 20–30 VLANs, your CPU (especially on a Pi 4) is managing 30 separate networks. In "ondemand" mode, the CPU slows down to save power, causing a 1-2 second lag when a customer hits the portal. Switching to Performance Mode keeps the CPU ready at all times.
Install the optimization tool:
Set the governor to Performance:
Make it permanent:
4. Weekly Database Maintenance
Keep your sales and voucher data loading instantly by scheduling a weekly database cleanup every Sunday at 3:00 AM.
Open the crontab editor:
Add this line to the bottom:
(Save and exit by pressing Ctrl+O, Enter, then Ctrl+X).
5. The Vendo Master Netplan Guide
Your Netplan configuration is the heart of your network. Using the wrong settings can lead to the dreaded "stuck at 100%" loading error.
1. Locate your Netplan File
The file name varies depending on your hardware, but it is always in the same folder.
To find yours, run: ls /etc/netplan/
2. The Speed Fix Settings
When editing your file (sudo nano /etc/netplan/FILENAME.yaml), apply these specific rules to stop the boot-time delays.
| Setting | Type | Why it is CRITICAL |
| optional: true | Ethernets | Tells Linux: "If no cable is plugged in, don't wait for a handshake." Essential for USB-to-LAN adapters. |
| forward-delay: 0 | Bridges | The "100% Status Fix." Bridges normally wait 30s to "listen" to the network. This opens the gate instantly. |
| stp: false | Bridges | Disables Spanning Tree Protocol. Speeds up the time it takes for a port to go from "Off" to "Active." |
Optimized Template (Copy-Paste Example)
Here is a sample configuration for a setup with a built-in WAN, USB-to-LAN, and VLANs.
wlan0- bridge to 10.0.0.1
vlan8-eth0.8 with ip 8.0.0.1
VLAN22-eth0.22 in bridge to 10.0.0.1
eth1 -usb to lan with ip 20.0.0.1
br0-with ip 10.0.0.1 and members are wlan0 and eth0.22
Pro Tip: Always use sudo netplan try before applying. This gives you 120 seconds to confirm changes before they revert, preventing you from being locked out of your own system!
To save your changes:
sudo netplan try
(If it says "Configuration accepted," press Enter.)
Troubleshooting Checklist
Indentation: Netplan is very picky. Always use 2 spaces for indentation. Never use tabs.
Static IPs: Ensure your eth1 and br0 are set to dhcp4: false if you are assigning them manual IPs like 11.0.0.1 or 20.0.0.1.
Interface Names: On x86, your ports might be named enp1s0 instead of eth0. Check ip link to confirm names before editing Netplan.
6. Fix "Initializing Firewall" Lag (Walled Garden)
If your Walled Garden (unrestricted sites) is too large, the system wastes minutes performing DNS lookups for every domain.
Map Gateway IPs manually:
Open the hosts file: sudo nano /etc/hosts and add these essential IPs to the bottom:
Clean up your Admin Dashboard:
Delete redundant subdomains. Stick to these essentials for the fastest performance:
api.gcash.com / m.gcash.com
gstatic.com / googleapis.com
api.paymongo.com / checkout.paymongo.com
api.xendit.co / checkout.xendit.co
