FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
203 views 2 comments
by anonymous

Not sure if this is the place to report bugs, but didn't find any better, so here I am.

In the script /etc/openvpn/auth-pam.sh, there are the following lines.

ovpn_inst=$(echo $config | sed 's/openvpn-//g' | sed 's/.conf//g')
auth_file="/etc/openvpn/auth_$ovpn_inst"

As $config points to the full path of the config file, the result of the consecutive sed invocations is that ovpn_inst becomes equal to /var/etc/<name of the openvpn config>.

As a result auth file assumes the value of /etc/openvpn/auth_/var/etc/home_vpn. At a later point the script checks if the file pointed by $auth_file exists and naturally /etc/openvpn/auth_/var/etc/<name of the openvpn config> does not exist, so it's impossible to authenticate with the TLS/Password method.

If the sed statements get fixed everything works fine.

1 Answer

0 votes
by anonymous
Hi,

Thank you for your feedback, but I got one more question before I can report this issue to RnD.

Did you find this on the latest 2.6 firmware?

EB.
by anonymous

The interface gives me firmware version RUTX_R_00.02.0 and fw build date 2020-12-31 10:38:24, so I suppose yes?

by anonymous
Thank you for your feedback.

Will report this to RnD.

EB.