The way in which msjnc currently detects connection status at start-up by parsing ncsvc.log is too brittle:
In a situation where your box crashes / you have to hard reset restart while the VPN is connected up and running (and so ncsvc.log is not clean anymore), when you restart and relaunch msjnc it insists that you are still connected (which of course you are not anymore after an OS restart), and whatever you do does it not manage to let you disconnect to force clear it's state so that you can then connect again.
The "workaround" I found after reading the msjnc Perl source is to just rm ~/.juniper_networks/network_connect/ncsvc.log - easy once you know about it... ;-) But a frustrating hour before that.
Sorry for only ranting and not actually proposing a patch! Hopefully just feedback instead actual code is a (small) form of contribution as well... Thank You for msjnc!!
The way in which msjnc currently detects connection status at start-up by parsing ncsvc.log is too brittle:
In a situation where your box crashes / you have to hard reset restart while the VPN is connected up and running (and so ncsvc.log is not clean anymore), when you restart and relaunch msjnc it insists that you are still connected (which of course you are not anymore after an OS restart), and whatever you do does it not manage to let you disconnect to force clear it's state so that you can then connect again.
The "workaround" I found after reading the msjnc Perl source is to just rm ~/.juniper_networks/network_connect/ncsvc.log - easy once you know about it... ;-) But a frustrating hour before that.
Sorry for only ranting and not actually proposing a patch! Hopefully just feedback instead actual code is a (small) form of contribution as well... Thank You for msjnc!!