• 0 posts
  • 44 comments
Joined 3 years ago
Cake day: June 7th, 2023
  • For most people, the thought of replacing an outlet or switch is daunting to say the least. My IKEA smart bulbs are going on 7 years old and still working great.

    I did replace every single outlet and switch in my house when I moved in, but that was before I knew about ZigBee or Zwave, and well before matter existed.

    I don’t feel the need to replace most of my switches and half of my outlets again.

  • Effectively, the other option is passwords, and people are really, really, bad at passwords. Password managers help, but then you just need to compromise the password manager. Strong SSO, backed by hardware, at least makes the attack need to be either physical, or running on a hardware approved by the company. When you mix that with strong execution protections, an EDR, and general policy enforcement and compliance checking, you get protection that beats the pants off 30 different passwords to 30 different sites, or more realistically, 3 passwords to 30 different sites.

  • The modern direction is actually going the other way. Tying identity to hardware, preventing access on unapproved or uncompliant hardware. It has the advantage of allowing biometrics or things like simple pins. In an ideal world, SSO would ensure that every single account, across the many vendors, have these protections, although we are far from a perfect world.

  • On Steamdeck, I haven’t tried multiple controllers, but with one, it has been rather seamless for both the PS5 and the Stadia controller. They are both Bluetooth, and when I turn them on they just work. That said, the original SteamDeck(which is what I have) doesn’t support CEC or Bluetooth waking, so the Switch wins out on automatically turning on and switching my TV’s input. The OLED SteamDeck is supposed to fix that, but I’m not paying for a replacement until this one dies or a SteamDeck 2 comes along.

  • Others have given you a good idea, but since you appear to be using Unifi for switch and firewall, o can give you a clear answer: Don’t set vlan on the Synology. Set it as the “Native” VLAN on the switch port going to the Synology.

    Synology can be vlan aware, but you don’t need it. Let the switch do the talking.

    On the Synology I recommend putting it on DHCP while you test. Once it starts getting an IP in the right subnet, you can then switch it to static. Just make sure your gateway is right, putting it wrong will cause the device to not be able to reach outside its own subnet.

  • I agree. The hardware was out of date before it was released. The controls were poorly placed to make the joycon gimmick work. It was designed for little kids hands and didn’t offer a solution for adults. The steamdeck really highlighted all these problems by doing it better day one. But for the target demo of the switch, very little of that mattered, and it was a great success. I just hope the Switch 2 learns from these mistakes and doesn’t repeat them.

  • M365 is doing away with all legacy authentication, do not be surprised if IMAP is completely unusable in the next 12 months. If you simply want to keep a copy of everything, a store and forward SMTP proxy would probably be the solution, so all email going to your domain would hit that first, then send off to M365.

  • The advantage of docker, as I see it for home labs, is keeping things tidy, ensuring compatibility, and easy to manage/backup setup configs, app configs, and app data. It is all very predictable and manageable. I can move my docker compose and data from one host to another in literal seconds. I can, likewise, spin up and down test environments in seconds too. Obviously the whole scaling thing that people love containers for is pointless in a homelab, but many of the things that make it scalable also make it easy to manage.