Smart TV Doesn't Connect After Sleeping

[wiimanic]

Hi all!

I've just moved over to using opnSense rather than my consumer router, and every device is happy, outside of my smart TV.
The behaviour I'm seeing is this:

 - Use TV as normal, stream some things, everything is happy.
 - It gets turned off or left for a little while on the screensaver.
 - Come back later, and nothing loads any more.
 - If I leave it a decent chunk of time (2-3 mins) it will eventually catch back up.
 - Alternatively, if I turn the Wifi on the TV off and back on, it seems fine again.

Checking the Firewall at the same time as this slow down is happening, I see logs that look like this:



With the packets having this:



Eventually, at 12:34, so ~4 mins later, it connected to Plex and started loading things (though I've had the same behaviour with Netflix + YouTube).


...All of this could be entirely unrelated, I'm just struggling to find the best way to diagnose this.

Is there something obvious that I should be checking for this, to help diagnose and fix the issue?
I've seen some other posts here suggest setting "Firewall Optimisation" to "conservative" but I've not tested that yet.
It doesn't seem to be a damaging setting to use and I've got more than enough CPU to spare, so should that be my first test?

My Setup:

- OpnSense 25.1.1
- No VLANs etc, DHCP set to give out IPs in the 192.168.0.10 - 200 range.
- No firewall rules or settings changed yet.
- N100, 4 x I226-V Ports, 8GB of RAM, 128 GB NVME. Using an eero Pro 6E for WiFi.
- This is running under Proxmox, with 1 interface for the WAN, the remaining 3 bridged together in Proxmox (1 for WiFi, others not used).
- Only really custom config is AdGuard installed, though as you can see above I've swapped devices to use CloudFlare DNS to rule that out for now.
- I've broadly tried to follow the general guides on this forum for general install practises + under proxmox.

Thanks for any help!

[viragomann]

I've seen some other posts here suggest setting "Firewall Optimisation" to "conservative" but I've not tested that yet.
It doesn't seem to be a damaging setting to use and I've got more than enough CPU to spare, so should that be my first test?

It just increases the state timeout. Hence it would rather take some more of the memory than CPU.

It seems that the connections are timing out. So yes, just try this.

However, I'd expect, that a properly working network device throws old connections on its own, when going to sleep, instead of trying to resume them after.

[wiimanic]

It seems that the connections are timing out. So yes, just try this.

I'll swap to that and test out over the next few days, see if it does fix the issue.

However, I'd expect, that a properly working network device throws old connections on its own, when going to sleep, instead of trying to resume them after.

That was why I was slightly hesitant to just change the setting, in case I'm just papering over a more awkward issue by upping the timeout. Its a ~3 year old Sony TV, so I thought it should be a sensible device, but that may not be the case, or there might be something else that is causing this issue, though it being only for 1 device is a bit odd.

EDIT: Feb 25th

So far...this seems to have fixed the issue. My memory usage barely changed, I guess because we have less than 20 devices in the flat, and the TV hasn't got stuck at all since.