* wireguard-android: Unable to import tunnel: invalid name
@ 2019-12-16 5:57 Dirk Kaiser
2019-12-16 7:36 ` Jason A. Donenfeld
0 siblings, 1 reply; 2+ messages in thread
From: Dirk Kaiser @ 2019-12-16 5:57 UTC (permalink / raw)
To: wireguard
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.
- GeoDirk
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: wireguard-android: Unable to import tunnel: invalid name
2019-12-16 5:57 wireguard-android: Unable to import tunnel: invalid name Dirk Kaiser
@ 2019-12-16 7:36 ` Jason A. Donenfeld
0 siblings, 0 replies; 2+ messages in thread
From: Jason A. Donenfeld @ 2019-12-16 7:36 UTC (permalink / raw)
To: Dirk Kaiser; +Cc: WireGuard mailing list
[-- 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-12-16 7:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-16 5:57 wireguard-android: Unable to import tunnel: invalid name Dirk Kaiser
2019-12-16 7:36 ` Jason A. Donenfeld
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).