computing:classic-bridging
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| computing:classic-bridging [2025/11/09 03:37] – oemb1905 | computing:classic-bridging [2025/11/09 03:39] (current) – oemb1905 | ||
|---|---|---|---|
| Line 11: | Line 11: | ||
| ------------------------------------------- | ------------------------------------------- | ||
| - | This tutorial is for Debian users who want to create network bridges, or virtual switches, on production hosts. These bridges can be used to pass traffic upstream to virtual appliances of all types. In the different bridge scenarios I cover in this tutorial, the intent is to pass traffic to Debian VMs which either run services for my business infrastructure and/or direct services for clients (usually some form of web hosting). I have two production servers: | + | ====== Introduction ====== |
| + | ~~NOTOC~~ | ||
| - | Brown Rice: Super Micro (Xeon Silver), 384GB RAM, 10.4TB zfs R10 JBOD (Co-Located) | + | This tutorial is for Debian users who want to create network bridges, or virtual switches, on production hosts. These bridges can be used to pass traffic upstream to virtual appliances of all types. In the different bridge scenarios I cover in this tutorial, the intent is to pass traffic to Debian VMs which either run services for my business infrastructure and/or direct services for clients |
| - | Pebble Host: Ryzen 7 8700G, 64GB RAM, 2TB NVME (Dedicated Hosting) | + | * Brown Rice: Super Micro (Xeon Silver), 384GB RAM, 10.4TB zfs R10 JBOD (Co-Located) |
| + | * Pebble Host: Ryzen 7 8700G, 64GB RAM, 2TB NVME (Dedicated Hosting) | ||
| Each of these machines uses virsh+qemu and have little or no public services listening. The primary and nearly exclusive role of these machines are to run/manage the virtual appliances within them. I typically run virsh+qemu and run VMs for a variety of services such as but not exclusive to private clouds, websites, mail servers, relays, etc. For this reason, it's imperative that the networking setups be solid and that I have good documentation of them. Each location, however, has a different set of requirements due to how they broadcast IP/ | Each of these machines uses virsh+qemu and have little or no public services listening. The primary and nearly exclusive role of these machines are to run/manage the virtual appliances within them. I typically run virsh+qemu and run VMs for a variety of services such as but not exclusive to private clouds, websites, mail servers, relays, etc. For this reason, it's imperative that the networking setups be solid and that I have good documentation of them. Each location, however, has a different set of requirements due to how they broadcast IP/ | ||
| + | ====== Brown Rice ====== | ||
| + | ====== Pebble Host ====== | ||
| --- // | --- // | ||
computing/classic-bridging.1762659476.txt.gz · Last modified: by oemb1905
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
