OpenWebif - Update

[el bandido]

The OpenWebif or Webif is a great way to access the enigma2 receiver on the local network or remotely over the Internet. Currently, the Webif works well for a laptop or home computer. If you want to stream something, then a file is presented and you select what you want to open it. This is basically how streaming works on the Webif on the local network using a laptop or home computer.

In a pinch though, it is nice to have Webif capabilities on a smartphone. This is great when you are stuck somewhere, or when you want to listen to music for example while driving. As mentioned earlier, OpenWebif works OK for home computer or laptop but fails on smartphone streaming. Every image I checked had basically the same problem which is streaming fails on Android smartphone. Here is what a failed stream may look like on the Android smartphone:


So we need to modify Webif to work like this:


Claude Code runs inside the computer, so he has access to the files you allow. This makes Claude Code a natural for fixing something like this.
It is important to remember that an AI assistant is only as good as the information it is presented with. Claude Code did a splendid job of sorting and straitening out the mobile Webif problem for Android type phones. So while we are here, we might as well go a bit further with this OpenWebif plugin and add a few more things to it.

Note:
Mobile Internet streaming comes at a risk for the simple reason you are putting a fta receiver out on the Internet where it can be logged into by bots. Extreme care needs to be used when mobile streaming outside of the local network. All you need for examples is to look at the various Internet forums including this one and note the spam that happens by bots and bad actors.

A summary from Claude is attached.

 

[el bandido]

A logging file has been setup to keep track of traffic when Webif is connected to the Internet. Here is a small snippet:

