@dragonarchitect @demicus AFAIK they explicitly removed #WiFi from #Proxmox (which is based off #Debian) because they only target #rackmount|able-hardware and consider WiFi & #Bluetooth as mere 'sidechannel attack vectors'…

• One could just get one of those cheap WiFi->Ethernet bridges if wired etherenet cabling isn't an option as a workaround.

Obviously their take makes sense in a #datacenter envoirment (pretty shure #vmware #ESXi and #Microsoft's #HyperV don't do WiFi either!) because homelabbers who can't even afford cheap Gigabit-#Ethernet ain't their customer audience.

• OFC that is annoying for those who don't have that luxury at hand!

@kkarhan @dragonarchitect @demicus Where did you read that, especially the "sidechannel attack vectors"? o.O
That's just FUD.

It's a restriction of WiFi itself - chipsets only support a single client, so bridges & co won't work and you need a NAT'd setup to begin with and other workarounds. It's also neither made not stable enough for 24/7.

But at the end of the day it's Debian, so you can configure it manually and there are forum threads on how.

@kkarhan @dragonarchitect @demicus I mean yeah, but on the other hand, if you actually run such environments and compliance is needed, you are using proper server hardware - which won't have all that anyway.

Using consumer hardware - apart from its many other problems - is not suitable for such environments and will never be.