Wissensdatenbank

On OpenWrt, iStoreOS or KWRT, when VilaNet says connected but phones and computers behind the router have no internet: update VilaNet from the official releases page, then open Network > VilaNet and Connect again. If LAN devices still have no internet after that update, turn off software flow offloading and hardware flow offloading, save, and connect once more.

A connected label does not prove LAN traffic uses the tunnel. Open an ordinary HTTPS site on a LAN device and check Overview at the same time.

1. Flow offloading skips the tunnel

A common case: the router itself can use the connection, transparent gateway or transparent proxy shows connected, and devices behind the router have no network or bypass the tunnel. Firewall (fw4) flow offloading sends established LAN connections down a fast path in the kernel, so they never enter the tunnel. iStoreOS turns this on by default.

1. Install the current packages from the releases page or openwrt.vilavpn.com. Steps: install VilaNet on OpenWrt.
2. Connect again. While transparent gateway or transparent proxy is connected, the current packages turn fw4 flow offloading off, and they restore your previous setting when you disconnect.
3. If you manage flow offloading yourself and do not want VilaNet to change it, set vilanet.global.manage_flow_offloading='0' and commit. VilaNet then only warns. If LAN traffic still bypasses the tunnel, turn offloading off yourself.
4. Manual path: open Network > Firewall and turn off Software flow offloading. If Hardware flow offloading is present, turn that off too. Save and apply, then connect VilaNet again.

Transparent proxy also needs the kernel modules kmod-nft-tproxy, kmod-nft-socket and kmod-nft-nat. Install any that are missing, then connect again.

2. LAN dies after you change server

In transparent gateway or transparent proxy, after you switch to another server the status can stay connected while devices behind the router cannot open sites, until you disconnect and connect again. The old tunnel is still being removed while the new one is created, so the tunnel looks up and does not forward.

Update, then switch server. The current packages remove the old path first, then build the new one. If you have not updated yet, disconnect and connect after the switch, or run:

/etc/init.d/vilanet restart

3. Transparent proxy resets, a WAN blip, or an empty server list

For any of the following, install the current packages, open Network > VilaNet, and select Connect:

• Transparent proxy says connected, but LAN connections are reset. The redirect rules exist, and the proxy is not actually listening.
• The LAN worked, then failed by itself after a short WAN drop, a PPPoE redial, or a WAN address renewal. After the update, the package is built to stay up through that blip and to connect again when the WAN returns.
• After an upgrade from a very old configuration, the whole-LAN gateway never starts and the router stays on the old per-device proxy behavior. The update does not overwrite a routing mode you already chose in the interface.
• The account is valid, but the page says No active packages or lists no servers. Update, then connect again.

Transparent proxy handles IPv4 only. When the whole LAN should carry both IPv4 and IPv6, use transparent gateway instead of staying on transparent proxy.

4. Install errors, idle status, or a LAN that drops every few seconds

• If opkg cannot satisfy dependencies, or reports a malformed package: run opkg update, install kmod-tun, and confirm the core package matches the specific architecture with the highest priority in opkg print-architecture.
• If you see a failure to bind TUN, or operation not permitted: the TUN kernel module is missing or not loaded. Run the commands below and reboot the router if needed.
• If connect just reported connected and vilanet status shows idle: restart the service and check the status again.
• If LAN devices drop every few seconds: that is usually the kill-switch interacting with MTU. Look at kill_switch and network under Settings in LuCI, or in /etc/config/vilanet. Do not change a setting you do not recognize. The matching notes are in the troubleshooting section of openwrt.vilavpn.com.

opkg update
opkg install kmod-tun
/etc/init.d/vilanet restart
vilanet status

How to tell it recovered

A LAN device that is not running its own VPN can open an ordinary HTTPS site, and Network > VilaNet > Overview still shows the service running and the connection connected. Both have to be true.

Still not working?

Confirm you installed the current official packages, not the retired installer. See the install steps. Confirm the routing mode is the one you wanted. See the three modes. Open a ticket from the client area with the router model, the OpenWrt version, whether you use opkg or apk, and a redacted vilanet status. Do not attach a password, a raw subscription or a public address.