👍🏻 A decent project.

[hululu1068]

It would be great if it could be supported on OpenWRT and other gateway devices.

It would be ideal if it could be deployed on OpenWRT and other gateway devices.
Additionally, having a sleek graphical monitoring panel would be a plus.

[domcyrus]

Thanks for the suggestion.

I think this is really two separate feature requests:

1. OpenWRT / gateway-device support
2. A graphical/web monitoring panel

For OpenWRT, the first realistic milestone would probably be a tested terminal/headless build or an opkg package for common router targets. RustNet already has static musl Linux builds for some architectures, but OpenWRT needs separate validation because router devices vary a lot by CPU architecture, kernel config, available storage/RAM, and packet-capture permissions.

Could you share a bit more about the target device?

ubus call system board
uname -a
opkg list-installed | grep -E 'libpcap|tcpdump'
df -h
free

Also useful:

• Router model
• OpenWRT version
• CPU architecture (aarch64, armv7, mips, mipsel, etc.)
• Whether you expect to run it over SSH as a terminal UI, or as a background collector
• Whether running as root is acceptable

Some caveats for OpenWRT:

• eBPF/process attribution may be unavailable or limited on many router kernels.
• Landlock and Linux file capabilities may also be unavailable, so the OpenWRT path may need to run as root with a reduced feature set.
• A web/graphical panel is a much larger feature than packaging. It would likely need a separate design: either a headless collector/API mode plus a web UI, or integration with LuCI.

So I would scope this as:

• First: prove RustNet can capture traffic reliably on a real OpenWRT device.
• Then: add an installation/package path.
• Later: consider a web dashboard as a separate feature.