A new OpenWrt LuCI application for bandwidth monitoring

timsaya · October 11, 2025, 2:32am

Hello everyone, over the past few months, I have been developing a network traffic monitoring program based on Rust eBPF technology to monitor the network speed of LAN/WAN devices. Not long ago, I discovered this forum and I hope it can bring help to everyone

LuCI Bandix is a network traffic monitoring application for OpenWrt

The main characteristics are as follows

Modern interface UI
Not dependent on iptables and nftables
Automatically obtain the host name from DHCP/DNS (Static Leases)
Support for LAN/WAN speed monitoring
Support for WAN speed limitation
Support device TCP/UDP connection number monitoring
Support APK and IPK
Supports most router architectures

There are still many bugs at present, and we welcome everyone to submit suggestions.

Thank you all

digital-living · October 11, 2025, 9:15pm

I am interested in this and willing but it looks like my router is not supported

GL-inet MT6000

frollic · October 11, 2025, 9:28pm

This conclusion is based on ... ?

digital-living · October 11, 2025, 9:41pm

I looked at the releases page and did not see anything that resembled my router.

I should be looking for filogic or am I wrong

timsaya · October 11, 2025, 9:43pm

I checked the documentation and found that this device is aarch64_cortex-a53 architecture, which is supported, just like my device (cudy tr3000). It may be an environment dependency issue. Have you encountered any problems?

you could download (or ipk file)
截屏2025-10-12 05.43.50

digital-living · October 11, 2025, 9:46pm

Thank you very much, I am not sure why I did not know that I have only had the router for about a year – LOL

timsaya · October 11, 2025, 9:47pm

Haha, you can use cat /etc/os-release to see your device architecture

Crect · October 12, 2025, 12:58am

github.com/timsaya/luci-app-bandix

luci-app-bandix/root/usr/share/bandix/firewall.include

main

#!/bin/sh
# Bandix firewall configuration for OpenWrt 24.10+

# 获取配置
. /lib/functions.sh
config_load 'bandix'
config_get_bool enabled 'general' 'enabled' '0'

[ "$enabled" -eq 0 ] && exit 0

# 检测使用nftables还是iptables
if command -v nft >/dev/null 2>&1; then
    # 使用nftables (OpenWrt 24.10+)
    nft add rule inet fw4 input tcp dport 8686 accept
else
    # 兼容旧版本使用iptables
    iptables -A INPUT -p tcp --dport 8686 -j ACCEPT
fi

Is it intended to make that port reachable from everywhere?

github.com/timsaya/bandix

bandix-ebpf/src/main.rs

main


      
              }
          }
          
          #[inline(always)]
          fn try_bandix(ctx: TcContext) -> Result<i32, ()> {
              let ethhdr: *const EthHdr = ptr_at(&ctx, 0)?;
              let ethhdr_type = unsafe { (*ethhdr).ether_type };
          
              // only handle ipv4
              match ethhdr_type {
                  network_types::eth::EtherType::Ipv4 => {}
                  _ => return Ok(TC_ACT_PIPE),
              }
          
              // get source mac address
              let src_mac = unsafe { (*ethhdr).src_addr };
              let dst_mac = unsafe { (*ethhdr).dst_addr };
          
              // get ipv4 header
              let ipv4hdr: *const Ipv4Hdr = ptr_at(&ctx, EthHdr::LEN)?;
              let data_len = unsafe { u16::from_be_bytes((*ipv4hdr).tot_len) } as u64;

And if support for IPv6 planned? Otherwise it might miss quite a lot of traffic.

Maybe you could capture the stats also based on just MAC address and match that to hosts using DHCP or neighbors

timsaya · October 12, 2025, 1:14am

Yes, actually 127.0.0.1 is sufficient. This script is designed for easy debugging, such as accessing interfaces directly from other devices in the local area network to troubleshoot.

Yes, IPv6 is currently being planned.

timsaya · October 12, 2025, 1:18am

Using DHCP or ARP is not very real-time for device up and down.

Crect · October 12, 2025, 1:21am

What I meant was to collect the stats in eBPF using the ethernet packet instead of IP packet and then in the web interface match the MAC addresses to hosts / IPs by either DHCP or neighbor table because one host might have multiple IP addresses so there might be multiple rows in the interface for the same host otherwise

timsaya · October 12, 2025, 1:30am

Thank you, I understand what you mean. When I was imagining it, it was for ordinary home users, without considering the situation of multiple IPs, VLANs, or other more complex network architectures. I am planning to join IPv6

Crect · October 12, 2025, 1:34am

Yeah but with IPv6 it's pretty normal for one host to have multiple addresses. One from DHCPv6 and even multiple more from SLAAC / Privacy Extensions in different prefixes like ULA, GUA etc.

timsaya · October 12, 2025, 1:41am

Okay, I will carefully consider how to achieve it. thank you