From: Perry The Cynic <perry@cynic.org>
To: Antonio Quartulli <a@unstable.cc>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Wireguard, iPhone, and cruise ships
Date: Thu, 13 Jun 2024 07:52:19 -0700 [thread overview]
Message-ID: <DEFB63D6-D7B8-4774-85CF-A8B387401D52@cynic.org> (raw)
In-Reply-To: <d592d6a9-8d4f-4d0e-935d-73735c37bc7d@unstable.cc>
That works when I’m in my room/cabin/place. I’m actually building a Raspberry Pi-based travel box right now (so next time I have linux tools to diagnose problems), and it can do tcp wrapping/forwarding. But carrying a battery-powered router-sized thing around on vacation somewhat defeats the point of carrying an iPhone on travel. Another box to break, another battery to run out. And my wife wants vpn access too, even if she’s away from me.
Cheers
— perry
> On Jun 13, 2024, at 7:45 AM, Antonio Quartulli <a@unstable.cc> wrote:
>
> Hi,
>
> On 13/06/2024 16:34, Perry The Cynic wrote:
>> So what are the practically available options here? I can set up whatever is needed on the server endpoint (it’s Debian), but what can I do on my phone to make wg work through an HTTP(s)-shaped pinhole? I’d hate to have to ditch wg for some other vpn just for that rare case… but what’s the answer?
>
> How about simply getting a small travel router that you can install between your devices and the uplink connection (being this wifi or ethernet)?
>
> The travel router could be running OpenWRT and thus allow you to play any wanted trick.
>
> Cheers,
>
> --
> Antonio Quartulli
prev parent reply other threads:[~2024-06-13 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 14:34 Perry The Cynic
[not found] ` <CAOG=JUJ=TWZicAd1zfa36GwFBh8EU3bgsO5JRJiEhdhQ1VWf+Q@mail.gmail.com>
2024-06-13 14:42 ` Perry The Cynic
2024-06-13 14:45 ` Antonio Quartulli
2024-06-13 14:52 ` Perry The Cynic [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DEFB63D6-D7B8-4774-85CF-A8B387401D52@cynic.org \
--to=perry@cynic.org \
--cc=a@unstable.cc \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).