From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Dirk Kaiser <dirk@gtt.tools>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard-android: Unable to import tunnel: invalid name
Date: Mon, 16 Dec 2019 08:36:14 +0100 [thread overview]
Message-ID: <CAHmME9oNDuoT=8r7nMFdL9_njrBoYuiAUx3vAD46tjaiWf1uNA@mail.gmail.com> (raw)
In-Reply-To: <e391693c-d4c4-91a0-6ebc-72a038d95a6b@gtt.tools>
[-- Attachment #1.1: Type: text/plain, Size: 902 bytes --]
On Mon, Dec 16, 2019, 06:57 Dirk Kaiser <dirk@gtt.tools> wrote:
> I've created the following client configurations with the following
> filenames:
>
> brat.batyr_LS.US_test.conf <==kicks off error
> pkds_LS.US_test.conf <==imports fine
> y_LS.US_test.conf <==imports fine
> zarina_LS.US_test.conf <==kicks off error
>
> On the Android client, the first and last filename generate the 'Unable
> to import tunnel: invalid name' when trying to import. The other two
> come import just fine. If I rename the two problem files to something
> else (i.e., brat.batyr.conf and zarina.conf), they import just fine.
> There obviously is a bug in the filename handling that needs to be fixed.
>
"Obviously", eh?
It's a length restriction, actually. We take the kernels interface name
length (and format) restrictions to retain parity of configs for both the
wgquick backend and the go backend.
Jason
>
[-- Attachment #1.2: Type: text/html, Size: 1531 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-12-16 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 5:57 Dirk Kaiser
2019-12-16 7:36 ` Jason A. Donenfeld [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='CAHmME9oNDuoT=8r7nMFdL9_njrBoYuiAUx3vAD46tjaiWf1uNA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=dirk@gtt.tools \
--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).