HomeLab Updates 12/06/2024

Projects

Here are the projects I’m working on as of now. I don’t have a timeframe for any of these, but I have listed them in order of priority.

• Server Room Cleanup and Organization
  • The server closet is a mess of cables. Of course it is V1, but it’s time for V2. A complete Revamp is in order.
• Sluberski HomeLab Wiki and Git Repositories
  • Wiki is going along smoothly; I have decided to keep Repositories behind lock and key since the main purpose for them is to document what I did EXACTLY so I can replicate it. This includes some things that I do not want out publicly for security reasons.
• CrowdSec Security Tooling installation and configuration
  • Fail2Ban is really good, but as I get closer to the business stuff with OnOffHome and selfhosting tooling for that, I will need something a bit more secure, thus CrowdSec. CrowdSec is pretty involved in the setup so it will take some time.
• Revamp of Websites
  • Websites were hard to create with my old website creation tool, and they were all running static. For now, the plan is to run WordPress like I am on this site. It will take some configuration changes often so I will release updates .
  • Sluberskihomelab.com
    • V1.1 – Released
  • access.sluberskihomelab.com
    • v1.1 – Released
• Dashboard Revamp
  • Internal Dashboard revamp to give me monitoring, access, and tools in one place
  • New External Dashboard attached to access.sluberskihomelab.com requiring a login to get to for those that do have access to my homelab.
• Services Audit
  • Find out if there are any better tools that I can run in replacement of what I have.
• Re-configuration of VLANS and Routing
  • My current VLAN setup is good, but it needs to be more secure. Below is the plan
    • Server VLAN /24
    • Public Access VLAN /26
    • Business VLAN /27
    • Internal Network VLAN /24
    • IoT VLAN /22
    • Surveillance VLAN /28

Issues

Currently the only pressing issue is that I’m getting 20-30k requests on my servers per day. This is not the biggest problem since I do have Fail2Ban deployed to all my public facing servers, but it could prove to be an issue in the future.

Notes