OPNsense Forum

English Forums => 23.7 Legacy Series => Topic started by: Pocket_Sevens on October 17, 2023, 09:33:02 pm

Title: Streaming Stuttering after Upagrde to 23.7
Post by: Pocket_Sevens on October 17, 2023, 09:33:02 pm
Good day all.  Just wondering if anyone else has noticed issues with streaming? 

I upgraded to 23.7 and noticed that some streams (Netflix, etc.) that were rock solid before seem to be stuttering (picture freezes, sound glitching).  Just wondering if anyone else has noticed this issue.  I haven't changed my config or my hardware; just wondering if maybe my hardware cannot handle 23.7 or if it's not only me experiencing this.

I'm kind of a noob at this so any assistance would be greatly appreciated.  Thanks.
Title: Re: Streaming Stuttering after Upagrde to 23.7
Post by: newsense on October 17, 2023, 10:07:54 pm
No, it's just you I'm afraid.

You'll need to provide more details to understand what is happening. HW specs and what the configuration looks like would be a good start.

Are there any processes pinning the CPU to 100% ? You can ssh in and use top command
Title: Re: Streaming Stuttering after Upagrde to 23.7
Post by: jmmartj on October 18, 2023, 03:24:22 am
Looks like not just Pocket_Sevens.

Made no changes to my config.  Running a 6-port, all-Intel, i7 w/32Gb of ram & actively cooled.  What has been noticeable are delays (5-10 seconds) when changing channels (in YouTubeTV) or content within other apps (like Netflix, Max, etc).  Tested on latest AppleTV & Nvidia Shield Pro, both wired.  Gig fiber up/down to the house.

SSH'd in, CPU does not go past 0.05%

Any advice/thoughts would be appreciated!   :)


Title: Re: Streaming Stuttering after Upagrde to 23.7
Post by: dMopp on October 18, 2023, 09:23:38 am
Have the same since latest update. And Wireguard also has problems (connected but routes are fckd up)

Restarting opnsense and fine for a while. Incant observe any spikes etc.
Title: Re: Streaming Stuttering after Upagrde to 23.7
Post by: jmmartj on October 20, 2023, 10:19:42 pm
Issue 'self-healed'.
Was a packet dropping issue by the local ISP, here in Southern California, USA.
Only affected Frontier & any Google services...
 ::)