• 0 Posts
  • 7 Comments
Joined 2 years ago
cake
Cake day: June 5th, 2024

help-circle
  • Not that I have any say in the matter but I think this kind of question is fine for the selfhost community. It’s still in the spirit of “how to do xyz with my own hardware / less dependence on a third party”.

    The other suggestions have covered my own. I did want to add that good resources for finding these kinds of tools are often called Awesome lists. Awesome self-hosted. Awesome CLI. Awesome social media. You get it. I’m not sure where the trend started but I stumbled on them after getting fed up with the likes of Slashdot and AlternativeTo.

    They’re usually a community-maintained git repo on one of the major platforms. This list has quite a few hits for “YouTube”, for instance: https://github.com/krzemienski/awesome-video


  • I’m a bit late to the party. I was a network admin in another life and believe I can help out. I’ve skimmed existing conversations but not fully poured over them.

    That said: I’d print the routing tables for the switches and firewall and review them. Considering firewall rules is sensible but it seems you’ve already done quite a bit of investigation there. It sounds like there is some vlan configuration missing. Like one of the switches doesn’t have the vlan interface defined or named in its vlan database.

    Review the routing tables and confirm who owns each vlan and what those networks are aware of. Also toggle your logging options on so you can review them and test with more info than pass/fail.

    It very well may be a OPNsense firewall knowledge thing but I’m not convinced. If you’re still working on this tomorrow I’d be happy to help root-cause the problem and fill in the gaps between RTFM and old YouTube videos. :)




  • Sure! That’s an SMTP Relay. A lot of folks jumped on the poopoo wagon. It’s common wisdom in IT that you don’t do your own email. There are good reasons for that, and you should know why that sentiment exists, however; if you’re interested in running your own email: try it! Just don’t put all of your eggs in one basket. Keep your third party service until you’re quite sure you want to move it all in-house (after due diligence is satisfied and you’ve successfully completed at least a few months of testing and smtp reputation warming).

    Email isn’t complex. It’s tough to get right at scale, a pain in the ass if it breaks, and not running afoul of spam filtering can be a challenge. It rarely makes sense for even a small business to roll their own email solution. For an individual approaching this investigatively it can make sense so long as you’re (a.) interested in learning about it, (b.) find the benefits outweigh the risks, and (c.) that the result is worth the ongoing investment (time and labor to set up, secure, update, maintain, etc).

    What’ll get you in trouble regardless is being dependent on that in-house email but not making your solution robust enough to always fill its role. Say you host at home and your house burns down. How inconvenient is it that your self-hosted services burned with it? Can you recover quickly enough, while dealing with tragedy, that the loss of common utility doesn’t make navigating your new reality much more difficult?

    That’s why it rarely makes sense for businesses. Email has become an essential gateway to other tooling and processes. It facilitates an incredible amount of our professional interactions. How many of your bills and bank statements and other important communication are delivered primarily by email? An unreliable email service is intolerable.

    If you’re going to do it make sure you’re doing it right, respecting your future self’s reliance on what present-you builds, and taking it slow while you learn (and document!) how all the pieces fit together. If you can check all of those boxes with a smile then good luck and godspeed says I.