Hello,
I wanted to know if this setup would work correctly in my network.
I have separate VLANs for my main network, guest network, and a WireGuard network. I also have multiple WiFi SSIDs assigned to different VLANs. In addition, I am using qosify for DSCP Markings and AdGuard Home for DNS filtering rules for DNS hijacking etc.
Would there be any interference or conflicts between these services and network segments, or should everything work normally with this setup?
Thank you.
That depends on what you'd like to do.
For traffic monitoring that setup should work.
For rate limiting or internet block...well, most likely it will work too.
I believe you can try it! Feel free to take and test any part of my code, that's an open-source and free for derivatives as well.
While I'm checking that, could you try v1.7.0?
the problem still there
root@proxmox-openwrt:~# logread -f
Fri Jun 19 15:12:32 2026 user.notice trafficctl: 2026-06-19 15:12:32 src=local user=root via=luci action=telegram_config_change target=
Fri Jun 19 15:12:32 2026 user.notice trafficctl-tg: Bot started, chat_id={redacted)
Fri Jun 19 15:12:34 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:34 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:35 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:35 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:36 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:37 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:37 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:38 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:38 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:39 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:39 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:40 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:41 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:41 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:42 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:42 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:43 2026 daemon.err trafficctl-telegram.sh[3697]: sh: out of range
Fri Jun 19 15:12:43 2026 user.notice trafficctl: 2026-06-19 15:12:43 src=local user=root via=luci action=telegram_config_change target=
Fri Jun 19 15:12:43 2026 user.notice trafficctl-tg: Bot started, chat_id={redacted)
Very impressive undertaking.
https://github.com/YusDyr/luci-app-trafficctl/blob/main/luci-app-trafficctl/root/usr/local/bin/trafficctl-telegram.sh#L28-L42 <-- The OpenWrt way is config_load + config_get/config_get_bool with default values.
@YusDyr again, very impressive for the first release.
I wonder if you could switch to using more of the OpenWrt styles instead of your static css file, because in a few themes I've tested outside of bootstrap, some controls or elements of luci-app-trafficctl are invisible or barely visible to the point you can't use them.
Also, the app only scans main LAN/VLAN, I was more interested to monitor devices in IoT VLAN and the app doesn't seem to display those.
Is there any way to see device upload speed?
It would also be useful to shape/rate limit devices on upload & download speed independantly.
Great work!, appreciate it. Feature request: Please! add MAC based whitelisting and bandwidth management also, as good as all of those features.It helps a lot.
fresh install with the required Packages installed
version: OpenWrt 25.12.5 r33051-f5dae5ece4 / LuCI (HEAD detached at 128a7812) branch 26.180.75667~128a781
do apk add --allow-untrusted upload.apk
