Possible to convert Asus Router Generated client.ovpn to ca.crt, client.crt, client.key, and client.conf?

slazinger_7

I have an Asus RT-AC3100 router with OpenVPN server capabilities. When I "enable", I am able to "Export OpenVPN configuration file" as "client.ovpn.

On Windows 10, I can download OpenVPN Connect and import the client.ovpn file and connect to the Asus router with my username and password stored in OpenVPN Connect just fine.

The problem is that I have a VOIP phone that is requiring me to upload a "client.conf" file, along with a "keys" folder that contains the "ca.crt", "client.crt", and "client.key" files. I'm not sure how to create or generate these files from the Asus router, but I feel like you should be able to create each file individually based on the information in the client.ovpn file generated by the Asus router.

So, the question is: is there any way to create the client.conf, ca.crt, client,crt, and client.key files needed by the VOIP phone from the client.ovpn file that I can export from the Asus router?

If not, is there another way that I can connect the VOIP phone using client.conf, ca.crt, client,crt, and client.key files to my Asus router?

TinCanTech

Try renaming the .ovpn file to .conf

slazinger_7

I tried that already, and it didn't work. The VOIP phone is looking for those four files, and specifically as indicated in my original post.

I can't seem to paste a picture from the VOIP phone manual into this response so you can see what it's asking for, but you can see the requirements on pg. 91 if the following link:

https://cdn-media.vtechphones.com/media/p/document2/products/%7B6CB713AF-6887-4B6C-A32A-4821DE6DCE0D%7D/VTech_VSP726_Admin_Provisioning_Manual-Rev-2.pdf

TinCanTech

Then extract the files from the file you have from your router.

slazinger_7

I'm not sure how to do that. The exported Asus client.ovpn file includes the following information:

remote [IP ADDRESS REDACTED] 1194
float
nobind
proto udp
dev tun
sndbuf 0
rcvbuf 0
keepalive 10 30
comp-lzo adaptive
auth-user-pass
client
auth SHA1
cipher AES-128-CBC
remote-cert-tls server
<ca>

[REDACTED]

</ca>

<cert>

[REDACTED]

</cert>

<key>

[REDACTED]

</key>

Basically what I tried doing is this:

Copied all this information to a "client.conf" file:

remote [IP ADDRESS REDACTED] 1194
float
nobind
proto udp
dev tun
sndbuf 0
rcvbuf 0
keepalive 10 30
comp-lzo adaptive
auth-user-pass
client
auth SHA1
cipher AES-128-CBC
remote-cert-tls server

I copied the [REDACTED] key between <ca> and </ca> to new file: "ca.crt"
I copied the [REDACTED] key between <cert> and </cert> to a new file: "client.crt"
I copied the [REDACTED] key between <key> </key> to a new file: "client.key"

I loaded those into the a ".tar" file as requested by the VOIP phone manual and uploaded, but that didn't work.

I was looking at some of our older OpenVPN files, and it seems the client.crt file needs more information than just the certificate, but I could be wrong.

Moreover, when I use the client.ovpn file with OpenVPN Connect, there is a place to insert my username and password, which I haven't done in any of the above-mentioned files. So, even if the settings are correct, presumably, I still need to provide a username/password somewhere/somehow in those files.

TinCanTech

slazinger_7 wrote I copied the [REDACTED] key between <ca> and </ca> to new file: "ca.crt"
I copied the [REDACTED] key between <cert> and </cert> to a new file: "client.crt"
I copied the [REDACTED] key between <key> </key> to a new file: "client.key"

That is the correct data.

slazinger_7 wrote I loaded those into the a ".tar" file as requested by the VOIP phone manual and uploaded, but that didn't work.

Check you device manual.

slazinger_7 wrote Moreover, when I use the client.ovpn file with OpenVPN Connect, there is a place to insert my username and password, which I haven't done in any of the above-mentioned files. So, even if the settings are correct, presumably, I still need to provide a username/password somewhere/somehow in those files.

Maybe the device does not even allow for it, I don't support your device though ..