Not able to connect with 2 firewall-proxy/vpns at same time

[Essax]

I have multiple firewall-proxy/vpns setup as per the qubes docs. I have always been able to use more than one at the same time with out any problems connecting to my vpn providers servers. Starting a few day ago I am no longer able to connect with more than one firewall-proxy/vpn at a time.

I start and connect with vpn1 . I start vpn2 and it fails to connect. Then I start vpn2 from the CLI and this is the output I get everytime. ( I  just posted the important part at the end )

Mon Jul 31 17:20:43 2017 us=xxxxx Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1602,tun-mtu 1500,proto UDPv4,comp-lzo,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-client'

Mon Jul 31 17:20:43 2017 us=870023 Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1602,tun-mtu 1500,proto UDPv4,comp-lzo,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-server'

Mon Jul 31 17:20:43 2017 us=xxxxx TCP/UDP: Preserving recently used remote address: [AF_INET]xxxxxxxxxxx

Mon Jul 31 17:20:43 2017 us=870070 Socket Buffers: R=[212992->212992] S=[212992->212992]

Mon Jul 31 17:20:43 2017 us=870086 UDP link local: (not bound)

Mon Jul 31 17:20:43 2017 us=870101 UDP link remote: [AF_INET]xxxxxxxxxxxx

Mon Jul 31 17:20:43 2017 us=951538 TLS: Initial packet from [AF_INET]Server ip xxxxxxx, sid=xxxxxxxxxxxxx

Mon Jul 31 17:20:43 2017 us=951664 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

Mon Jul 31 17:20:44 2017 us=42751 VERIFY OK: nsCertType=SERVER

Mon Jul 31 17:20:44 2017 us=938100 NOTE: --mute triggered...

Mon Jul 31 17:20:44 2017 us=938181 1 variation(s) on previous 3 message(s) suppressed by --mute

Mon Jul 31 17:20:44 2017 us=938321 [server] Peer Connection Initiated with [AF_INET]xxxxxxxxxxxxxxxx

Mon Jul 31 17:20:45 2017 us=987500 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)

Mon Jul 31 17:20:46 2017 us=66601 AUTH: Received control message: AUTH_FAILED

Mon Jul 31 17:20:46 2017 us=66649 SIGTERM received, sending exit notification to peer

Mon Jul 31 17:20:49 2017 us=214365 TCP/UDP: Closing socket

Mon Jul 31 17:20:49 2017 us=214441 SIGTERM[soft,exit-with-notification] received, process exiting

If I were to shutdown vpn1, I would have no problems connecting with vpn2.

My vpn service provider also has a limited vpn service that is free of charge.  I configured a firewall-proxy/vpn with those configuration files and I could use that and one of my other proxy/vpns at the same time.  Taking into consideration the vpn logs and the fact that I can connect with the free service I'm leaning towards the problem being with my vpn provider.

I'm going to start a support ticket with my provider but I wanted to hear if anyone else thought as I do or if there could be another problem I'm not seeing in the logs.

Thanks in advance 

Essax

Sent with ProtonMail Secure Email.

[Chris Laprise]

On 07/31/2017 07:54 PM, 'Essax' via qubes-users wrote:

>> AUTH: Received control message:
>> AUTH_FAILED

This sounds like an issue with the provider. If they ask for more detail
you can set '--verb 5' for more verbosity from openvpn.

--

Chris Laprise, tas...@openmailbox.org
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886