32

I have a home setup with private services and Wireguard to phone in from outside, and would sometimes like to be able to access some of these services from devices that don't have their own Wireguard client like an eBook reader.

Ideally, I would have Wireguard on my Android phone, create a WiFi hotspot and allow other devices to use that Wireguard connection. Out of the box this doesn't work. Does anybody know how to achieve it?

you are viewing a single comment's thread
view the rest of the comments
[-] tofubl@discuss.tchncs.de 5 points 2 months ago* (last edited 2 months ago)

Dang, also on Graphene...

here's a thread with official Graphene voices saying it won't happen (and why)

[-] jet@hackertalks.com 6 points 2 months ago* (last edited 2 months ago)

Yeah, to me it's a absolute killer feature for a travel phone. The GOS discussion around it boils down to violating the android profile security model.

E.x., im using a hotel wifi that only allows one device, or I have a esim for one phone only that doesn't allow "tethering".

Fair enough on the security model, but at least give me the option... Maybe with a always on notification warning. Being paternalistic about how you think the phone will be used and in which context is overstepping for infrastructure

I travel with a backup phone, and because of this I have calyxos on the backup and not gos.

[-] tofubl@discuss.tchncs.de 3 points 2 months ago

Having strong opinions is what Graphene does. 😅

And they do seem to be an authority on all things security, so most of the time I like that about them.

this post was submitted on 06 Oct 2024
32 points (97.1% liked)

Selfhosted

40696 readers
320 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