Subnet clarity & auto connect

Got a problem with Viscosity or need help? Ask here!

k41zen

Posts: 5
Joined: Sun Aug 23, 2009 7:16 pm

Post by k41zen » Sun Aug 23, 2009 7:22 pm
I'm trying to configure Viscosity to send 5 class C subnets through the VPN and everything else through my default gateway.

When I do this everything is getting sent through the VPN. I've configured them leaving the gateway fields blank or using vpn_gateway but still the same.

I take it the "send all traffic through the VPN" option overwrites anything in the route list?

I'm also trying to configure this to reconnect the VPN after the MAC wakes up. How does Viscosity monitor this and understand if the connection was active before the MAC goes to sleep? Does the "overwrite NIC on disconnect" affect this setting?

TIA

k41zen

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Wed Sep 16, 2009 3:47 am
Hi k41zen,
I take it the "send all traffic through the VPN" option overwrites anything in the route list?
The option simply triggers OpenVPN's "redirect-gateway def1" command, which sets the default route. It shouldn't overwrite any of your custom routes. However by the sound of it you want this option turned off. You'll also need to make sure the OpenVPN server isn't sending the redirect-gateway command as well (which will override Viscosity's setting).
I'm also trying to configure this to reconnect the VPN after the MAC wakes up. How does Viscosity monitor this and understand if the connection was active before the MAC goes to sleep? Does the "overwrite NIC on disconnect" affect this setting?
Viscosity simply listens for when the computer is about to go to sleep and disconnects the connection, and stores the connections that were active in memory. When the computer wakes back up, Viscosity reconnects these connections. I'm unsure what you are referring to by "overwrite NIC on disconnect", however generally network changes should be fine.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

k41zen

Posts: 5
Joined: Sun Aug 23, 2009 7:16 pm

Post by k41zen » Wed Sep 16, 2009 6:41 am
James,

Thanks for the reply. I can confirm that the reconnection option doesn't work for me when the Mini wakes back up.

k41zen

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Sat Sep 19, 2009 1:09 am
I can confirm that the reconnection option doesn't work for me when the Mini wakes back up.
Are you running Leopard, or Snow Leopard? Does Viscosity try and reconnect the connection when your computer wakes up (i.e. does the icon start moving/spinning)? And finally, make sure the "Reconnect active connections on wake" option is ticked under Preferences->General.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

k41zen

Posts: 5
Joined: Sun Aug 23, 2009 7:16 pm

Post by k41zen » Tue Oct 27, 2009 10:53 pm
James,

Sorry for the delay.

I'm running Leopard. Viscosity doesn't attempt to connect and the option "Reconnect active connections" is already ticked.

The problem still occurs. Viscosity doesn't attempt to re-connect the VPN after its woken up.

K41zen

k41zen

Posts: 5
Joined: Sun Aug 23, 2009 7:16 pm

Post by k41zen » Tue Oct 27, 2009 11:00 pm
One thing I have noticed though is that when I wake up my Mini it comes up and then goes back to sleep after about 5 seconds. I have no idea why this is.

Could it be that Viscosity is trying to re-connect the first time but then after the machine sleeps the second time it doesn't try to connect again?

Update: OK so it seems the wake up issue is related to Plex and its Energy Saving settings. I've turned these off and set the OS to handle this.

I'll test and see if this has anything to do with the VPN reconnect issue.

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Sun Nov 01, 2009 6:57 am
One thing I have noticed though is that when I wake up my Mini it comes up and then goes back to sleep after about 5 seconds. I have no idea why this is.
Yes, this sounds like the cause. Viscosity typically waits a little while after the computer has woken up (to make sure all AirPort and other network interfaces have come online) before reconnecting any connections. However if your computer is put back to sleep within this time then technically there were no active connections when the computer went to sleep, and hence nothing is re-connected when the computer wakes up the second time.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

k41zen

Posts: 5
Joined: Sun Aug 23, 2009 7:16 pm

Post by k41zen » Sun Nov 01, 2009 10:49 pm
This was the cause of my problem. I've disabled the power saving options in Plex and let the OS handle it.

Now when I wake up my machine it stays up AND the Viscosity does its job and re-establishes the VPN. Sweet :P

Thanks for your help.
8 posts Page 1 of 1