Opened 12 years ago

Closed 10 years ago

#196 closed Bug / Defect (fixed)

National characters in the connection name and tun-ipv6

Reported by: namiltd Owned by: Gert Döring
Priority: major Milestone: beta 2.3
Component: IPv6 Version: OpenVPN 2.3-beta / 2.3-RC (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords: unicode ascii


When the connection name contains national characters such as: "Połączenie lokalne VPN" will not initiate a connection tun-ipv6. There is an error:
Tue Feb 28 23:54:08 2012 NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 set address Połączenie lokalne VPN 2011:16a0:211:832::c421 store=active
Element not found.
Tue Feb 28 23:54:10 2012 ERROR: netsh command failed: returned error code 1

Change History (5)

comment:1 Changed 12 years ago by namiltd

I think that the problem stems from the lack of conversion of ANSI-> OEM and the lack of quotation marks in the parameters netsh.

comment:2 Changed 11 years ago by David Sommerseth

Owner: set to Gert Döring
Status: newassigned

comment:3 Changed 10 years ago by Samuli Seppänen

Keywords: unicode ascii added

comment:4 Changed 10 years ago by Gert Döring

Why was I owning that anyway? :-)

It *should* work with the fix from d12fk (8f5a4598662f4b2abe7acfe8f68c90a8b03f2dc8, "Support non-ASCII TAP adapter names on Windows").

namiltd: can you test with the openvpn installer on

comment:5 Changed 10 years ago by Gert Döring

Resolution: fixed
Status: assignedclosed

I'm closing the ticket now, as I assume the bug is fixed. If not, please tell us.

Note: See TracTickets for help on using tickets.