[2025-10-07 14:04:46] ✗ LOGIN FAILED: IP 176.97.210.9, user '' - Attempting authentication
[2025-10-07 14:04:46] ✗ FAILED: FAILED LOGIN from IP 176.97.210.9, user '' (global count in window: 1)
[2025-10-07 14:04:46]   → IP 176.97.210.9 - First failed attempt recorded
[2025-10-07 14:04:46] ✗ LOGIN FAILED: IP 176.97.210.9, user '' - User not found
[2025-10-07 14:10:11] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:10:11] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 1)
[2025-10-07 14:10:11]   → IP 172.56.68.58 - First failed attempt recorded
[2025-10-07 14:10:11] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - User not found
[2025-10-07 14:10:14] ✗ LOGIN FAILED: IP 172.56.68.58, user 'root' - Attempting authentication
[2025-10-07 14:10:14] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user 'root' (global count in window: 2)
[2025-10-07 14:10:14]   → IP 172.56.68.58 - Failed attempt #2 recorded
[2025-10-07 14:10:14] ✗ LOGIN FAILED: IP 172.56.68.58, user 'root' - Root access blocked from external network
[2025-10-07 14:10:24] ✗ LOGIN FAILED: IP 172.56.68.58, user 'root' - Attempting authentication
[2025-10-07 14:10:24]   ⏱ DELAY: Applying 2 second delay for IP 172.56.68.58
[2025-10-07 14:10:26] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user 'root' (global count in window: 3)
[2025-10-07 14:10:26]   → IP 172.56.68.58 - Failed attempt #3 recorded
[2025-10-07 14:10:26] ✗ LOGIN FAILED: IP 172.56.68.58, user 'root' - Root access blocked from external network
[2025-10-07 14:10:26] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:10:26]   ⏱ DELAY: Applying 5 second delay for IP 172.56.68.58
[2025-10-07 14:10:31] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 4)
[2025-10-07 14:10:31]   → IP 172.56.68.58 - Failed attempt #4 recorded
[2025-10-07 14:10:31] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - User not found
[2025-10-07 14:10:42] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:10:42]   ⏱ DELAY: Applying 10 second delay for IP 172.56.68.58
[2025-10-07 14:10:52] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 5)
[2025-10-07 14:10:52]   → IP 172.56.68.58 - Failed attempt #5 recorded
[2025-10-07 14:10:52]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:10:52] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - User not found
[2025-10-07 14:10:56] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:10:56]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 115 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:10:56] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 6)
[2025-10-07 14:10:56]   → IP 172.56.68.58 - Failed attempt #6 recorded
[2025-10-07 14:10:56]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:10:56] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - IP is locked out
[2025-10-07 14:11:11] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:11:11]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 104 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:11:11] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 7)
[2025-10-07 14:11:11]   → IP 172.56.68.58 - Failed attempt #7 recorded
[2025-10-07 14:11:11]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:11:11] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - IP is locked out
[2025-10-07 14:16:07] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:16:07]   ⏱ DELAY: Applying 30 second delay for IP 172.56.68.58
[2025-10-07 14:16:37] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 2)
[2025-10-07 14:16:37]   → IP 172.56.68.58 - Failed attempt #8 recorded
[2025-10-07 14:16:37]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:16:37] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - User not found
[2025-10-07 14:16:37] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:16:37]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:16:37] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 3)
[2025-10-07 14:16:37]   → IP 172.56.68.58 - Failed attempt #9 recorded
[2025-10-07 14:16:37]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:16:37] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - IP is locked out
[2025-10-07 14:16:37] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:16:37]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:16:37] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 4)
[2025-10-07 14:16:37]   → IP 172.56.68.58 - Failed attempt #10 recorded
[2025-10-07 14:16:37]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:16:37] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - IP is locked out
[2025-10-07 14:17:14] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:17:14]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 82 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:17:14] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 5)
[2025-10-07 14:17:14]   → IP 172.56.68.58 - Failed attempt #11 recorded
[2025-10-07 14:17:14]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:17:14] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - IP is locked out
[2025-10-07 14:17:14] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:17:14]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:17:14] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 6)
[2025-10-07 14:17:14]   → IP 172.56.68.58 - Failed attempt #12 recorded
[2025-10-07 14:17:14]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:17:14] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - IP is locked out
[2025-10-07 14:17:15] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:17:15]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:17:15] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 7)
[2025-10-07 14:17:15]   → IP 172.56.68.58 - Failed attempt #13 recorded
[2025-10-07 14:17:15]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:17:15] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - IP is locked out
[2025-10-07 14:17:35] ✗ LOGIN FAILED: IP 172.56.68.58, user 'root' - Attempting authentication
[2025-10-07 14:17:35]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 99 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:17:35] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user 'root' (global count in window: 8)
[2025-10-07 14:17:35]   → IP 172.56.68.58 - Failed attempt #14 recorded
[2025-10-07 14:17:35]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:17:35] ✗ LOGIN FAILED: IP 172.56.68.58, user 'root' - IP is locked out
[2025-10-07 14:17:35] ✗ LOGIN FAILED: IP 172.56.68.58, user 'root' - Attempting authentication
[2025-10-07 14:17:35]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:17:35] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user 'root' (global count in window: 9)
[2025-10-07 14:17:35]   → IP 172.56.68.58 - Failed attempt #15 recorded
[2025-10-07 14:17:35]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:17:35] ✗ LOGIN FAILED: IP 172.56.68.58, user 'root' - IP is locked out
[2025-10-07 14:17:35] ✗ LOGIN FAILED: IP 172.56.68.58, user 'root' - Attempting authentication
[2025-10-07 14:17:35]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:17:35] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user 'root' (global count in window: 10)
[2025-10-07 14:17:35]   → IP 172.56.68.58 - Failed attempt #16 recorded
[2025-10-07 14:17:35]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:17:35] ✗ LOGIN FAILED: IP 172.56.68.58, user 'root' - IP is locked out
[2025-10-07 14:17:44] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:17:44]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 110 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:17:44] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 11)
[2025-10-07 14:17:44]   → IP 172.56.68.58 - Failed attempt #17 recorded
[2025-10-07 14:17:44]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:17:44] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - IP is locked out
[2025-10-07 14:17:45] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - Attempting authentication
[2025-10-07 14:17:45]   🚫 BLOCKED: IP 172.56.68.58 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:17:45] ✗ FAILED: FAILED LOGIN from IP 172.56.68.58, user '' (global count in window: 12)
[2025-10-07 14:17:45]   → IP 172.56.68.58 - Failed attempt #18 recorded
[2025-10-07 14:17:45]   🔒 LOCKOUT: IP 172.56.68.58 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:17:45] ✗ LOGIN FAILED: IP 172.56.68.58, user '' - IP is locked out
[2025-10-07 14:23:17] ✗ LOGIN FAILED: IP 46.30.174.24, user '' - Attempting authentication
[2025-10-07 14:23:17] ✗ FAILED: FAILED LOGIN from IP 46.30.174.24, user '' (global count in window: 1)
[2025-10-07 14:23:17]   → IP 46.30.174.24 - First failed attempt recorded
[2025-10-07 14:23:17] ✗ LOGIN FAILED: IP 46.30.174.24, user '' - User not found
[2025-10-07 14:27:08] ✗ LOGIN FAILED: IP 172.56.68.200, user '' - Attempting authentication
[2025-10-07 14:27:08] ✗ FAILED: FAILED LOGIN from IP 172.56.68.200, user '' (global count in window: 2)
[2025-10-07 14:27:08]   → IP 172.56.68.200 - First failed attempt recorded
[2025-10-07 14:27:08] ✗ LOGIN FAILED: IP 172.56.68.200, user '' - User not found
[2025-10-07 14:27:18] ✗ LOGIN FAILED: IP 172.56.68.200, user 'root' - Attempting authentication
[2025-10-07 14:27:19] ✓ SUCCESS: IP 172.56.68.200, user 'root' - Successful login, cleared 1 failed attempts
[2025-10-07 14:27:19] ✓ LOGIN SUCCESS: IP 172.56.68.200, user 'root'
[2025-10-07 14:27:34] ✗ LOGIN FAILED: IP 204.76.203.219, user '' - Attempting authentication
[2025-10-07 14:27:34] ✗ FAILED: FAILED LOGIN from IP 204.76.203.219, user '' (global count in window: 3)
[2025-10-07 14:27:34]   → IP 204.76.203.219 - First failed attempt recorded
[2025-10-07 14:27:34] ✗ LOGIN FAILED: IP 204.76.203.219, user '' - User not found
[2025-10-07 14:29:07] ✗ LOGIN FAILED: IP 192.168.1.83, user '' - Attempting authentication
[2025-10-07 14:29:07] ✗ FAILED: FAILED LOGIN from IP 192.168.1.83, user '' (global count in window: 3)
[2025-10-07 14:29:07]   → IP 192.168.1.83 - First failed attempt recorded
[2025-10-07 14:29:07] ✗ LOGIN FAILED: IP 192.168.1.83, user '' - User not found
[2025-10-07 14:29:18] ✗ LOGIN FAILED: IP 192.168.1.83, user 'root' - Attempting authentication
[2025-10-07 14:29:18] ✗ FAILED: FAILED LOGIN from IP 192.168.1.83, user 'root' (global count in window: 4)
[2025-10-07 14:29:18]   → IP 192.168.1.83 - Failed attempt #2 recorded
[2025-10-07 14:29:18] ✗ LOGIN FAILED: IP 192.168.1.83, user 'root' - Invalid password
[2025-10-07 14:29:28] ✗ LOGIN FAILED: IP 192.168.1.83, user 'root' - Attempting authentication
[2025-10-07 14:29:28]   ⏱ DELAY: Applying 2 second delay for IP 192.168.1.83
[2025-10-07 14:29:30] ✓ SUCCESS: IP 192.168.1.83, user 'root' - Successful login, cleared 2 failed attempts
[2025-10-07 14:29:30] ✓ LOGIN SUCCESS: IP 192.168.1.83, user 'root'
[2025-10-07 14:29:37] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - Attempting authentication
[2025-10-07 14:29:37] ✗ FAILED: FAILED LOGIN from IP 188.166.233.183, user '' (global count in window: 5)
[2025-10-07 14:29:37]   → IP 188.166.233.183 - First failed attempt recorded
[2025-10-07 14:29:37] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - User not found
[2025-10-07 14:29:37] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - Attempting authentication
[2025-10-07 14:29:37] ✗ FAILED: FAILED LOGIN from IP 188.166.233.183, user '' (global count in window: 6)
[2025-10-07 14:29:37]   → IP 188.166.233.183 - Failed attempt #2 recorded
[2025-10-07 14:29:37] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - User not found
[2025-10-07 14:29:38] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - Attempting authentication
[2025-10-07 14:29:38]   ⏱ DELAY: Applying 2 second delay for IP 188.166.233.183
[2025-10-07 14:29:40] ✗ FAILED: FAILED LOGIN from IP 188.166.233.183, user '' (global count in window: 7)
[2025-10-07 14:29:40]   → IP 188.166.233.183 - Failed attempt #3 recorded
[2025-10-07 14:29:40] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - User not found
[2025-10-07 14:29:41] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - Attempting authentication
[2025-10-07 14:29:41]   ⏱ DELAY: Applying 5 second delay for IP 188.166.233.183
[2025-10-07 14:29:46] ✗ FAILED: FAILED LOGIN from IP 188.166.233.183, user '' (global count in window: 8)
[2025-10-07 14:29:46]   → IP 188.166.233.183 - Failed attempt #4 recorded
[2025-10-07 14:29:46] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - User not found
[2025-10-07 14:29:46] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - Attempting authentication
[2025-10-07 14:29:46]   ⏱ DELAY: Applying 10 second delay for IP 188.166.233.183
[2025-10-07 14:29:56] ✗ FAILED: FAILED LOGIN from IP 188.166.233.183, user '' (global count in window: 9)
[2025-10-07 14:29:56]   → IP 188.166.233.183 - Failed attempt #5 recorded
[2025-10-07 14:29:56]   🔒 LOCKOUT: IP 188.166.233.183 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:29:56] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - User not found
[2025-10-07 14:29:56] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - Attempting authentication
[2025-10-07 14:29:56]   🚫 BLOCKED: IP 188.166.233.183 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:29:56] ✗ FAILED: FAILED LOGIN from IP 188.166.233.183, user '' (global count in window: 10)
[2025-10-07 14:29:56]   → IP 188.166.233.183 - Failed attempt #6 recorded
[2025-10-07 14:29:56]   🔒 LOCKOUT: IP 188.166.233.183 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:29:56] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - IP is locked out
[2025-10-07 14:29:57] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - Attempting authentication
[2025-10-07 14:29:57]   🚫 BLOCKED: IP 188.166.233.183 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:29:57] ✗ FAILED: FAILED LOGIN from IP 188.166.233.183, user '' (global count in window: 11)
[2025-10-07 14:29:57]   → IP 188.166.233.183 - Failed attempt #7 recorded
[2025-10-07 14:29:57]   🔒 LOCKOUT: IP 188.166.233.183 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:29:57] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - IP is locked out
[2025-10-07 14:29:58] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - Attempting authentication
[2025-10-07 14:29:58]   🚫 BLOCKED: IP 188.166.233.183 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:29:58] ✗ FAILED: FAILED LOGIN from IP 188.166.233.183, user '' (global count in window: 12)
[2025-10-07 14:29:58]   → IP 188.166.233.183 - Failed attempt #8 recorded
[2025-10-07 14:29:58]   🔒 LOCKOUT: IP 188.166.233.183 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:29:58] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - IP is locked out
[2025-10-07 14:29:58] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - Attempting authentication
[2025-10-07 14:29:58]   🚫 BLOCKED: IP 188.166.233.183 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 14:29:58] ✗ FAILED: FAILED LOGIN from IP 188.166.233.183, user '' (global count in window: 13)
[2025-10-07 14:29:58]   → IP 188.166.233.183 - Failed attempt #9 recorded
[2025-10-07 14:29:58]   🔒 LOCKOUT: IP 188.166.233.183 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 14:29:58] ✗ LOGIN FAILED: IP 188.166.233.183, user '' - IP is locked out
[2025-10-07 14:31:56] ✗ LOGIN FAILED: IP 172.56.68.200, user 'root' - Attempting authentication
[2025-10-07 14:31:56] ⚠ GLOBAL ATTACK: GLOBAL ATTACK DETECTED - 13 attempts in last 300 seconds
[2025-10-07 14:31:56]   ⏱ DELAY: Global attack mode - applying 10 second delay for IP 172.56.68.200
[2025-10-07 14:32:06] ✓ SUCCESS: IP 172.56.68.200, user 'root' - Successful login (no prior failures)
[2025-10-07 14:32:06] ✓ LOGIN SUCCESS: IP 172.56.68.200, user 'root'
[2025-10-07 14:42:28] ✗ LOGIN FAILED: IP 167.172.221.215, user '' - Attempting authentication
[2025-10-07 14:42:28] ✗ FAILED: FAILED LOGIN from IP 167.172.221.215, user '' (global count in window: 1)
[2025-10-07 14:42:28]   → IP 167.172.221.215 - First failed attempt recorded
[2025-10-07 14:42:28] ✗ LOGIN FAILED: IP 167.172.221.215, user '' - User not found
[2025-10-07 14:50:14] ✗ LOGIN FAILED: IP 172.56.68.200, user '' - Attempting authentication
[2025-10-07 14:50:14] ✗ FAILED: FAILED LOGIN from IP 172.56.68.200, user '' (global count in window: 1)
[2025-10-07 14:50:14]   → IP 172.56.68.200 - First failed attempt recorded
[2025-10-07 14:50:14] ✗ LOGIN FAILED: IP 172.56.68.200, user '' - User not found
[2025-10-07 14:50:14] ✗ LOGIN FAILED: IP 172.56.68.200, user 'root' - Attempting authentication
[2025-10-07 14:50:14] ✓ SUCCESS: IP 172.56.68.200, user 'root' - Successful login, cleared 1 failed attempts
[2025-10-07 14:50:14] ✓ LOGIN SUCCESS: IP 172.56.68.200, user 'root'
[2025-10-07 15:00:23] ✗ LOGIN FAILED: IP 159.223.21.82, user '' - Attempting authentication
[2025-10-07 15:00:23] ✗ FAILED: FAILED LOGIN from IP 159.223.21.82, user '' (global count in window: 1)
[2025-10-07 15:00:23]   → IP 159.223.21.82 - First failed attempt recorded
[2025-10-07 15:00:23] ✗ LOGIN FAILED: IP 159.223.21.82, user '' - User not found
[2025-10-07 15:00:24] ✗ LOGIN FAILED: IP 159.223.21.82, user '' - Attempting authentication
[2025-10-07 15:00:24] ✗ FAILED: FAILED LOGIN from IP 159.223.21.82, user '' (global count in window: 2)
[2025-10-07 15:00:24]   → IP 159.223.21.82 - Failed attempt #2 recorded
[2025-10-07 15:00:24] ✗ LOGIN FAILED: IP 159.223.21.82, user '' - User not found
[2025-10-07 15:00:47] ✗ LOGIN FAILED: IP 195.178.110.15, user '' - Attempting authentication
[2025-10-07 15:00:47] ✗ FAILED: FAILED LOGIN from IP 195.178.110.15, user '' (global count in window: 3)
[2025-10-07 15:00:47]   → IP 195.178.110.15 - First failed attempt recorded
[2025-10-07 15:00:47] ✗ LOGIN FAILED: IP 195.178.110.15, user '' - User not found
[2025-10-07 15:00:50] ✗ LOGIN FAILED: IP 195.178.110.15, user '' - Attempting authentication
[2025-10-07 15:00:50] ✗ FAILED: FAILED LOGIN from IP 195.178.110.15, user '' (global count in window: 4)
[2025-10-07 15:00:50]   → IP 195.178.110.15 - Failed attempt #2 recorded
[2025-10-07 15:00:50] ✗ LOGIN FAILED: IP 195.178.110.15, user '' - User not found
[2025-10-07 15:04:45] ✗ LOGIN FAILED: IP 172.56.69.26, user 'root' - Attempting authentication
[2025-10-07 15:04:46] ✓ SUCCESS: IP 172.56.69.26, user 'root' - Successful login (no prior failures)
[2025-10-07 15:04:46] ✓ LOGIN SUCCESS: IP 172.56.69.26, user 'root'
[2025-10-07 15:21:07] ✗ LOGIN FAILED: IP 172.56.69.200, user 'root' - Attempting authentication
[2025-10-07 15:21:08] ✓ SUCCESS: IP 172.56.69.200, user 'root' - Successful login (no prior failures)
[2025-10-07 15:21:08] ✓ LOGIN SUCCESS: IP 172.56.69.200, user 'root'
[2025-10-07 15:21:08] ✗ LOGIN FAILED: IP 172.56.69.200, user 'root' - Attempting authentication
[2025-10-07 15:21:08] ✓ SUCCESS: IP 172.56.69.200, user 'root' - Successful login (no prior failures)
[2025-10-07 15:21:08] ✓ LOGIN SUCCESS: IP 172.56.69.200, user 'root'
[2025-10-07 15:29:07] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - Attempting authentication
[2025-10-07 15:29:07] ✗ FAILED: FAILED LOGIN from IP 69.164.207.173, user '' (global count in window: 1)
[2025-10-07 15:29:07]   → IP 69.164.207.173 - First failed attempt recorded
[2025-10-07 15:29:07] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - User not found
[2025-10-07 15:29:13] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - Attempting authentication
[2025-10-07 15:29:13] ✗ FAILED: FAILED LOGIN from IP 69.164.207.173, user '' (global count in window: 2)
[2025-10-07 15:29:13]   → IP 69.164.207.173 - Failed attempt #2 recorded
[2025-10-07 15:29:13] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - User not found
[2025-10-07 15:29:14] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - Attempting authentication
[2025-10-07 15:29:14]   ⏱ DELAY: Applying 2 second delay for IP 69.164.207.173
[2025-10-07 15:29:16] ✗ FAILED: FAILED LOGIN from IP 69.164.207.173, user '' (global count in window: 3)
[2025-10-07 15:29:16]   → IP 69.164.207.173 - Failed attempt #3 recorded
[2025-10-07 15:29:16] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - User not found
[2025-10-07 15:29:16] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - Attempting authentication
[2025-10-07 15:29:16]   ⏱ DELAY: Applying 5 second delay for IP 69.164.207.173
[2025-10-07 15:29:21] ✗ FAILED: FAILED LOGIN from IP 69.164.207.173, user '' (global count in window: 4)
[2025-10-07 15:29:21]   → IP 69.164.207.173 - Failed attempt #4 recorded
[2025-10-07 15:29:21] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - User not found
[2025-10-07 15:29:21] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - Attempting authentication
[2025-10-07 15:29:21]   ⏱ DELAY: Applying 10 second delay for IP 69.164.207.173
[2025-10-07 15:29:31] ✗ FAILED: FAILED LOGIN from IP 69.164.207.173, user '' (global count in window: 5)
[2025-10-07 15:29:31]   → IP 69.164.207.173 - Failed attempt #5 recorded
[2025-10-07 15:29:31]   🔒 LOCKOUT: IP 69.164.207.173 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - User not found
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - Attempting authentication
[2025-10-07 15:29:31]   🚫 BLOCKED: IP 69.164.207.173 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 15:29:31] ✗ FAILED: FAILED LOGIN from IP 69.164.207.173, user '' (global count in window: 6)
[2025-10-07 15:29:31]   → IP 69.164.207.173 - Failed attempt #6 recorded
[2025-10-07 15:29:31]   🔒 LOCKOUT: IP 69.164.207.173 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - IP is locked out
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - Attempting authentication
[2025-10-07 15:29:31]   🚫 BLOCKED: IP 69.164.207.173 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 15:29:31] ✗ FAILED: FAILED LOGIN from IP 69.164.207.173, user '' (global count in window: 7)
[2025-10-07 15:29:31]   → IP 69.164.207.173 - Failed attempt #7 recorded
[2025-10-07 15:29:31]   🔒 LOCKOUT: IP 69.164.207.173 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - IP is locked out
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - Attempting authentication
[2025-10-07 15:29:31]   🚫 BLOCKED: IP 69.164.207.173 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 15:29:31] ✗ FAILED: FAILED LOGIN from IP 69.164.207.173, user '' (global count in window: 8)
[2025-10-07 15:29:31]   → IP 69.164.207.173 - Failed attempt #8 recorded
[2025-10-07 15:29:31]   🔒 LOCKOUT: IP 69.164.207.173 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - IP is locked out
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - Attempting authentication
[2025-10-07 15:29:31]   🚫 BLOCKED: IP 69.164.207.173 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 15:29:31] ✗ FAILED: FAILED LOGIN from IP 69.164.207.173, user '' (global count in window: 9)
[2025-10-07 15:29:31]   → IP 69.164.207.173 - Failed attempt #9 recorded
[2025-10-07 15:29:31]   🔒 LOCKOUT: IP 69.164.207.173 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - IP is locked out
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - Attempting authentication
[2025-10-07 15:29:31]   🚫 BLOCKED: IP 69.164.207.173 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 15:29:31] ✗ FAILED: FAILED LOGIN from IP 69.164.207.173, user '' (global count in window: 10)
[2025-10-07 15:29:31]   → IP 69.164.207.173 - Failed attempt #10 recorded
[2025-10-07 15:29:31]   🔒 LOCKOUT: IP 69.164.207.173 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - IP is locked out
[2025-10-07 15:29:31] ✗ LOGIN FAILED: IP 69.164.207.173, user '' - Attempting authentication
[2025-10-07 15:29:31]   🚫 BLOCKED: IP 69.164.207.173 is LOCKED OUT for 119 more seconds - REJECTING IMMEDIATELY
[2025-10-07 15:29:31] ✗ FAILED: FAILED LOGIN from IP 69.164.207.173, user '' (global count in window: 11)
[2025-10-07 15:29:31]   → IP 69.164.207.173 - Failed attempt #11 recorded
[2025-10-07 15:29:31]   🔒 LOCKOUT: IP 69.164.207.173 - LOCKED OUT for 120 seconds (2 minutes)

