Segregating vlans, but sharing some data

[Pattagghiu]

Hello,
i lost the fight with my dark side and eventually got a no-brand N100 box with 4 2.5Gb nics and 16Gb ram.
Formatted everything and put proxmox on it. Shortly i put on it:
- VM openwrt (pci passthrough for the WAN interface)
- VM openmediavault (keeps the data, sits in the base trusted lan)
- lxc with home assistant and jellyfin (sits in the iot vlan)
- lxc with transmission (sits in a dedicated vlan)

Now, the problem:
- transmission needs to get access to a folder/disk/something on openmediavault where to put files in
- jellyfin needs to get access to folder/disk/something on openmediavault where to read file from.

seems clear network access is not the way since my target is to keep them separated (yes opening maybe one port is better that having all together, but i'd avoid..)
Is there a way at proxmox level to share "something" between them?
Can i mount a shared folder with proxmox and pass it to the LXC as disk?
Any other idea?
Thanks

 

[LnxBil]

I'm no friend of pcie passthrough for this. I'd go with LACP on all interfaces, have one bridge and run the VLANs on top of them. Separation is directly done in the VMs and in the switch. You then can just create another VLAN for the VMs to share data in a separate network.

 

[Pattagghiu]

I'm no friend of pcie passthrough for this. I'd go with LACP on all interfaces, have one bridge and run the VLANs on top of them. Separation is directly done in the VMs and in the switch. You then can just create another VLAN for the VMs to share data in a separate network.

hello,
the only passthrough i uses is for the WAN connection to the openwrt instance (so i'm sure this is staying by itself), all the rest IS on the same bridge, but tagged.
but if i keep LXCs segregated it is a nonsense to create another vlan to share data, isn't it?
have i other solution to keep networks segregated, but share data?
thanks

 

[LnxBil]

the only passthrough i uses is for the WAN connection to the openwrt instance (so i'm sure this is staying by itself), all the rest IS on the same bridge, but tagged.

Thank's for clearing that up.

but if i keep LXCs segregated it is a nonsense to create another vlan to share data, isn't it?
have i other solution to keep networks segregated, but share data?

For LX(C) containers, you can just bind mount the data, yet for KVM/QEMU VMs, there is no way over the GUI to do that, yet. You may try 9psetup.