Yes, because each one has been. Just because it’s “Apple” and you think it’s better every iteration is a mistake on your part.
Yes, because each one has been. Just because it’s “Apple” and you think it’s better every iteration is a mistake on your part.
Cool, so the version from many years ago related to OP’s question…how?
Pretty much exact. Lots of reviews to back that up without me spouting about it.
Take your own advice: https://www.n-able.com/fr/blog/vlan-hopping-security
For some reason you think a home router can’t be gotten into because of a VLAN of all things🤣
You’re sitting here worrying about some packets from the internet being safe for some reason and not realizing the big picture. Go back to Innernette learning school, tough guy.
Lolz at you. Sweet baby Jesus, you have no idea.
JFC 🤦
How are you NOT understanding what OP thinks is happening, versus what you thinks is happening?
If I get shell access to this router I have access to ALL NETWORKS. VLAN won’t help any of this.
You are aware that being on the router would have access to ALL the ingress and egress interfaces, right?
I’m not saying idle power is unimportant. I’m saying the M-Class chips can’t ever go idle with a minimal set of features NOT being engaged, because they’re going to be more engaged in general vs other chips that can run truly headless. macOS doesn’t allow for that.
Well it wouldn’t matter if your router is the thing that someone gets into. All you’re doing is separate traffic in different subnets, and if that’s your goal, you’re good to go.
Please inform me of how that’s…“insane”?
VLAN on a singular router without physical separation is not secure. OP was asking for feedback, that’s my feedback. It’s accurate.
Friend…you clearly are not reading what I’m saying. Not one single sentence that I’ve typed suggested there needs to be, or ever was a physical separation. That is why this setup without clarification doesn’t make much sense if security is the goal.
You are saying exactly what I’m saying and arguing about it for some reason.
Not saying physical switches are needed for security, which is why I was asking for clarification. Doing all of this on a router doesn’t make sense without a physical separation though. That’s my point. If the router gets owned, they have access to all networks anyway. If the idea is just for traffic direction and shaping, then I’m confused why the bridged pihole.
I don’t think there is anything wildly wrong with it, but it seems like you’re doing all of this at the router, unless you have dedicated switches for each VLAN?
VLAN is not a security feature, it’s a logical separation of IP segments. Maybe I’m missing your intention here, but just setting different IP spaces on VLANs and then bridging them doesn’t help your security, it just complicates your network.
You may want to check your specs again. The Ryzen APUs are very power efficient and run the same stretch as M3 (reported): 15W-45W
Though the more realistic at the wall measurements of the 2023 Mac Minis pretty much seem to have it pegged at a solid 15W-25W min under normal service workloads. The reported “idle” measurements of the M* chips being at 6W are literally just saying “if it has power”, and unrealistic considering you can’t even run them without a the GPU being engaged somewhat without a fully headless software configuration.
You can get a Ryzen mini PC for less than $200. Depends on what is worth to you in cost.
Unless you’re watching the videos directly on the Synology, I don’t see this affecting too much unless you’re strictly relying on transcoding for other devices you’re positive don’t support it. Even then, you could always just default to rendering on the remote device directly which isn’t a huge deal. If you’re using Dolphin, it shouldn’t be an issue. You could always use VLC as well and it shouldn’t be a problem.
Maybe I’m missing something else?
You need a public DNS record that points to your public IP of your server.
Well the services would have to speak the same event or messaging system, whatever it may be. Then you’d just need to bridge the networks of the containers, or have them speak to endpoints in each side.
There is no universal messaging system between all pieces of software though. Maybe figure out what you’re sending to first, then work back from there. There’s nothing blocking you from sending data between two containers in a variety of ways though.
deleted by creator