Take the above log snippet and present it to Claude (not Claude Code) to analyze it:
47 unauthorized login attempts** from **9 distinct malicious IP addresses in roughly ~1 hour 25 minutes.

This is just a small sample of what you will get or be exposed to if you setup OpenWebif to run on the Internet!

 

[el bandido]

Several scenarios or ideas were gone through with the OpenWebif plugin, finally settling on brief waits between unsuccessful login attempts. What is on the server now and what is being built into images starting with 1008 is a 2minute forced wait for 5 failed login attempts. A reboot of the receiver should reset the login attempts. If you have ever watched brute force attacks logs, you will see an amazing amount of login attempts in a period of a few seconds. Forcing seconds of wait time that increases with each failed attempt confuses the bots, and most give up rather easily when a delay is present.

So a partial protection from attackers is the forced, short wait between failed login attempts which should stop rather quickly most brute force attacks. But something better is needed. to compliment the modified OpenWebif that is running over the Internet, a firewall and/or Wireguard needs to be installed. Both of these are available in TNAP 6 images dated 10-06-2025 and later.

 

[el bandido]

OpenWebif log file is stored in /tmp of receiver's files. Efforts are made to consider the logfile size, and keep it less than 1 MB. We do not want log files that continuously grow unchecked. The /tmp folder in the receiver is cleared on a reboot, but log file size considerations are made for receivers that go months without a reboot.

