I’m just starting to try nethsecurity beta1 (new install of beta1 update to 8-23.05.2-ns.0.0.1-beta1-10-g355c764) but I’m having problems with openvpn roadwarrior with local users:
AUTH: Received control message: AUTH_FAILED
but i’m quite sure of user/pass and i’ve had no problems with the alpha2
I hope to have some time tomorrow to do more tests, but in the meantime does anyone had the same problem?
tnx
forgot to say: I think that the port choice didn’t work (stuck on 1194, if I remember well also in alpha).
Did you update the machine from Alpha 1 or it is a clean installation?
From Alpha1, the Roadwarrior server has been almost completely rewritten so old configuration does not fit.
clean install, i’ve made a new install to be sure… same problem with
NethSecurity 8-23.05.2-ns.0.0.1-beta1 and
NethSecurity 8-23.05.2-ns.0.0.1-beta1-17-g8b7f385
root@NethSec:~# grep ns_roadwarrior1 /var/log/messages
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 TLS: Initial packet from [AF_INET]>IP<.4:5216 (via [AF_INET]>IP<%eth1), sid=97a8ac6b 9fc24bd3
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 VERIFY OK: depth=1, CN=NethSec
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 VERIFY OK: depth=0, CN=testov1
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 peer info: IV_VER=2.6.3
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 peer info: IV_PLAT=linux
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 peer info: IV_TCPNL=1
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 peer info: IV_MTU=1600
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 peer info: IV_NCP=2
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 peer info: IV_CIPHERS=AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 peer info: IV_PROTO=990
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 peer info: IV_LZO_STUB=1
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 peer info: IV_COMP_STUB=1
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 peer info: IV_COMP_STUBv2=1
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 WARNING: Failed running command (–auth-user-pass-verify): external program exited with error status: 1
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 TLS Auth Error: Auth Username/Password verification failed for peer
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 WARNING: ‘link-mtu’ is used inconsistently, local=‘link-mtu 1549’, remote=‘link-mtu 1553’
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 WARNING: ‘auth’ is used inconsistently, local=‘auth [null-digest]’, remote=‘auth SHA256’
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 WARNING: ‘keysize’ is used inconsistently, local=‘keysize 256’, remote=‘keysize 128’
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256
Feb 5 17:09:57 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 [testov1] Peer Connection Initiated with [AF_INET]>IP<:5216 (via [AF_INET]>IP<%eth1)
Feb 5 17:09:58 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 PUSH: Received control message: ‘PUSH_REQUEST’
Feb 5 17:09:58 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 Delayed exit in 5 seconds
Feb 5 17:09:58 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 SENT CONTROL [testov1]: ‘AUTH_FAILED’ (status=1)
Feb 5 17:10:03 NethSec openvpn(ns_roadwarrior1)[4465]: >IP<:5216 SIGTERM[soft,delayed-exit] received, client-instance exiting
Edit: you can also apply the fixes from the Updates page without flashing the whole system. But in this case you need to setup again the user password.
yes it’s all working (chaged port, firewall rule updated, new config ok)
probably not so important but it is possible to set TCP/443, so unless you are going to implement something like sslh I guess it should be denied or written in docs or maybe nobody will ever put openvpn on 443
I’d rather to not block such configurations: maybe sometime you may really need to setup OpenVPN on port 443 to bypass some strange rule on restricted networks