Messages

[...]Instead, I have an AppleTV4K and a Chromecast
[...]
I have zero trust in any of the smart TV's native operating systems nor the apps that run on them.

Heh. The lesser of two evils? (I imagine your practical choices are limited; I don't pay attention to that class of devices.)

Instead of "Lesser of two evils" I think of it more as a decision made after performing a risk assessment.

Apple has shown to have set a higher bar for security, and Chromecast devices are basically dumb where the casting device is likely a bigger risk.

WebOS used by LG (and who knows what by budget TV brands) are certainly more suspect, and the preloaded apps that come on your smart TV are a revenue source for the TV makers, not unlike the bloat of software that came on your Packard Bell PC bought in the 1990's.

Meyergru is pretty spot on with this.

My best you can do solution here at home is to never connect the "Smart" TV itself to my network.  Instead, I have an AppleTV4K and a Chromecast connected to my big family TV.  The AppleTV4K does everything (and more) better than the TV's native apps.  The Chromecast allows for the simple streaming from one device to another.

I have zero trust in any of the smart TV's native operating systems nor the apps that run on them.

As for the router idea: I think you are mixing up concepts here. If the router really acts as a router and does NAT, OpnSense will not be able to discern between devices behind that router, so no. If it can be repurposed as a switch, then in a sense, yes. However, all devices connected to the switch can interact without OpnSense even interfering.
Rules per device is possible, but then again: how do you even identify a specific device? By IP? By MAC? Good luck with either.

To add on to this, many routers with WiFi can be configured to behave as only a WiFi AP.  Either with it's native firmware or flashed with other firmware.  I was always fond of the Tomato forks (FreshTomato being the most current).  In fact, ASUS routers use a fork of this for their routers.

Once configured as an AP, you can connect it to your network just as any AP, via Ethernet to your LAN.

I still have 2 Clarkdale CPUs and motherboards kicking around here somewhere, if you wish to upgrade.

but I need to get on this as money is about to expire so I need to spend it.

Damn, that sounds like my wife!

I have nearly the same one on my Topton N5105.  Mine is a 120MM version.  Larger fan for less noise and more air flow.  Temps usually stay 36-44C.  I don't do any packet inspection or such.  1Gb WAN and a 2.5Gb LAN that sometimes does move large amounts of data.

Note that when I received the Topton, temps were terrible.  I needed to take it apart, lap the contact pad between the CPU die and the heatsink, and reassemble it with a copper shim and fresh thermal paste.  It would likely keep temps reasonably in spec without the USB fan on top, but I had already bought it, so I keep it sitting on top of the Topton (blowing down onto the heatsink).

https://www.amazon.com/dp/B00G05A2MU

[...] if Mythos was so powerful, how did Claude Code's source code leak?

oops!

More likely a planned "leak".  It went viral, created tons more chatter and attention than if they just released it and asked in a press release "Developers, would you please review this code so you can use it in the future?"  I imagine it was well scrubbed of anything sensitive they wouldn't want released.

I work in semiconductor manufacturing (25+ years now).  The "silicon" you are talking about, CPU/GPU/SoC CMOS logic, has some of the most guarded IP (Intellectual Property) that you can imagine.  The companies offering LLM AI also make semiconductor chips, so there is no way they will ever let AI get a whiff of them.

That said, there is extensive use of computer algorithmic review during all phases of development, manufacturing and test.  Companies such as Cadence Design Systems have been offering tools to the semiconductor industry for decades.

20561 days uptime is roughly 56 years. 2026 minus 56 is 1970.

He's running a very old version.  Worked great on ARPANET.

/*grin*

5HP gain, easy.

What would be the benefit of running memtest86+ if it cannot test all of the installed memory?  Only testing a portion of your memory does not give you any conclusive result.  And avoiding memory used by the system/OS is even less valuable, for this would be the area which you would really wish to know if there is an issue.

I also recently replaced my ISP's cable modem /w a Netgear CM2000 which meets and exceeds the specs of the ISP's modem.

I would start here.  Plug your modem directly into a known good computer and test.

When troubleshooting, I have always been from the school of "What was the last thing changed?"

I'll chime in here as well.  Earlier today I updated from 25.7.10 to 16.1.2_5.  For a long time I've been an advocate of never updating "critical" infrastructure or services with any software that ends in ".0" (or ".1" with OPNsense's revision formatting).  While it is just my home network, there are a number of homelab servers and services, and need to support several users needing it for school and WFH situations.  We all have become very dependent on things working properly in the past half decade.

Kudos to the OPNsense team for a seamless and pain free release.  Also want to recognize and offer a big "Thank you!" to the regulars here on the forum for your willingness to offer you advice and support.

Perhaps :) I read it as "You can accept the baseline so that we don't have to troubleshoot your network."

My post was tongue in cheek.  You are correct, initial troubleshooting should disable any shaping and packet inspection to determine if they are impacting the situation.

[Packet shapers.]

Saw a note under the section "Technologies that aren't recommended with Microsoft Teams":

Packet shapers. Any kind of packet snipper, packet inspection, or packet shaper devices aren't recommended for Teams media traffic and may degrade quality significantly.

Interesting.

You could also read that as Microsoft saying "Don't do anything that prevents us from having complete control of your system..."