I have now moved the Experiment Pod to my HomeLab rack

 I decided to drop my participation in the community sub-committee and focus on other things.  In so doing, I have moved the Experiment Pod to the HomeLab rack.  I decided to change out the rack and put the entire Experiment Pod panel into the rack as well as an Edgerouter-X to give the ExPod vlan a dhcp source and isolate it from the rest of the network.  The unmanaged 8 port switch is there as well to connect to each of the ExPod RPis.

In addition, I have added a managed switch (GS108Tv3) to offload the number of connections to the key managed switch outside of the HomeLab rack.

I have re-arranged the HomeLab rack to allow for four different systems

 I decided to change out the HomeLab rack and concentrate on four sub-systems: (1) Experiment Pod; (2) Proxmox; (3) Edgerouter-12/M4100-26g; and (4) Monitor sub-system.  Each one of these sub-systems can now be independently booted up and used.

I added a GS108Tv3 managed switch to the top of the rack so that I could change out the cables going from the HomeLab rack to only need one connection to the external GS108Tv2 switch behind the rack.  This frees up some of the ports on that switch to be used for experiments on the table.  The ExPod is now behind an Edgerouter-X connected to that top switch, with all components able to be turned off at the same time from a single switch on the power switch panel.  The Proxmox server is also connected to that top switch for all of its external ports and is powered through a single switch on the power switch panel.  The Edgerouter-12/M4100-26g combination is powered down from a single switch on the same power switch panel; external connections go through the top switch.  The monitor sub-system is also turned on and off through a single switch on the power switch panel and is behind an Edgerouter-X connected to the top switch.

I also added an RGB led lighting on the sides of the HomeLab rack.

Issue: the vlans for server admin and servers still require the Edgerouter-12 to be running since the DHCP servers are on that device.  This will need to be dealt with int the future.

Why would it be important to keep a HomeLab network after you retire?

Adapted from NoteAI.com on 2023-09-25

Summary: A HomeLab is a server setup that resides in your home and allows you to host applications and virtualized systems for testing, development, or personal use. It can be a simple tower PC, a Raspberry Pi, or a repurposed professional server. Having a HomeLab has several advantages, including providing a playground for learning and experimentation, allowing you to work on projects that you can't try on the job, and enabling you to create projects that would otherwise be costly. It can also be used for hosting media, testing websites, building a DVR system, and accessing remote systems.

Why it Matters:

• A HomeLab provides a safe and controlled environment for learning and experimenting with technology.
• It allows individuals to gain hands-on experience with enterprise equipment and software.
• It can be used for personal projects, professional development, and staying current in the industry.
• A HomeLab offers flexibility and customization options that may not be available in a production environment.
• It can be a cost-effective solution for hosting services and self-hosted options.

Significance and Potential Impact:

• Keeping a HomeLab network after retirement can provide a continued opportunity for learning and staying engaged with technology.
• It allows retirees to pursue personal projects, explore new technologies, and maintain their technical skills.
• A HomeLab can serve as a hobby and a way to stay connected with the tech community.
• It provides retirees with a platform to share their knowledge and experiences with others.
• Keeping a HomeLab network can contribute to personal growth, mental stimulation, and a sense of purpose in retirement.

Implications:

• Retirees who maintain a HomeLab network can continue to contribute to the tech industry and stay relevant in their field.
• It can be a fulfilling and enjoyable hobby that provides intellectual stimulation and a sense of accomplishment.
• Retirees with a HomeLab network can share their knowledge and experiences with others, mentoring and inspiring the next generation of tech enthusiasts.
• It can be a way to stay connected with the tech community and continue learning from others in the field.
• Keeping a HomeLab network can contribute to a fulfilling and meaningful retirement by providing a platform for personal growth and exploration.

Using pfSense as a Multi-WAN interface for Monitoring within the HomeLab

 I am back.  I started playing with pfSense in my Proxmox server in order to have a multi-headed connection into vlans within my network.  The purpose is to have an isolated vlan (isolated in the sense that the other vlans cannot get to it) to use as a monitoring point.  My thought is this: let pfSense become the DNS/DHCP source for a number of hardware and VM/LXC components to provide monitoring and automation activities.  I would eventually use Ansible to automate setups within the HomeLab and would use Observium/collectd to monitor the different HW components.  I could also use a component to provide CA capabilities.  The steps needed include:

1. download a tar.gzip of pfSense Community Edition from the pfSense website
2. create a VM of pfSense on the Proxmox server
3. setup the VM to link to an existing vlan in the HomeLab on the WAN side and to an isolated vlan on the LAN side
4. check the pfSense console to make sure that the ports are configured correctly
5. add a Raspberry Pi w/SSD to the isolated vlan and bring it up; helps if it is already setup to integrate with the tailscale network
6. check that the Raspberry Pi can communicate through pfSense to the WAN side and that it has an IP within the subnet of the LAN; this will become the seat of monitoring and automation for the HomeLab
7. add XRDP to the Raspberry Pi so that I can access the GUI
8. setup Putty on my Windows laptop as an SSH tunnel to the web interface to pfSense through the Raspberry Pi; repeat with other things that I wish to monitor

Seemed like a good idea at the time.  Not sure why this would be frowned upon security wise.  I just need to be sure that I am always aware of new and clever attacks that might be possible within the network.

I'm wondering if the same thing can be done with one of my spare Edgerouter-X routers.

Update: I was able to do the same thing with the Edgerouter-X router.  So in retrospect, I have spun down the Proxmox pfSense router for use later.  I don't think that I will be getting rid of it anytime soon.  It's nice to know that I now have the ability to change the different routers that I have to give a multi-head ability to my HomeLab.