Sample test that shows what happens in a failed login attempt for OpenWebif. Know what your password and login credentials are. Else, you may be locked out for two minutes, which equates to a short ban. This is explained in detail in the attached .md file. This addition gives OpenWebif a slight bit of standalone security from a brute force attack. Creating a decent login password, and not something like "1234" for a password is suggested and highly recommended, especially if you are going to connect on the Internet.

Lockout Test:

[2025-10-09 11:22:14] [SUCCESS] IP 172.56.65.135, user 'root' - Successful login (no prior failures)
[2025-10-09 11:22:27] [SUCCESS] IP 192.168.1.83, user 'root' - Successful login (no prior failures)
[2025-10-09 11:26:10] [FAILED_ATTEMPT] FAILED LOGIN from IP 172.56.65.135, user '' (global count in window: 1)
[2025-10-09 11:26:10]   → IP 172.56.65.135 - First failed attempt recorded
[2025-10-09 11:26:19] [FAILED_ATTEMPT] FAILED LOGIN from IP 172.56.65.135, user 'ttyy' (global count in window: 2)
[2025-10-09 11:26:19]   → IP 172.56.65.135 - Failed attempt #2 recorded
[2025-10-09 11:26:25] [DELAY_PROGRESSIVE] 2 second delay required for IP 172.56.65.135
[2025-10-09 11:26:25] [DELAY_PROGRESSIVE] 2 second delay required for IP 172.56.65.135
[2025-10-09 11:26:27] [FAILED_ATTEMPT] FAILED LOGIN from IP 172.56.65.135, user '6⁶667' (global count in window: 3)
[2025-10-09 11:26:27]   → IP 172.56.65.135 - Failed attempt #3 recorded
[2025-10-09 11:26:27] [FAILED_ATTEMPT] FAILED LOGIN from IP 172.56.65.135, user '6⁶667' (global count in window: 4)
[2025-10-09 11:26:27]   → IP 172.56.65.135 - Failed attempt #4 recorded
[2025-10-09 11:26:38] [DELAY_PROGRESSIVE] 10 second delay required for IP 172.56.65.135
[2025-10-09 11:26:38] [DELAY_PROGRESSIVE] 10 second delay required for IP 172.56.65.135
[2025-10-09 11:26:53] [DELAY_PROGRESSIVE] 10 second delay required for IP 172.56.65.135
[2025-10-09 11:26:53] [FAILED_ATTEMPT] FAILED LOGIN from IP 172.56.65.135, user '6⁶667' (global count in window: 5)
[2025-10-09 11:26:53]   → IP 172.56.65.135 - Failed attempt #5 recorded
[2025-10-09 11:26:53] [LOCKOUT] IP 172.56.65.135 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-09 11:26:53] [FAILED_ATTEMPT] FAILED LOGIN from IP 172.56.65.135, user '' (global count in window: 6)
[2025-10-09 11:26:53]   → IP 172.56.65.135 - Failed attempt #6 recorded
[2025-10-09 11:26:53] [LOCKOUT] IP 172.56.65.135 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-09 11:27:08] [BLOCKED_LOCKOUT] IP 172.56.65.135 is LOCKED OUT for 104 more seconds - REJECTING IMMEDIATELY
[2025-10-09 11:27:08] [FAILED_ATTEMPT] FAILED LOGIN from IP 172.56.65.135, user '6⁶667' (global count in window: 7)
[2025-10-09 11:27:08]   → IP 172.56.65.135 - Failed attempt #7 recorded
[2025-10-09 11:27:08] [LOCKOUT] IP 172.56.65.135 - LOCKED OUT for 120 seconds (2 minutes)
[2025-10-09 11:27:15] [BLOCKED_LOCKOUT] IP 172.56.65.135 is LOCKED OUT for 113 more seconds - REJECTING IMMEDIATELY
[2025-10-09 11:27:20] [BLOCKED_LOCKOUT] IP 172.56.65.135 is LOCKED OUT for 108 more seconds - REJECTING IMMEDIATELY
[2025-10-09 11:27:23] [BLOCKED_LOCKOUT] IP 172.56.65.135 is LOCKED OUT for 104 more seconds - REJECTING IMMEDIATELY
[2025-10-09 11:27:25] [BLOCKED_LOCKOUT] IP 172.56.65.135 is LOCKED OUT for 103 more seconds - REJECTING IMMEDIATELY
[2025-10-09 11:27:25] [BLOCKED_LOCKOUT] IP 172.56.65.135 is LOCKED OUT for 103 more seconds - REJECTING IMMEDIATELY
[2025-10-09 11:27:32] [BLOCKED_LOCKOUT] IP 172.56.65.135 is LOCKED OUT for 96 more seconds - REJECTING IMMEDIATELY
[2025-10-09 11:27:32] [BLOCKED_LOCKOUT] IP 172.56.65.135 is LOCKED OUT for 96 more seconds - REJECTING IMMEDIATELY
[2025-10-09 11:27:38] [BLOCKED_LOCKOUT] IP 172.56.65.135 is LOCKED OUT for 90 more seconds - REJECTING IMMEDIATELY
[2025-10-09 11:27:57] [FAILED_ATTEMPT] FAILED LOGIN from IP 172.56.65.119, user '' (global count in window: 8)
[2025-10-09 11:27:57]   → IP 172.56.65.119 - First failed attempt recorded
[2025-10-09 11:28:04] [SUCCESS_CLEARED] IP 172.56.65.119, user 'root' - Successful login, cleared 1 failed attempts

