this post was submitted on 29 Jan 2025
38 points (95.2% liked)

Selfhosted

41554 readers
509 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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?

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.

you are viewing a single comment's thread
view the rest of the comments
[–] Shimitar@downonthestreet.eu 2 points 1 day ago (4 children)

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?

[–] vividspecter@lemm.ee 1 points 18 hours ago

Compared to other embedded devices, ease of installation, less chance of driver quirks and much higher performance (especially relevant if you're running a VPN on the same device).

Compared to other x86 software based routers, a UI that is familiar, and the Linux kernel which generally means it gets new features quicker than its BSD based counterparts.

[–] MangoPenguin@lemmy.blahaj.zone 3 points 1 day ago (1 children)

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.

[–] possiblylinux127@lemmy.zip 2 points 1 day ago (1 children)

Better hardware is not a VM in Proxmox. You want quality gear with each component doing one job.

[–] MangoPenguin@lemmy.blahaj.zone 1 points 21 hours ago (1 children)

If thats what your needs are. But proxmox has nothing to do with the hardware being better.

[–] possiblylinux127@lemmy.zip 1 points 17 hours ago (1 children)

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)

[–] MangoPenguin@lemmy.blahaj.zone 1 points 4 hours ago* (last edited 4 hours ago)

True, modern hardware can easily route 10gbps or more though so for most of us that won't be an issue. Often OpenWRT on consumer routers struggles to route even 1gbps.

I agree on the external AP, that is needed.

[–] mouse@midwest.social 1 points 1 day ago

It can be used as a VPN router, any VM that needs a VPN can be connected to a network bridge that is forward through the VPN. This could also be done on the primary router and a VLAN.

[–] JackAttack@lemmy.dbzer0.com 1 points 1 day ago

Well currently I have a nest wifi pro router that doesn't allow a lot of customization. (I used to be a Google fan). And since I had a beelink I figured I would try it. I was also wanting to be able to run a VPN on my router and the nest doesn't allow clients.