Subscribe to our Mailing List Follow Us on Facebook Follow Us on Twitter

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Login with Facebook Sign In with OpenID Sign In with Twitter
Sign In Apply for Membership

Categories

In this Discussion

Who's Online (0)

Cisco VPN - Stops being able to connect
  • Vote Up0Vote Down cpandarcpandar
    Hello,

    I have an issue where Shimo will be unable to connect to our university's Cisco VPN. Not only that, but it seems to interfere with the OS X built-in VPN client, so that will no longer connect either. Quitting/restartign Shimo does not solve the problem. I don't know what's causing it, how can I help debug this? So far I have found that restarting the machine allows both clients to connect again. I believe the problem is related to Shimo, as I've been using the OS X built-in client for months with no issues, and the problem started Monday after I installed Shimo. 

    Happy to provide any information that would be helpful. But as it stands, this is completely unusable, and I may have to uninstall Shimo.

  • Vote Up0Vote Down cpandarcpandar
    As an addendum - logging out of the machine and logging back in does not solve the problem. Restarting seems to.

    I don't really want to run Shimo now because I don't want to be locked out of my VPN connection again, I lose a lot of time if I have to restart the machine periodically...
  • Vote Up0Vote Down FabianFabian
    Have you tried to use vpnc as the profile's backend?
  • Vote Up0Vote Down cpandarcpandar
    Actually, that seems to be the one selected in the profile. Should I try switching to Mac OS X Internal?
  • Vote Up0Vote Down cpandarcpandar
    Well, tried using Shimo with the Mac OS X Internal as the backend method... that actually seemed less reliable, and eventually (after ~2 hours) neither Shimo nor the built-in client was able to connect to the VPN.

    Restarted, and am back to using the OS X built-in client, which still works.
  • Vote Up0Vote Down cpandarcpandar
    Hi Fabian, any ideas? Or do you have a version that would be more useful for debugging this problem? I'm in OS X 10.7.4 on a 15-inch MBP.
  • Vote Up0Vote Down cpandarcpandar
    Anything? The software is currently completely unusable.
  • Vote Up0Vote Down FabianFabian
    Please try the following version: https://www.dropbox.com/s/ymjvyuhnc1pzmwb/Shimo.zip
  • Vote Up0Vote Down lansinglansing
    I was having similar difficulty with this and tried the above version.

    Previous behavior:  Says connected, but no utun interface.

    New behavior:  Says CONNECTED_NOT_I, still no utun.

    Also, it breaks the internal VPN... this is horrible.
  • Vote Up0Vote Down cpandarcpandar
    With this new version, I ran into the case where Shimo wouldn't connect, and it my internal VPN was unable to connect as well. 

    Shimo was displaying the following:
    Shimo could not load its tun/tap kernel extensions, which are required by the used VPN protocol. Maybe you have some other VPN software running, which uses similar kernel extensions?

    (no other connections were actively running)

    When I tried to run OS X's internal VPN, I got the following

    An unrecoverable error occurred. Verify your settings and try reconnecting.

    (this error persisted even after I closed Shimo).


    Had to restart my system to get connections back.

    Seems possible that Shimo is not unloading kernel extensions properly on some disconnects, and this prevents Shimo and the internal connection from being able to reconnect. Is there anyway to force Shimo to unload all kernel extensions...?

  • Vote Up0Vote Down FabianFabian
    Can both of you please send me your log files, which can be found in Shimo's statistics window when you try to connect...
  • Vote Up0Vote Down cpandarcpandar
    So far I've only had one recent issue where Shimo was unable to connect. In that case, the program became unresponsive, and gradually took up more and more memory until about 3Gb, when I had to force-close it. Because it was unresponsive, I couldn't get a log file. Will send a log file next time I can. Thanks.
  • Vote Up0Vote Down cpandarcpandar
    Hi Fabian, had another incident occur. Am pasting the contents of the error log (with sensitive info XXX'd out of course).

    I'm pretty sure this has to do with switching networks without disconnecting the connection. In this case, I suspended my laptop on one network, brought it home, then resumed (on a different network) and got the following:

    2012-07-23 21:52:12 State changed to: Contacting
    2012-07-23 21:52:12 Enter IPSec secret for XXX@XXX.XX.1.253: 
    2012-07-23 21:52:12 Enter password for XXX@XXX.XX.1.253: 
    2012-07-23 21:52:12 vpnc version 0.5.3
    2012-07-23 21:52:12 ERROR: can't send packet: Can't assign requested address

  • Vote Up0Vote Down cpandarcpandar
    And just to be clear, as with other times, OS X internal VPN is also unable to connect.
  • Vote Up0Vote Down FabianFabian
    You might be correct with your assumption that it is related to a failed disconnection process when you suspended your laptop. I will look into the sleep process again...
  • Vote Up0Vote Down cpandarcpandar
    Any insight?
  • Vote Up0Vote Down cpandarcpandar
    Still having these problems using the latest Shimo version. 

    2012-08-17 09:41:37 State changed to: Contacting
    2012-08-17 09:41:37 Enter IPSec secret for XXX@XXX.XXX1.253: 
    2012-08-17 09:41:37 Enter password for XXX@XXX.XXX.1.253: 
    2012-08-17 09:41:37 vpnc version 0.5.3
    2012-08-17 09:41:37 ERROR: can't send packet: Can't assign requested address

    I believe this is still related to the sleep process. And, as usual, this disables my internal VPN connection.

    Please let me know if you plan to fix this issue. Fabian, this has been a major inconvenience for me, and I'm surprised that despite our long forum discussion over more than a month, there is still no resolution and little apparent progress... I don't mean to be rude, but I'm perfectly willing to help troubleshoot this problem, but have received little feedback from your end. At this point Shimo was a waste of time and money from my standpoint.

  • Vote Up0Vote Down FabianFabian
    Just for clarification: You can connect with Shimo to your VPN server. When you then send your computer to sleep and afterwards wake it up again, Shimo tries to reconnect and then you are getting this error message?!
  • Vote Up0Vote Down cpandarcpandar
    Yes, that is correct. I don't know if the problem occurs otherwise, but that is a reproducible way to cause the problem.

    The reason it's a big issue is that if I ever forget to disconnect Shimo before I sleep my laptop, when I resume, my VPN connection is unusable until I restart the computer.. and that is far more of a loss of productivity than anything I gained from using Shimo.

    Thank you for looking into it.
  • Vote Up0Vote Down cpandarcpandar
    No ideas?
  • Vote Up0Vote Down FabianFabian
    I have to do some testing on my side again. Normally Shimo should disconnect before it allows the computer to go to sleep and the reconnect upon wake-up.
    It seems that the disconnecting process does not finish and leaves the connection in an undefined state, which does not allow for easy reconnection on wake...
  • Vote Up0Vote Down cpandarcpandar
    Got it. Is there a way of just forcing Shimo to reset the connection when faced with this error?
  • Vote Up0Vote Down cpandarcpandar
    Did you do any testing regarding this issue?
  • Vote Up0Vote Down FabianFabian
    Yes, but for me it was working flawlessly. You could try to increase the reconnection delay in Shimo's advanced preferences...
  • Vote Up0Vote Down jondevitojondevito
    Mine doesn't work 99% of the time anymore. All of these problems started happening after the last update. Sometimes after a shutdown I can get it to work, most of the time not anymore though. This last update has been nothing but trouble for me.

    Jon
  • Vote Up0Vote Down jondevitojondevito
    PS - It got much worse after Mountain Lion upgrade.

    Jon
Add a Comment
 
Quality Software Made in Aachen, Germany