Test Lab Notebook

Exploring IPv6 Address Space for the RADV Router In my last post, I set up the NAT network that will enable the Router Advertisement Daemon (RADV) router to connect to external networks. Now, I’m shifting focus to choosing an address space and documenting what I’ve learned about IPv6 networks in preparation for deploying the RADV router. The Immensity of IPv6 Address Space As I delve into IPv6, I’m astonished by the vastness of its address space. IPv6 provides approximately 10 38 × 3.4 unique addresses—enough to assign an IP address to every grain of sand on Earth and still have plenty left over! This expansive range allows for an unprecedented number of devices to be connected to the internet, far exceeding the limitations of IPv4. Why I Need a Unique Local Address (ULA) For my lab setup, I need to utilise a Unique Local Address (ULA) for internal communication. ULAs are similar to the private address ranges defined in IPv4, such as 192.168.x.x or 10.x.x.x...

  Bonus Notes: Setting Up the Host OS with Chocolatey (Infrastructure as Code for the Host) As I’m using infrastructure as code principles in my lab environment, it makes sense to extend this approach to my host operating system as well. By automating the installation and configuration of essential software on the host OS, I can ensure consistency, repeatability, and efficiency across my entire setup. In this bonus content, I’ll cover how to use Chocolatey to set up Git, Vagrant, VirtualBox, and Packer on Windows, including automating Git configuration during installation. Why Use Chocolatey? Chocolatey is a package manager for Windows that simplifies the installation and management of software. By leveraging Chocolatey, I can automate the setup of development tools and other software, aligning with my infrastructure as code approach. This automation not only saves time but also helps maintain a standardized environment across different machines. Installing Software with Chocol...

Setting Up a NAT Network for the RADV Router In this post, I’ll be focusing on the first essential step before deploying the Router Advertisement Daemon (RADV) router: establishing a NAT network that enables external connectivity. To streamline this process, I’ll utilise VirtualBox’s command line tool, VBoxManage , to automate the network creation. This approach not only enhances consistency within my lab environment but also aligns perfectly with my Infrastructure as Code (IaC) principles, ensuring that every network configuration is repeatable and version-controlled. Git plays a crucial role in managing and tracking these changes. Every script and configuration is stored in a Git repository, making it easy to roll back or redeploy setups elsewhere. This practice ensures that each network modification, such as adding a NAT network, is committed to the repository, promoting full transparency and traceability—key practices to carry into production environments. For the RADV router, a...