Proxmox and Raspberry Pi

Hello World,

Thanks again for your advice and corrections.

Was seeing the use and installation of proxmox on a raspberry pi 4/5 and raspberry pi compute module 4b with a hat....and got me interested in how openwrt is installed/used on proxmox.

My question being
Once proxmox is installed on a raspberry pi then openwrt is installed via Virtual machine, then load balance and network bonding interface using openwrt is configured, do the interface work automatically?

Having proxmox installed on the raspberry pi, additional Operating system can also be installed separately using Virtual Machine configuration/settings on the device, does the interface loose their configs?

Does the use of a different Operating system on boot [which are Virtual machine] keep the openwrt configs within the same device via proxmox?

All answers are appreciated.

virtual machines connect to the bridges defined on host. You can passthrough PCI or USB devices to a VM under more advanced scenarios.

Again thanks.
So the configs work on my all case scenarios by use of bridge?

OpenWRT will not escape virtual machine you configure. Rest you have to ask whomever sells you moxpox


Two things to consider:

  • one generic, applying to 'every' kind of virtualization
    this always forces you to do several key policy decisions (configurations) twice, once on the hypervisor (which bridges attach to which virtual network card) and another time inside the VM (on OpenWrt as well). If you are on top of your hypervisor-foo (or only need it for optional stuff on your lab network, for experimenting) this can be fine, but it does make your setup significantly more complex and introduces some bootstrapping dependencies you need to be aware of (the hypervisor needs 1+ IPs, but the DHCPd is only running in a VM on top of it, but the VM won't start before the hypervisor works, correct system time is increasingly important for anything around encryption, but the RPi doesn't have a battery-backed RTC, so the time will only update after you've come online (not good)).
  • one RPi specific
    x86_64 is easy and simple, you have one generic image that works 'everywhere' (the magic of UEFI/ BIOS and ACPI), ARM isn't, you need a bespoke image (and target) for pretty much anything. If you can boot armsr (system ready) images in a VM on your RPi is something for you to find out, but be expected to spend quite some tinkering (and potentially development) before you may succeed (it 'should' be possible, but I haven't heard any specific success stories on an RPi host yet - and there are many potential pitfalls that would require quite some effort to solve).

Your border gateway is a quite essential part of your network, it does make sense to run it on dedicated hardware (x86_64, RPi4+ or one of the more traditional plastic routers like filogic 8x0 or ipq807x) and to keep the setup 'simple'. This reduces its attack surface and makes disaster recovery (which may just be a blown fuse or an excavator down the street having ripped apart your 'internet' cables a lot easier. Keep it easily compartmentalized, with clear functionally independent devices.

1 Like

This is what an answer and advice looks like.
Very much appreciated and content for now.

Have to do more research and tinkering from this advice.

Much appreciated.