For wifi7 on the 6ghz band, the ssid has to be wpa3 encrypted, so that’s not going to play nicely on the same ssid as wifi5 wpa2 radios. I would have the wifi7 radio broadcast a unique ‘performance’ network, leave it’s 5ghz on but let it have unii3 on its own and restrict the wifi5 network to unii 1/2 channels.
Ubiquiti is probably your best bet for ‘cheap’ wifi7. As far as mix and match, the short answer is it’s bad.
The long answer is that for anywhere the cells overlap you’re going to have degraded performance at or near wifi5 speeds, which really means wifi4 speeds on 2.4ghz. You’re right that this is mitigated by careful channel planning but once you’re past 4 APs within earshot of each other you’ll run out of 40mhz channels unless you’re in a place where the dfs bands aren’t problematic.
If you are looking for performance improvements, ditching the wifi 5 in favor of wifi6 will be as big or bigger of a jump than 6 to 7 off the 6ghz band.
It will probably just define ‘significant’ as ‘using tools other than Gemini’
Other software has similar behavior and this could do the same thing for, conceivably, all of them.
I could see a world where I would run something like this every 5 years and be surprised how much crap just accumulated over that time.
To the best of my knowledge there’s not a publicly available list for most of the providers, but I’m also not sure why you would even want/need one? Like, what’s the threat you’re trying to mitigate by allow/blocklisting arbitrary mobile network vendors?
Same, I don’t see anything about hdmi in there
P.P.S Do not make a self-hosted password manager your first project. You should expect one of these first projects to absolutely eat shit for reasons you don’t fully understand yet, and having it be your daily-driver password manager would be a hell of a shitty weekend.
The other recommendations are good, but please please double check your tstat wiring and/or HVAC system to ensure they are compatible. One of the few stats that work with my system without shenanigans is the Honeywell T10 Pro (which also worked out of the box with HA). This required me to rewire the control run to use it, and is not something I would recommend for people who aren’t prepared to cook the control board on their furnace if they do an oopsie or regularly read electrical diagrams.
No, because there wouldn’t be anything connecting the two ports together. In your scenario, all each side would be able to do would be to talk to ‘cpu’, there would be no mechanism to forward traffic upstream without iptables or something similar handling that function.
About 70% of my server list would have been better as a message board.
Given the proclivities of Valve and their hardware so far, i woud expect the gabecube to not have soldered ram.
Yeah, I agree with ‘nuke first ask questions later’ when your compromised host is impacting other devices. If and only if i knew the attempts weren’t going anywhere or doing anything would I consider unicing the vm/container to see what happened.
This seems to me an application of the 80/20 rule. Valve (and its infrastructure) is taking it the last 20% needed to make it mainstream-viable.
Without having access to a known good connection (or known good setup) you can’t 100%, but if you can take packet captures at the handoff to the isp equipment and the far side doesn’t receive them, that’s a pretty clear indicator to me. At the very least it would be enough for me to reach out to them and ask what’s up.
My experience was miserable attempting to do so, to the point that it was better to just nuke everything across 4 drives and start over
That seems reasonable to me as far as implementations go. The ones where they will autoassign always just overload pd index 0 which is worse than doing nothing imo lmao
It is. How At&t handles it is they hand out only 1 /64 of the delagted /60 (by default) per explicit IA-PD request, rather than the full /60 they allocate by default (which, note, is not on a nibble boundry like it’s supposed to be, and you only get half of that as usable).
But on every gateway device I’ve used, even if you get a full /56 prefix, you still have to explicitly assign out each /64 to sub interfaces. Really, ipv6 is a bunch of great ideas which were ruined by shitty implementations everywhere.
It’s going to be a nice release