You get 5 tries. On the 6th wrong password entry, you are treated to a 2 minute wait or a reboot of the receiver.
Final edits to OpenWebif will be in the next image dated today or later.

 

[el bandido]

Look on the Internet and you will see all sorts of things written about streaming, especially 4:2:2 high bitrate channels. Claims of success or failure will vary, and include things like high cpu usage, failed streams, and other just arbitrary reasons as to why one streaming setup worked while another failed. But to a large degree, it just comes down to bits and bytes.

A high bitrate feed will create a pretty decent sized file in a a short period of time. So to successfully stream a high bitrate channel to another device such as computer or smartphone connected to the Internet, you have to consider: A device or program that will properly open and play the feed, The upload capability of the receiver that the stream is coming from, and finally the download capability of the device receiving the stream.

Most streaming attempts of high bitrate feeds probably fail due to network connections. While it is True that you need a player that will play the feed, In all probability, you do not need an exotic computer to stream most fta satellite content. You do need a decent video card, but even that can be fairly low end in price range. The video card should meet or exceed the minimum requirements of the target feed, and this is also true of the video player that is selected.

The most important thing about high bitrate streaming is the connection between the device providing the stream (upload) and the device receiving the stream (download). For an example, let's say you want to stream ABC on 99w c band, and your receiver that will be used to provide the stream is an Octagon SF8008. Since this is a high bitrate stream, the Octagon at minimum will need to be able to upload at a speed of around 11-12 Mbps, and the receiving device will need to be able to download at minimum 11-12 Mbps.

