>> >> Is there at least an explanation for this and an easier way to fix this >> problem after it happened (I will probably not be able to avoid making >> this mistake again some time)? > > You could install the NetworkManager-openconnect package (see bug > #729085) and then you wouldn't have to run it from the command line in > the first place? > Also, wouldn't starting it in the background with the -b flag allow it to fork and not be tied to the controlling terminal anymore, thus avoiding the problem of accidentally closing the terminal? You would then have to explicitly kill the process to close the VPN connection, of course. -Paul
