fraichu

This worked. Now I can have unlimited lightweight systemd containers, each with it's own globally routable public ipv6 address :)

I hope some GPU manufacturer starts allowing removable RAMs. 4 x 8 GB DDR5 might not be too bad given PCIe speeds aren't a bottleneck. If I could upgrade the RAM to 64 GB later, I'm ready to give $10k at 3080 level perf. Intel ARC people I hope you are already doing this!

Can you go IPv6 only with dynamic dns + recycling ip every day? My raspberry pi doesn't get bot traffic. I have 22, 80, 443 and a few other ports open on public ipv6 address.

• Can give NixOS a try if you want to make things extra hard and get more satisfaction from finishing. The biggest advantage is most of your OS & services config will be in a file, so there's no need to remember a thousand knobs to tune the experience just the way you want - a text file in a git repo will be all your config.
• I'd recommend Namecheap over porkbun. I found porkbun has less features. I specifically needed to wildcard forward email, which works well on namecheap.
• If you're from Africa, India or some other country where $10 / year is a lot I recommend a 111 class B domain https://gen.xyz/1111b for $1 / year.
• Do you have static IPv4 or globally routable public IPv6 address assigned to your device? I'm ipv6 only selfhoster, and I use inadyn and afraid
• Can use wireguard and then later open ssh once you feel more comfortable.

I'll try doing this and update if it works for me.

Chat GPT @ chat.openai.com's answer

Thank you for providing the details. Based on your requirements, you can achieve your goal by utilizing the Linux bridge functionality to create a software-level Layer 2 switch. Here's an outline of the steps involved:

1. Install the necessary software: Ensure that the bridge-utils package is installed on your Linux machine. You can typically install it using the package manager specific to your distribution. For example, on Ubuntu or Debian, you can run sudo apt-get install bridge-utils.

2. Identify your physical network interface: Determine the name of your WiFi network interface that is connected to the ISP router. You can use the ip link command to list the available network interfaces. Look for the interface name associated with your WiFi connection (e.g., wlan0).

3. Disable network management on the physical interface: To prevent network managers from managing the physical interface directly, you'll want to disable their control. This step may vary depending on your specific network manager. For example, if you're using NetworkManager, you can edit the configuration file associated with your WiFi connection (usually located in /etc/NetworkManager/system-connections/) and set managed=false. Alternatively, you can stop or disable the network manager service temporarily.

4. Create a bridge interface: Create a Linux bridge interface using the brctl command. For example, you can run sudo brctl addbr br0 to create a bridge named br0.

5. Add the physical interface to the bridge: Add your WiFi interface to the bridge using the brctl addif command. For example, run sudo brctl addif br0 wlan0 to add wlan0 to the bridge.

6. Configure the bridge interface: Assign an IP address to the bridge interface (br0) by configuring it in the network configuration files. The specific file to edit depends on your Linux distribution. For example, on Ubuntu or Debian, you can edit /etc/network/interfaces and add the following lines:

   auto br0
   iface br0 inet dhcp
   

   Alternatively, you can use network management tools like NetworkManager or systemd-networkd to configure the bridge interface.

7. Configure the virtual machines and containers: Configure your virtual machines, Docker containers, and systemd-containers to use the bridge interface (br0) as their network interface. This configuration varies depending on the specific technology you are using. For example:

   • For Docker: Create a new Docker network of type "bridge" and specify the bridge name as br0. Then, when creating or running Docker containers, connect them to this network.
   • For systemd-containers: Configure the net-attach@.netdev and net-attach@.network units to attach the container to the bridge interface (br0). This can be done using the systemctl command and systemd network configuration files.

With these steps, your virtual machines, Docker containers, and systemd-containers should be able to obtain IP addresses directly from your ISP router via the software-level Layer 2 switch created using the Linux bridge interface.

Please note that the specific commands and configuration files may vary depending on your Linux distribution and network management setup. Make sure to adapt the instructions accordingly. Additionally, be cautious when modifying network configurations as it can potentially impact your network connectivity.