If you look at the streaming conversations that can be found on the Internet, very few (if any) mention the fact that you have to upload and also download at a minimum speed for a successful streaming experience. The exotic conversations about high cpu usage, the computer getting hot...etc may be valid, but they point to other problems and not the actual streaming experience itself which really does not require that much. But what is required has to be very consistent!

 

[el bandido]

After researching what has been written about satellite tv streaming, and the streaming of high bitrate feeds in particular, a lot of people would probably tell you that streaming the high bitrate ABC feeds on 99w to an Android smartphone with a low cpu rating would not work or at minimum, provide an unwatchable feed. Actually it is not that hard to do if you meet the upload and download requirements.

The MPV and VLC players that are found in the Google play store will handle most high bitrate feeds. as long as the upload and download speeds are met. Recent attempts at improving the OpenWebif coding I think have helped in the streaming experience in the TNAP images. And also as a test to simply bypass OpenWebif altogether, a direct link may be used for the desired stream. But again, at the end of the day, it comes to upload and download speeds. You have to have both for a successful streaming experience.

 

[el bandido]

As a test a script was made to watch the high bitrate stream, and flag any discrepancies in network streaming. What is shown below is one of the ABC channels on 99w being streamed to a smartphone over the Internet.

Timestamp                | Buf Warn | TX Rate Mbps | CPU Load | Free RAM MB | Active Conn
-------------------------|----------|--------------|----------|-------------|------------
2025-10-12 19:03:57 |        0 |           12 |    13.42 |             |           1
2025-10-12 19:04:02 |        0 |           12 |    13.47 |             |           1
2025-10-12 19:04:07 |        0 |           12 |    13.43 |             |           1
2025-10-12 19:04:12 |        0 |           11 |    13.40 |             |           1
2025-10-12 19:04:17 |        0 |           12 |    13.36 |             |           1
2025-10-12 19:04:23 |        0 |           12 |    13.33 |             |           1
2025-10-12 19:04:28 |        0 |            3 |    13.31 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:04:33 |        0 |            5 |    13.28 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:04:38 |        0 |           11 |    13.42 |             |           1
2025-10-12 19:04:43 |        0 |           10 |    13.39 |             |           1
2025-10-12 19:04:48 |        0 |           12 |    13.52 |             |           1
2025-10-12 19:04:53 |        0 |           10 |    13.56 |             |           1
2025-10-12 19:04:58 |        0 |           10 |    13.51 |             |           1
2025-10-12 19:05:03 |        0 |            9 |    13.55 |             |           1
2025-10-12 19:05:08 |        0 |            7 |    13.51 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:05:13 |        0 |            4 |    13.46 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:05:18 |        0 |            2 |    13.43 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:05:23 |        0 |            2 |    13.55 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:05:28 |        0 |            0 |    13.59 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:05:33 |        0 |            2 |    13.54 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:05:38 |        0 |            1 |    13.58 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:05:43 |        0 |            5 |    13.53 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:05:48 |        0 |           11 |    13.49 |             |           1
2025-10-12 19:05:54 |        0 |           10 |    13.61 |             |           1
2025-10-12 19:05:59 |        0 |            2 |    13.56 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:06:04 |        0 |            0 |    13.52 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:06:09 |        0 |            0 |    13.56 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:06:14 |        0 |            1 |    13.59 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:06:19 |        0 |            2 |    13.62 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***
2025-10-12 19:06:24 |        0 |            2 |    13.73 |             |           1
*** WARNING: Upload rate dropped below stream requirement! ***

