wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Christophe-Marie Duquesne <chmd@chmd.fr>
To: Kalin KOZHUHAROV <me.kalin@gmail.com>
Cc: wireguard <wireguard@lists.zx2c4.com>
Subject: Re: [Android] Wireguard on the Amazon FireTV stick
Date: Wed, 9 Jan 2019 19:11:43 +0100	[thread overview]
Message-ID: <CAHLp1Y=kj0Lq0SpFbgh5M-QkphChkZsNd+U9SN5QoSOdF60O4Q@mail.gmail.com> (raw)
In-Reply-To: <CAHLp1Ym2RyhT_FoNrJQVZ8gVK=dPEJsZk0wDeOPvL_ibUSTLRw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1389 bytes --]

Hi again,

I managed to enable the interface by sending a tap event through the adb
shell ("input tap 1000 100"), which brought the tunnel editor, from which
it is possible to navigate to the enable button.

And the answer is... It works!

I could verify that, when using a browser on the Fire TV, my public address
was the one of my VPN server. Quite handy if you want to take your stick on
holidays and still be able to watch content from your home country, for
example.

This is obviously hacky. In order to be usable, the app would need to
handle the navigation key events. I noticed that It already handles
KEYCODE_BACK, so I guess this could go together. Amazon has a section about
it on their documentation [1].

Cheers,
Christophe-Marie

[1]: https://developer.amazon.com/docs/fire-tv/remote-input.html

On Wed, Jan 9, 2019 at 12:07 AM Christophe-Marie Duquesne <chmd@chmd.fr>
wrote:

> Looks like the intent com.wireguard.android.action.SET_TUNNEL_UP does not
> do much. I tried to start the tunnel like this:
>
> am broadcast -a com.wireguard.android.action.SET_TUNNEL_UP -e tunnel wg0
> -n com.wireguard.android/.model.TunnelManager
>
> After further investigation, the code to handle this intent is deactivated
> [1]. Any help would be appreciated!
>
> [1]:
> https://git.zx2c4.com/wireguard-android/tree/app/src/main/java/com/wireguard/android/model/TunnelManager.java#n275
>

[-- Attachment #1.2: Type: text/html, Size: 2302 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-01-09 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 10:26 [Android] Wireguard on the Amazon FireTV stick Christophe-Marie Duquesne
2019-01-08 10:47 ` Kalin KOZHUHAROV
2019-01-08 12:53   ` Christophe-Marie Duquesne
2019-01-08 23:07     ` Christophe-Marie Duquesne
2019-01-09 18:11       ` Christophe-Marie Duquesne [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='CAHLp1Y=kj0Lq0SpFbgh5M-QkphChkZsNd+U9SN5QoSOdF60O4Q@mail.gmail.com' \
    --to=chmd@chmd.fr \
    --cc=me.kalin@gmail.com \
    --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).