Comment # 12 on bug 1204869 from
Just discovered something important for this ticket:

The created VPN crashes when the offered certificate is detected as being
invalid. 

Explanation:

The CISCO VPN device I use to connect to, has a valid certificate signed for a
specific domain. Lets name it domain.com.

If the new VPN profile is created with IP as a Gateway value, instead the
domain.com as the Gateway value, the behavior is the one I described, the NM
crashes, even though I consent that I accept the invalid certificate ! 
See: openconnect-ciscoAnyConnect-VPN.png

If the new VPN profile is created with domain.com as the Gateway value (the
domain the certificate was created/signed for) the connection works !

The other issue (All users may connect to this network) stays.

So to conclude: I guess introducing "All users may connect to this network" is
not causing the NM to crash. Accepting the invalid certificate cause the NM to
crash.

Also the NM seems to crash in such a way that no other connection works
anymore. Whatever I am trying to connect to, using NM, results in nothing
happening. No reaction from the NM. The only thing I get in logs is the line
regards to agent not being present.

After a NM crash, if I open NM setting and click on whatever connect (to edit)
I get an error: See system_error_multiple.png

If I try to delete a connection I also get an error: See
system_error_after_failed_VPN_connection.png


You are receiving this mail because: