Not sure if this 100% goes here but I’m relatively new to the self hosting world. Please advise if this needs to be moved elsewhere and I will.

I recently picked up a beelink mini PC and have been running Proxmox for things like jellyfin, home assistant, etc.

I’m looking to set up OpenWRT and found a helper script that sets up the VM but I’m having issues being able to configure wireless. According to the official docs, wireless is off by default if there are eth ports. When I go to edit it, both in the LuCl and in the /etc/config/wireless file, I hit 2 issues:

  1. The web client doesn’t have a wireless option.
  2. There is no wireless file In the config directory.

I tried looking for some solutions online but wasn’t sure what was exactly specific for me. I wasn’t sure if this was a hardware issue or a Proxmox/OpenWRT config issue. Any advice on this?

Side note: My thoughts were I could use the internal wi-fi adapter for wireless but would I need a USB adapter of some sort for this capability?

  • just_another_person@lemmy.worldEnglish
    0·
    1 day ago

    There’s a huge list of reasons why this is not going to work, or not work well.

    I’ll stick to the biggest issue though, which is that OpenWRT expects exclusive control over the wireless chipset, and you’re trying to run it through a VM on whoknowswhat hypervisor settings. Even if nothing else on the host machine uses the Wi-Fi adapter, OpenWRT has specific builds and kernel patches for specific drivers and specific hardware combinations. If it doesn’t see exactly what it’s expecting, it’s not going to work.

    Now…even if you DID manage to get it to seemingly work, it will constantly crash or panic if you engage the wireless chipset on a hypervisor because it’s going to throw some disallowed instruction expecting exclusive control and access to the hardware.

    I know this, because this is how it works, they say so in their own docs, and you can see people say the same thing over and over again this exact same thing. It’s not going to be a good time.

    If you want to just use software portions for network services or whatever, that shouldn’t cause issues, but again, doing it through a VM is like dressing a Yugo up as a Ferrari and expecting the same performance.