@Maholmire I mean why put it inside a VM if you already have a VM? Like, the college gives you a VM: why do you need VirtualBox?

Either way, the case might be that you can't route to it from outside. (You also don't need an ethernet port to bridge: you create a bridge interface and then you can add and remove other interfaces at will, any of which could be virtual. The conventional use for it is to add ethernet ports to the bridge interface to bridge the ports, but now people often bridge one physical port with several virtual ones, but you don't have to have *any* physical ports involved. FSE talks to Postgres over that kind of bridge.)

> Currently running through some Nix-related troubleshooting atm. Though I just wish it would've been easier to connect to a VM by default rather than having to jump through hoops.

Easiest way to do this is to just use qemu and forward a port on the host to a port on the VM, or to just use libvirtd (I expected to hate libvirt but after I got all the XML out of the way, I did not hate it at all).