Selfhosted

60887 readers

846 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

What access points do you use? (lemmy.ml)

submitted 2 years ago* (last edited 2 years ago) by agile_squirrel@lemmy.ml to c/selfhosted@lemmy.world

67 comments fedilink hide all child comments

I'm thinking about upgrading my W-Fi and I was curious what wireless access points (WAP) people are using. I'm currently using a Netgear R7800 running OpenWRT.

you are viewing a single comment's thread
view the rest of the comments

[–] elvith@feddit.org 9 points 2 years ago (2 children)

I really like them but they do have two downsides for "more advanced" users (or at least for me) - it is a home device as after all.

No support for VLAN or VLAN tagging - you can set up you WiFi and a guest WiFi. You can also map the guest network to an Ethernet port. But that's about it.
There is no way to change the DNS suffix (*. fritz.box) to another value - I do own a domain that I use for the local services on my home server, etc. which then allows for Let's Encrypt certificates, but I cannot use it "out of the box".

If you're an advanced user, there's plenty of ways around that, though. I just wished that these two thing were to exist in the firmware to have less work with my home infrastructure.

[–] thelittleblackbird@lemmy.world 3 points 2 years ago (1 children)

Totally agree with the first point, it is a limitation, and the guest wifi sticking to a eth port is just a patch. One that works but still a patch.

But I don't see the point of the prefixes. What do you mean? I also have a custom domain and a local dns server y can use the domain even internally. I just simple ignore that...

[–] elvith@feddit.org 2 points 2 years ago

Yeah, I’m also using a local resolver. But since I had some problems using another DHCP server (which was probably a problem on my end), so I’m current setting some devices in my FRITZ!box to a fixed IP and then enter that in my DNS server. If I could just skip the second part and tell the FRITZ!Box to just resolve printserver.example.com instead of printserver.fritz.box - that’d be nice. Maybe I should do another try with a DHCP server soon.

[–] MangoPenguin@lemmy.blahaj.zone 1 points 2 years ago

Damn those are some serious limitations for an AP.