It appears that the status message is just due to the file $HOME/.pulse_secure/pulse/.pulse_status that was left there. It appears that the connection has been terminated but the status message was not cleared. I manually renamed the .pulse_status file to another file name. Not sure if that is a good permanent fix or if it will cause problems in the future.
... View more
I used full tunneling on Ubuntu using pulsesecure (not thinking through it, as I was remotely via VPN connected to the Ubuntu system from home ), and it of course cut off all the connections to the outside world after establishing the full tunnel VPN connection. A system engineer visited my office, and was able to power cycle it. After that I was able again to use ssh to connect to the Ubuntu machine from home, but the full tunnel VPN session I tried earlier (and caused the disconnections as detailed above) was still active, and allowed no outgoing connections from the Ubuntu. After overwriting the /etc/resolv.conf file on the Ubuntu with appropriate information. I was able to connect from the Ubuntu to outside world again. However, when I now run "/usr/local/pulse/PulseClient.sh -S" on the Ubuntu, I get "connection status : Connected", information about bytes sent out and received, "Connection Mode : ESP", "Encryption Type : AES256/SHA1", "Comp Type : None", "Assigned IP : xxx.xxx.xxx.xx" (I removed the IP digits here). So there is a hanging runaway full tunnel VPN connection that I cannot kill. I tried "/usr/local/pulse/PulseClient.sh -K" or "Kill" instead of "K" and nothing appears to change, because when I type the PulseClient.sh status command ("-S"; as above), I get the same information as above. How do I kill/terminate this runaway full tunnel pulsesecure connection on my Ubuntu?
... View more