The above log snippet shows a poor network connection for the SF8008 due to a large amount of traffic on its network. The result on the target, which is a cheap Android smartphone is a stream that is broken, with constant start/stops.

This code snippet shows a successful streaming attempt from the Sf8008 over the internet to a smartphone without any glitches or freezes in the received stream:

Timestamp                | Buf Warn | TX Rate Mbps | CPU Load | Free RAM MB | Active Conn
-------------------------|----------|--------------|----------|-------------|------------
2025-10-12 22:27:13 |        0 |           11 |    13.72 |             |           1
2025-10-12 22:27:19 |        0 |           11 |    13.67 |             |           1
2025-10-12 22:27:24 |        0 |           11 |    13.69 |             |           1
2025-10-12 22:27:29 |        0 |           11 |    13.64 |             |           1
2025-10-12 22:27:34 |        0 |           11 |    13.67 |             |           1
2025-10-12 22:27:39 |        0 |           11 |    13.61 |             |           1
2025-10-12 22:27:44 |        0 |           11 |    13.56 |             |           1
2025-10-12 22:27:49 |        0 |           11 |    13.56 |             |           1
2025-10-12 22:27:54 |        0 |           11 |    13.51 |             |           1
2025-10-12 22:27:59 |        0 |           10 |    13.55 |             |           1
2025-10-12 22:28:04 |        0 |           12 |    13.59 |             |           1
2025-10-12 22:28:09 |        0 |           11 |    13.62 |             |           1
2025-10-12 22:28:14 |        0 |           11 |    13.57 |             |           1
2025-10-12 22:28:19 |        0 |           11 |    13.52 |             |           1
2025-10-12 22:28:24 |        0 |           10 |    13.48 |             |           1
2025-10-12 22:28:29 |        0 |           11 |    13.52 |             |           1
2025-10-12 22:28:34 |        0 |           10 |    13.64 |             |           1
2025-10-12 22:28:39 |        0 |           10 |    13.75 |             |           1
2025-10-12 22:28:44 |        0 |           10 |    13.69 |             |           1
2025-10-12 22:28:50 |        0 |           10 |    13.64 |             |           1
2025-10-12 22:28:55 |        0 |           10 |    13.66 |             |           1
2025-10-12 22:29:00 |        0 |           11 |    13.61 |             |           1
2025-10-12 22:29:05 |        0 |           10 |    13.72 |             |           1
2025-10-12 22:29:10 |        0 |           11 |    13.75 |             |           1
2025-10-12 22:29:15 |        0 |           10 |    13.77 |             |           1
2025-10-12 22:29:20 |        0 |           10 |    13.70 |             |           1
2025-10-12 22:29:25 |        0 |           11 |    13.73 |             |           1
2025-10-12 22:29:30 |        0 |           11 |    13.83 |             |           1
2025-10-12 22:29:35 |        0 |           11 |    13.76 |             |           1
2025-10-12 22:29:40 |        0 |           11 |    13.78 |             |           1
2025-10-12 22:29:45 |        0 |           11 |    13.72 |             |           1
2025-10-12 22:29:50 |        0 |           11 |    13.66 |             |           1
2025-10-12 22:29:55 |        0 |           10 |    13.61 |             |           1
2025-10-12 22:30:00 |        0 |           12 |    13.56 |             |           1
2025-10-12 22:30:05 |        0 |           12 |    13.60 |             |           1
2025-10-12 22:30:10 |        0 |           12 |    13.63 |             |           1
2025-10-12 22:30:15 |        0 |           13 |    13.58 |             |           1
2025-10-12 22:30:20 |        0 |           12 |    13.53 |             |           1
2025-10-12 22:30:26 |        0 |           13 |    13.49 |             |           1
2025-10-12 22:30:31 |        0 |           13 |    13.45 |             |           1
2025-10-12 22:30:36 |        0 |           12 |    13.41 |             |           1
2025-10-12 22:30:41 |        0 |           13 |    13.38 |             |           1
2025-10-12 22:30:46 |        0 |           12 |    13.35 |             |           1
2025-10-12 22:30:51 |        0 |           11 |    13.32 |             |           1
2025-10-12 22:30:56 |        0 |           11 |    13.29 |             |           1
2025-10-12 22:31:01 |        0 |           11 |    13.35 |             |           1
2025-10-12 22:31:06 |        0 |           11 |    13.32 |             |           1
2025-10-12 22:31:11 |        0 |           11 |    13.38 |             |           1
2025-10-12 22:31:16 |        0 |           11 |    13.43 |             |           1
2025-10-12 22:31:21 |        0 |           10 |    13.47 |             |           1
2025-10-12 22:31:26 |        0 |           11 |    13.44 |             |           1
2025-10-12 22:31:31 |        0 |           10 |    13.48 |             |           1
2025-10-12 22:31:36 |        0 |            9 |    13.44 |             |           1

