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:
- The web client doesn’t have a wireless option.
- 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?
Edit: I realized later I left some context off. In case i wasn’t clear enough. Sorry. Currently I use a Google nest wifi pro router and was hoping to replace it with OpenWRT for more control/customization.
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.
you can simply use passthrough. openwrt acts like any other minimal linux distro.
Read the post
deleted by creator
I’ve never virtualized OpenWRT, but with hardware passthrough I don’t see why it shouldn’t work.
@JackAttack@lemmy.dbzer0.com
I’m gonna LOL the absolute fucking fuck out of this.
Try it. You have no understanding at a minimum of how it works not only at a hardware level, but at a virtualized level.
I’m absolutely sure you’re going to be the brilliant mind who fixes the problem though. See you next Tuesday!
Thanks for the advice. It isn’t an end all if I can’t get it to work in this way. Just thought I’d give it a try since I saw there was a helper script for Proxmox. I wasn’t aware of the limitations that may come with this though. I guess either upgrading routers in the future for something for customizable may be a better option.
GL.Inet for an OpenWRT hardware set. I recommend them all the time.
Any specific ones to look into?
Models? The Flint 2 is pretty damn great. Really nice hardware selections, and a form factor most people expect. Out of the box capable of being a gateway for a large network without flinching. Wireguard performance is fantastic.
I will definitely check this out. Sounds really promising from the quick glimpse and most importantly, affordable.
Edit: gesture typing made me type adorable lol.
Adorable? 🤣 How is that?
For just an AP, I’ve used a number of the GL-AR300 and they’ve been fine as AP and repeaters, but only 2.4 GHz. I have no interference issues where I am so that’s fine for me, but if you’re somewhere populated, YMMV.
They also have the full firewall/router set on them, but I generally don’t use them for that.