All of lore.kernel.org
 help / color / mirror / Atom feed
From: Davide Depau <davide@depau.eu>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Issues with WireGuard on Android (with kernel module)
Date: Fri, 04 May 2018 09:49:31 +0000	[thread overview]
Message-ID: <CAMp63jVrpgfL4tGXvbk=9zCHYG4-Te3+1NF_HGexAMVW6dTisg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pDYf0AwnW3G85WTycOB=RHFKc_CymvEmN3dBO23cF9Ug@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 906 bytes --]

Hi Jason,
I've already extracted the configs generated by the app: my phone is rooted
and I found them in /data.
Anyway I learned a few days ago that my university's wifi blocks traffic by
protocol: though the UDP port I'm using for WireGuard I'm using is
technically open, their firewall apparently analyzes the frames and,
finding unexpected encrypted traffic, filters it.
I'll change the server port to OpenVPN's, which is also open and hopefully
won't look suspicious, and do some more checks.

Thank you
Davide

On Mon, Apr 30, 2018 at 7:34 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Hi Davide,
>
> It's possible you mixed up the keys in the config. The next version of
> the Android app, which should be out soon, will have the ability to
> export configs to .zip files, so you'll be able to test your
> configuration on your computer, to verify that the problem is not
> Android.
>
> Jason
>

[-- Attachment #2: Type: text/html, Size: 1285 bytes --]

      reply	other threads:[~2018-05-04  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 13:24 Issues with WireGuard on Android (with kernel module) Davide Depau
2018-04-30 17:34 ` Jason A. Donenfeld
2018-05-04  9:49   ` Davide Depau [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='CAMp63jVrpgfL4tGXvbk=9zCHYG4-Te3+1NF_HGexAMVW6dTisg@mail.gmail.com' \
    --to=davide@depau.eu \
    --cc=Jason@zx2c4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.