dlmc
Junior Member
Posts: 10
Joined: Oct 2013
|
RE: T21P OpenVPN
Hmm that makes no sense, the security data is meant to be private. I would need to generate a new CA and CLIENT certs to attach something.
The Yealink OpenVPN instructions are great and all, but what they really should consist of is a breakdown of the TAR file contents (with a working sample provided by Yealink) that can be used to prove an initial working state.
There is no clear indication of what feature set of OpenVPN is supported, like OpenVPN base version, what crypto support and version.
The instructions on how to compile kernels and OpenVPN and such are actually not very useful. I would not think many people do this but use a package manager to install openvpn.
The Web UI feedback about the upload of the file being successful is also not as useful a knowing the file uploaded, was processed and the contents found acceptable to install and then the installation succeeding.
The only thing in the syslog output is:
2014-11-12T15:52:45.432996+00:00 Log [357]: WEB <6+info > Upload VPN file success!
The other matter preventing enablement of OpenVPN support, after doing:
Login to Yealink T21P
Network -> Advanced
VPN [Upload VPN Config ... Browse]
Select the local path to the openvpn.tar file.
Click "Upload"
Get back browser alert dialog on screen "Upload VPN file success!" click "OK"
Click "OK" on the browser dialog above.
The web page now refreshes and reloads.
The problem here is that selecting
Network -> Advanced
VPN -> Active: Enabled
Clicking "Confirm"
Results in browser alert dialog "Please upload VPN config file first!"
This seems like JavaScript preventing the enable from being set. But due to the page reload between uploading the openvpn.tar and setting Active:Enabled it does not seen possible to enable it.
If I preform a system backup (Settings -> Configuration -> Export) the resulting "config.bin" file which is also a TAR file.
I can see my files with correct timestamp and file lengths in relation to my files, these are like factory/openvpn/vpn.conf and such.
Also note the ownership I set to root (uid=0) and root (gid=0) just in case there was an issue in that area.
Also the standard file permissions exist on the files, that is mode=0664 for vpn.conf, mode=0640 for *.crt and mode=0600 for *.key these are standard file system permissions for the files when they are created.
Providing the Yealink kernel runs openvpn client software as 'root' then everything should be fine.
(This post was last modified: 11-13-2014 03:32 AM by dlmc.)
|
|
11-13-2014 03:10 AM |
|