Abandon search engines, normalize asking your cousins your questions again

First time I’m hearing about this, could you elaborate?

Thanks, that’s a great write up. One thing I didn’t ubderstand however is in your Docker macvlan, you set the parent to br0.10 and br0.20, where are those parents defined?

Maybe I misunderstood the macvlan documents but what I did was defining a vlan in server netplan vlan0.100 and set the macvlan parent to that vlan0.100. Is that not how it’s supposed to be?

I will post it when I get my hands on it, but basically I made a macvlan which is using the server vlan, and then in the compose I set the network to that macvlan, which seems to be functional at least

Thanks for sharing this, I’ll give it a try and see how it goes

I mean at the moment I don’t have any bridges setup (other than the dockers own bridge) I thought maybe I could solve my issue with bridging

That is my gut feeling too, but as I mentioned in another comment all physical devices work fine in their respective subnet. This is happening before I move the containers to a new subnet, and before these changes everything was working fine.

Answer to your first question, he dockers successfully resolve and access internet

2. Yes the OPNSense is the primary router and dhcp provider so all the subnets and vlans are defined and working with physical devices

I actually was having the same issue with the routing of server. How did you setup your bridge exactly? Do you mind sharing your netplan?

I apologize if my comment came off as an attack, that was not my intention.

I appreciate you putting in the effort to bring up a concern, but I still don’t get it.

Hope you enjoy your weekend

I not sure what you are trying to argue.

Even if you audit the code yourself, you still need to trust your OS, you need to trust the hardware the OS is running on, and you need to trust the proprietary drivers of each component in that hardware. Then at that point you gotta trust the person who sold you the hardware hasn’t modified it.

Ok and?

Which app? Which implementation?

For large networks with over 20 devices, I find them acceptable not because they are good but because other options are more expensive.

For small networks? I despise them

1. The UI keeps changing and moving around settings for no good reason after each update
2. You can’t setup devices directly if you have a device or two, you are required to setup a control center
3. The control center is already slow and sluggish, but the real nightmare starts when you start having 100 or more devices
4. Last couple of years they have been releasing batches with serious issues, software and hardware. The way they accepted recall for unfixable devices was so limited that many people are left with broken APs that will kill their network occasionally and the poor consumer has no idea why.
5. Honestly fuck 'em. there’s more but I don’t wanna give them any more rent space in my head on a Sunday lol

That’s amazing, thanks for sharing!

Ah right, I thought you were doing it like this

Internet -> Fritzbox + Pihole -> Opnsense -> Home Network

It makes sense now :D

That sounds overly complicated, why not have it all on opnsense instead of 3 different devices?

Is your opnsense unstable? Otherwise regarding network availability you are just introducing unnecessary failure points the network.

I’m curious as why you decided to setup pihole when you already have opnsense. More so that your records are in pihole and not opnsense

No, Hosting has a technical definition. When you rent a server or in this case VPS, the company is hosting you. You can maintain or administer the services but you are never hosting yourself on someone else’s computer.

Is it self hosting? No.

Does it matter? Idk.

By definition, the cloud provider is hosting you. It’s not about being good or bad it just is. If the mod deemed your question to be irrelevant to the community then idk maybe it does matter in this context.

Great news for bloatware enthusiasts ᐠ( ᐛ )ᐟ

Nothing bricking, just some compatibility issues I had and being stuck to microg releases was not my ideal way to go.

Installing them separately is really easy so no need to worry. Basically you install lineage then droidify and you can install microg services from there.