search

madscientist / msjnc

MadScientist Juniper Network Connect Session Manager
MIT License
69 stars 20 forks source link

status detection based on ncsvc.log is too brittle and should be implemented differently #5

Closed vorburger closed 11 years ago

vorburger commented 11 years ago

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!!

xaptronic commented 11 years ago

I had the same problem which this post helped to resolve. Might be a good contribution to a wiki.

madscientist commented 11 years ago

This should be fixed now. Please try version 2.5.