Complete implementation of Media Flow module for real-time detection and
monitoring of streaming services with quality estimation and alerts.
Features:
---------
1. Streaming Service Detection
- Video: Netflix, YouTube, Disney+, Prime Video, Twitch, HBO, Hulu, Vimeo
- Audio: Spotify, Apple Music, Deezer, SoundCloud, Tidal, Pandora
- Visio: Zoom, Teams, Google Meet, Discord, Skype, WebEx
2. Quality Estimation
- SD (< 1 Mbps), HD (1-3 Mbps), FHD (3-8 Mbps), 4K (> 8 Mbps)
- Based on real-time bandwidth analysis
3. Real-time Monitoring
- Active streams dashboard with 5-second auto-refresh
- Bandwidth consumption per stream
- Client IP tracking
- Service categorization (video/audio/visio)
4. Historical Data
- Session history with timestamps
- Usage statistics per service
- Usage statistics per client
- Configurable retention (last 1000 entries)
5. Configurable Alerts
- Service-specific usage thresholds
- Actions: notify, limit, block
- UCI-based alert configuration
RPCD Backend:
-------------
Script: root/usr/libexec/rpcd/luci.media-flow
Methods implemented:
- status: Module status and netifyd integration check
- get_active_streams: Currently active streaming sessions
- get_stream_history: Historical sessions (configurable timeframe)
- get_stats_by_service: Aggregated stats per service
- get_stats_by_client: Aggregated stats per client IP
- get_service_details: Detailed info for specific service
- set_alert: Configure usage alerts
- list_alerts: List all configured alerts
Integration with netifyd DPI for application detection.
Views:
------
1. dashboard.js - Main overview with active streams and service stats
2. services.js - Detailed per-service statistics and details modal
3. clients.js - Per-client streaming activity
4. history.js - Chronological session list with filters
5. alerts.js - Alert configuration interface
All views follow naming conventions:
- Menu paths match view file locations (media-flow/*)
- RPC object: 'luci.media-flow' matches RPCD script name
- All views use 'use strict'
- All RPC methods exist in RPCD implementation
Files Structure:
----------------
✓ Makefile: Complete with all required fields
✓ RPCD: luci.media-flow (matches ubus object)
✓ ACL: All 8 RPCD methods covered (read/write separated)
✓ Menu: 5 views with correct paths
✓ Views: All menu paths have corresponding .js files
✓ UCI Config: media_flow with global settings and alerts
✓ README: Complete documentation with API reference
Validation:
-----------
✓ RPCD script name matches ubus object (luci.media-flow)
✓ Menu paths match view file locations
✓ ACL permissions cover all RPCD methods
✓ RPCD script is executable
✓ JSON files have valid syntax
✓ All views use strict mode
✓ RPC method calls match RPCD implementations
Dependencies:
-------------
- netifyd: Deep Packet Inspection for application detection
- luci-app-netifyd-dashboard: Integration with Netifyd dashboard
- jq: JSON processing for historical data aggregation
Usage:
------
# View status
ubus call luci.media-flow status
# Get active streaming sessions
ubus call luci.media-flow get_active_streams
# Get 24h history
ubus call luci.media-flow get_stream_history '{"hours": 24}'
# Set alert for Netflix
ubus call luci.media-flow set_alert '{"service": "Netflix", "threshold_hours": 4, "action": "notify"}'
Data Storage:
-------------
- History: /tmp/media-flow-history.json (last 1000 entries)
- Stats: /tmp/media-flow-stats/ (aggregated data)
- Alerts: /etc/config/media_flow (UCI persistence)
All data stored locally, no external telemetry.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
5.3 KiB
5.3 KiB
LuCI Media Flow - Streaming Detection & Monitoring
Real-time detection and monitoring of streaming services with quality estimation and configurable alerts.
Features
Streaming Service Detection
Automatically detects and monitors:
Video Streaming:
- Netflix, YouTube, Disney+, Prime Video, Twitch
- HBO, Hulu, Vimeo
Audio Streaming:
- Spotify, Apple Music, Deezer
- SoundCloud, Tidal, Pandora
Video Conferencing:
- Zoom, Microsoft Teams, Google Meet
- Discord, Skype, WebEx
Quality Estimation
Estimates streaming quality based on bandwidth consumption:
- SD (Standard Definition): < 1 Mbps
- HD (High Definition): 1-3 Mbps
- FHD (Full HD 1080p): 3-8 Mbps
- 4K (Ultra HD): > 8 Mbps
Real-time Monitoring
- Active streams dashboard with live updates
- Bandwidth consumption per stream
- Client IP tracking
- Service categorization (video/audio/visio)
Historical Data
- Session history with timestamps
- Usage statistics per service
- Usage statistics per client
- Configurable retention period
Alerts
Configure alerts based on:
- Service-specific usage thresholds
- Daily/weekly limits
- Automatic actions (notify, limit, block)
Dependencies
- netifyd: Deep Packet Inspection engine for application detection
- luci-app-netifyd-dashboard: Netifyd integration for OpenWrt
- jq: JSON processing (for historical data)
Installation
opkg update
opkg install luci-app-media-flow
/etc/init.d/rpcd restart
/etc/init.d/uhttpd restart
Configuration
UCI Configuration
File: /etc/config/media_flow
config global 'global'
option enabled '1'
option history_retention '7' # Days to keep history
option refresh_interval '5' # Seconds between updates
config alert 'netflix_limit'
option service 'Netflix'
option threshold_hours '4' # Hours per day
option action 'notify' # notify|limit|block
option enabled '1'
Adding Alerts
Via LuCI:
- Navigate to Monitoring → Media Flow → Alerts
- Click "Add"
- Configure service name, threshold, and action
- Save & Apply
Via CLI:
uci set media_flow.youtube_alert=alert
uci set media_flow.youtube_alert.service='YouTube'
uci set media_flow.youtube_alert.threshold_hours='3'
uci set media_flow.youtube_alert.action='notify'
uci set media_flow.youtube_alert.enabled='1'
uci commit media_flow
ubus API
Methods
# Get module status
ubus call luci.media-flow status
# Get active streaming sessions
ubus call luci.media-flow get_active_streams
# Get historical data (last 24 hours)
ubus call luci.media-flow get_stream_history '{"hours": 24}'
# Get statistics by service
ubus call luci.media-flow get_stats_by_service
# Get statistics by client
ubus call luci.media-flow get_stats_by_client
# Get details for specific service
ubus call luci.media-flow get_service_details '{"service": "Netflix"}'
# Set alert
ubus call luci.media-flow set_alert '{"service": "Netflix", "threshold_hours": 4, "action": "notify"}'
# List configured alerts
ubus call luci.media-flow list_alerts
Data Storage
History File
- Location:
/tmp/media-flow-history.json - Format: JSON array of session entries
- Retention: Last 1000 entries
- Rotates automatically
Statistics Cache
- Location:
/tmp/media-flow-stats/ - Aggregated statistics per service/client
- Updates every refresh interval
How It Works
- Detection: Integrates with netifyd DPI engine to detect application protocols
- Classification: Matches detected applications against streaming service patterns
- Quality Estimation: Analyzes bandwidth consumption to estimate stream quality
- Recording: Saves session data to history for analysis
- Alerting: Monitors usage against configured thresholds
Dashboard Views
Main Dashboard
- Current streaming status
- Active streams with quality indicators
- Top services by usage
- Auto-refresh every 5 seconds
Services View
- Detailed statistics per service
- Total sessions, duration, bandwidth
- Service details modal
Clients View
- Usage statistics per client IP
- Top service per client
- Total consumption
History View
- Chronological session list
- Filter by time period
- Quality and duration indicators
Alerts View
- Configure service-based alerts
- Set thresholds and actions
- Enable/disable alerts
Troubleshooting
No streams detected
-
Check netifyd is running:
/etc/init.d/netifyd status -
Verify netifyd configuration:
uci show netifyd -
Check netifyd flows:
ubus call luci.netifyd-dashboard get_flows
Quality estimation inaccurate
Quality estimation is based on instantaneous bandwidth and may not reflect actual stream quality. Factors:
- Adaptive bitrate streaming
- Network congestion
- Multiple concurrent streams
History not saving
-
Check permissions:
ls -la /tmp/media-flow-history.json -
Check jq availability:
which jq opkg install jq
Performance
- CPU Usage: Minimal (parsing only, netifyd does DPI)
- Memory: ~2-5 MB for history storage
- Disk: None (tmpfs)
- Network: No additional overhead
Privacy
- All data stored locally on device
- No external telemetry or reporting
- History can be disabled or purged anytime
License
Apache-2.0
Author
CyberMind.fr