Skip to content
Obviously you have the OpenVPN server pushing out an IP address AND a DHCP server on the remote network (or possibly it is assigning a self-assigned IP). While Mac OS X is perfectly happy to give a network interface multiple IP addresses, they've obviously clashed in your case.
Cheers,
James
Problem with redirect-gateway
Got a problem with Viscosity or need help? Ask here!
- Posts: 5
- Joined: Fri Feb 12, 2010 8:42 pm
Hello, I've a problem when using redirect-gateway option.
The connection starts, everything works fine. After few minutes, the system is not able to create new connections so I'm not able to use the network anymore. The old established connections keep on working.
It's not a VPN client/server settings problem as I tried the VPN connection with another openvpn client with the very same configuration and everything worked perfectly all the time.
I'm using Snow Leopard 10.6.2.
The connection starts, everything works fine. After few minutes, the system is not able to create new connections so I'm not able to use the network anymore. The old established connections keep on working.
It's not a VPN client/server settings problem as I tried the VPN connection with another openvpn client with the very same configuration and everything worked perfectly all the time.
I'm using Snow Leopard 10.6.2.
Hi gdigiacomo,
Try comparing the OpenVPN config file Viscosity is using with the copy you can confirm is working. Viscosity's config files can be found at: Your Home Folder/Library/Application Support/Viscosity/#/config.conf
You may also like to double check you don't have a DNS issue on your hands by following the troubleshooting information at:
http://www.viscosityvpn.com/support/?se ... pportid=14
Cheers,
James
Try comparing the OpenVPN config file Viscosity is using with the copy you can confirm is working. Viscosity's config files can be found at: Your Home Folder/Library/Application Support/Viscosity/#/config.conf
You may also like to double check you don't have a DNS issue on your hands by following the troubleshooting information at:
http://www.viscosityvpn.com/support/?se ... pportid=14
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
- Posts: 5
- Joined: Fri Feb 12, 2010 8:42 pm
Configuration is exactly the same as I loaded from the "working" client viscosity's configuration file.
I've already investigated about DNS problem but it's not the case...
Any other suggestion?
I've already investigated about DNS problem but it's not the case...
Any other suggestion?
Well routing is all handled by OpenVPN itself - Viscosity doesn't step in and change the routing table. If it is indeed a routing issue, you'd experience the same problem when kicking off your connection from the Terminal, for example with the following command:
/Applications/Viscosity.app/Contents/Resources/openvpn2.1 --config ~/Library/Application\ Support/Viscosity/OpenVPN/1/config.conf
If it's only happening with Viscosity, and not from the command line, try turning off DNS support for your connection (under the General tab when editing your connection). This will ensure Viscosity isn't monitoring for any DNS changes, only changes caused by a DHCP request.
If it's occurring from OpenVPN directly as well, you've either got a conflict on your machine, or you've run into something OpenVPN related (in which case you may like to post on the OpenVPN mailing list).
Cheers,
James
/Applications/Viscosity.app/Contents/Resources/openvpn2.1 --config ~/Library/Application\ Support/Viscosity/OpenVPN/1/config.conf
If it's only happening with Viscosity, and not from the command line, try turning off DNS support for your connection (under the General tab when editing your connection). This will ensure Viscosity isn't monitoring for any DNS changes, only changes caused by a DHCP request.
If it's occurring from OpenVPN directly as well, you've either got a conflict on your machine, or you've run into something OpenVPN related (in which case you may like to post on the OpenVPN mailing list).
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
- Posts: 5
- Joined: Fri Feb 12, 2010 8:42 pm
command-line OpenVPN client bundled with Viscosity works perfectly!!!
I've disabled the DNS support in my connection but same problem occours.
dunno what else to do
I've disabled the DNS support in my connection but same problem occours.
dunno what else to do
Is this by any chance a TAP based connection? If so a remote DHCP server could be overriding your IP address/routing. Try editing your connection in Viscosity and un-tick the "Enable DHCP" option.
Cheers,
James
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
- Posts: 5
- Joined: Fri Feb 12, 2010 8:42 pm
it's TAP and the IP doesn't override my IP address / routing
if that was the case, it didn't work at all! but it works for the first minutes, then hangs
and, since the configuration and the server are the same, openvpn command-line client wouldn't work too!
if that was the case, it didn't work at all! but it works for the first minutes, then hangs
and, since the configuration and the server are the same, openvpn command-line client wouldn't work too!
- Posts: 5
- Joined: Fri Feb 12, 2010 8:42 pm
by disabling "Enable DHCP" option it seems to work...
what precisely that function does?
what precisely that function does?
what precisely that function does?It allows Mac OS X to pull an IP address from a DHCP server (just like when you plug in a network cable or connect to a wireless network).
Obviously you have the OpenVPN server pushing out an IP address AND a DHCP server on the remote network (or possibly it is assigning a self-assigned IP). While Mac OS X is perfectly happy to give a network interface multiple IP addresses, they've obviously clashed in your case.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
9 posts
Page 1 of 1