So streaming of high bitrate satellite channels is possible if all of the conditions are met for it. I think the main problem is a lot of people do not understand what is needed for a successful streaming experience, and just assume what the problem is. If you know what is required, you can make certain the requirements are met. If you don't know what the requirements are, then you are just guessing.

 

[el bandido]

One thing is certain: FTA receiver manufacturers and resellers LIE about the receiver specs! Just because your receiver is rated to have a fast network connection does not mean it works as advertised. Then other things have to be considered such as wiring, other devices in the system such as routers, and the wireless path (if used). Wireless specs and wireless transfer speeds will almost always be different when compared to a wired system.

Shown below are the results of an Octagon SF8008 with a wired connection that runs through a couple of switches. A roughly 6.5 Gigabyte file of Ubuntu is used because it is of a decent size, and will show a decent average speed.

Transfer (Upload) to a network share on one of the local computers:
32.22 MB/s or about 258 Mbps

Transfer to TNAP webserver (Internet Upload):
1.7 MB/s or about 13.6 Mbps

A recording of the ABC channel was made for one hour and 4 seconds. This represents the streaming target shown in the previous examples of streaming. Its size ended up at some 5 Gigabytes. Result: 1.37 MB/s or 11.0 Mbps

So from these investigations, we can conclude that it would be very marginal for me to stream ABC over the Internet to another device without having some video problems at some point.

Just because your equipment is rated at a high transfer rate Does Not mean that you will actually get it!
My particular system has lots of Ethernet cables along with switches. Any of these can cause transfer problems or slow-downs.
WiFi or Wireless presents its own unique set of challenges.
It does help to understand exactly what your system is capable of by using real files and timing how long they take as shown above.
In my system, I can change to another receiver in the Network and increase the upload speed by 4 times. Just an example to show how much variance you can have.

 

[el bandido]

I run a combination of Windows and Ubuntu Linux computers. Linux is my preference. So how much does VLC use when streaming one of the ABC HEVC channels? The answer is Very little.

Here is one of the computers watching the Monday night football game:


A guy might look at that and say VLC is consuming almost 100 percent cpu. Well...Not so fast. You have to consider all the resources available which are shown at the very top, and you will see the computer is actually idling. VLC Is Not a memory or resource hog in a decent computer that is running correctly.

Here is a screenshot from a different computer today:


Again, if you understand what you are looking at, The computer is idling with VLC running. What VLC is actually streaming is also shown.
It is impossible to know how VLC or other media players effect every computer that is connected to our various FTA systems. All I can tell you is VLC is not a resource hog in my systems, and it works flawlessly within its capabilities on a cheap Android smartphone.

 

[el bandido]

Let's review what we have for security and expand it a bit. I am streaming over the Internet, so I want the connection to OpenWebif to be as secure as possible.
The firewall, which is probably the best piece in multi-layered security is described in detail here: Claude Code Rebuilds Ancient Enigma2 Firewall
Then we have the Brute Force Protection, described earlier in this thread. So now let's look at Login and strengthen it a bit.

By default, a login to OpenWebif is done in root. This in itself is a bit dangerous because the root password for OpenWebif is of course the root password for the receiver. So if ALL defenses fail, and a hacker successfully breaks through, then you could have something somewhere between a small problem to a more larger, complex problem. So how about just changing the login for OpenWebif to a user type login, which will be assigned a dollar sign($) in terminal or telnet as compared to root's pound sign( #). We do this so in the event of a hack, the attacker ends up with user privileges instead of root.

First we need to add the user. I think this has to be done in terminal or telnet. So for an example, we will add the user ted and give him a password.

TNAP 6 sf8008

sf8008 login: root
Password:
root@sf8008:~# adduser ted
New password:
Retype new password:
Added user ted.

passwd: password updated successfully
root@sf8008:~#

Ideally, the username ted would not be used, and something a little more complex will be chosen. And the password should be of decent strength as this level of security is no better than the username and password that is chosen. Next, set the OpenWebif Plugin up to deny root login. And while you are there, it is a good idea to put a password on streaming.

For the moment, it seems disabling root access is only available in http. Really we want to use https, so maybe this can be looked at and added soon? So to recap, we have installed for the moment:
Firewall
Brute Force Protection
User Login instead of root Login.

Using https and a couple more items need to be explored.
For the Ultimate in protection, add Wireguard to it. The idea here is to create Internet streaming and remote for a FTA type receiver that is at least reasonably safe to operate.

Something else to think about:
Having a wireless Local Network can present its own challenges. Just because you are using OpenWebif to stream over the local network wirelessly does not mean you automatically have security from intruders.

 

[el bandido]

Here is a screenshot showing VLC resource usage while streaming ABC on a Windows 11 computer. Think about it a minute....How much computer resource should be needed to play a video??? Here is the answer for this Window's machine: