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?

  • aTun@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 day ago

    If you do the PCI passthrough Wifi adapter to openwrt, look for name of adaptor and search okpg for in kernel driver for that. Maybe you will face with no driver support, try installing openwrt pre-relase for up to date driver support, or driver only support client mode, Intel Wifi. You can get cheap USB Wifi adapter from Aliexpress that openwrt support but mostly have only one radio so your access point will have one 5Mhz or 2.4Mhz not both at the same time. you can try two adaptor to get both. For supported Wifi adapter and more information https://github.com/morrownr/USB-WiFi?tab=readme-ov-file

  • roofuskit@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 day ago

    If you’re going to dive in to openwrt from google wifi you should probably start with ready made hardware.

    https://forum.openwrt.org/t/best-newcomer-routers-2024/189050

    Please keep in mind that to duplicate mesh functionality it’s going to take a significant effort and you need to make sure the hardware you buy is compatible with 802.11s. Open WRT forums have hardware compatibility rundowns of known working routers so it’s not too difficult to find them.

    This is a much bigger uphill battle rolling your own hardware unless you just plan to buy a separate access point or two for hardware and skip the mesh functionality.

  • ChillPill@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 day ago

    Back in the day I ran a pfsense VM on ESXi before broadcom bought them. I found it easier to just purchase a cheap Unifi AP and spin up a VM for the Unifi controller app (I’m assuming you can still run that on your own hardware, its been a few years). I think I got a UAP 6 lite or something like that. If I recall it was about $130 CAD with the PoE injector.

    Techincally its not ideal to run your firewall on the same device as other things, but I never had any issues.

    Also, does the mini PC have multiple NICs? You will have a bad time if it does not.

  • Possibly linux@lemmy.zip
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 day ago

    You want a dedicated Firewall and at least on access point. Your USB adapter is not designed to support lots of devices. It almost certainly has one channel.

  • just_another_person@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    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.

  • MangoPenguin@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 day ago

    It would be fun as an experiment, but often using wifi adapters as an AP generally doesn’t work that well. Most of us are running an external AP such as Unifi hardware.

    As far as getting this working, have you done the passthrough setup on the VM for the wifi adapter?

    And have you confirmed that OpenWRT supports your wifi adapter?

    • JackAttack@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 day ago

      Both great questions. I did not check the hardware and I definitely should have…as far as passthrough I have not. I really only ran the helper script to install the Proxmox VM and configurations. I’ll have to check the settings when I’m back home to see what exactly it did.

  • Shimitar@downonthestreet.eu
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 day ago

    What is the point in installing OpenWRT on something that is not a router? I use it, i have it on a few different WiFi access points…

    but what would be the reason to install on a regular pc, whether on VM or not?

    • MangoPenguin@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 day ago

      It’s a handy router OS, why not?

      Consumer router hardware generally under performs a lot, so running your router on better hardware solves that.

          • Possibly linux@lemmy.zip
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 day ago

            I does though since there is the added overhead.

            You want hardware that is designed for networking. Networking pulls the CPU away from other things. It might be fine if you only ran a router in Proxmox but that’s about it.

            Also, good wireless hardware is needed for any decent speeds. You want good antennas connected to hardware that has MU-MIMO. It is also important to pay attention to the Wireless version. (You want at least WiFi 5 if not 6)