Search found 13 matches

Search found 13 matches Page 1 of 2
by MasterYous
Sat Oct 06, 2012 1:52 pm
Forum: Viscosity Support (Mac Version)
Topic: running scripts is hosed with 1.4.2
Replies: 4
Views: 5894

James, Appreciate the response. Based on what you advised, a little bit of background on what I am doing is warranted. I have heavily modified Viscosity 's DNS python scripts to support things like multiple domain suffix searching even when the options are negotiated via pure DHCP (no PUSH options b...
by MasterYous
Thu Oct 04, 2012 1:18 am
Forum: Viscosity Support (Mac Version)
Topic: running scripts is hosed with 1.4.2
Replies: 4
Views: 5894

Hey James - any update on this? Am I just missing something obvious? I still can't get any scripts to run, regdls of my script-security setting... and rgdls of whether or not I enable the 'advanced' scripts in the GUI.
by MasterYous
Sat Sep 29, 2012 3:03 pm
Forum: Viscosity Support (Mac Version)
Topic: running scripts is hosed with 1.4.2
Replies: 4
Views: 5894

Hi... I enabled advanced scripting using the new option in the GUI. I set script-security to 2 just as the log warned me... But I can no longer run scripts, period. With the version immediately prior of Viscosity, the script ran, but did not honor route-delay, so it was running as soon as TAP was op...
by MasterYous
Wed Aug 17, 2011 1:50 am
Forum: Viscosity Support (Mac Version)
Topic: Down Script Not Being Run
Replies: 7
Views: 8450

Hi MasterYous, Viscosity stopped using up/down scripts to implement DNS support as of version 1.3.0. DNS support is all handled internally by Viscosity now. The dnsdown.py scripts are only included for users automatically upgrading from version 1.2.3 to 1.3.x (so OpenVPN can still remove DNS settin...
by MasterYous
Fri Aug 12, 2011 4:01 am
Forum: Viscosity Support (Mac Version)
Topic: Down Script Not Being Run
Replies: 7
Views: 8450

I wanted to add my 2 cents to this. In a previous version of Viscosity, I did not have to manually specify the down command to get the dnsdown script to run - didn't Viscosity automatically run 'dnsdown.py' if you exited or disconnected? (provided you enabled DNS?) So I observed the same problem bei...
by MasterYous
Wed Jun 29, 2011 1:39 am
Forum: Viscosity Support (Mac Version)
Topic: 1.3.1 DHCP bugs
Replies: 8
Views: 8516

I've made some changes to the latest beta (1.3.2b7) to ensure DHCP will only ever be turned on after OpenVPN has set the MAC address. Give it a try and see how it goes. Thanks for your response, I will try this now and see if it helps either or both issues - I will post back. James - I am pleased t...
by MasterYous
Wed Jun 29, 2011 1:16 am
Forum: Viscosity Support (Mac Version)
Topic: 1.3.1 DHCP bugs
Replies: 8
Views: 8516

I've made some changes to the latest beta (1.3.2b7) to ensure DHCP will only ever be turned on after OpenVPN has set the MAC address. Give it a try and see how it goes.
Thanks for your response, I will try this now and see if it helps either or both issues - I will post back.
by MasterYous
Thu Jun 23, 2011 8:51 am
Forum: Viscosity Support (Mac Version)
Topic: 1.3.1 DHCP bugs
Replies: 8
Views: 8516

Hey James and team - I'm a long-time user (contributed to this community before with some DNS scripts) so you might remember me. Wanted to hop on and report two bugs I found while using 1.3.1 - one of which is a showstopper for someone using a pure DHCP configuration such as myself. Bug one - bad - ...
by MasterYous
Thu May 27, 2010 9:03 am
Forum: Goodies
Topic: SOLVED: multiple DNS server settings with *pure* DHCP/tap
Replies: 1
Views: 30296

Normally, if you are using DHCP with a bridged interface in OpenVPN (e.g. not using DHCP-OPTIONS or server-push), you will find that the DNS support scripts in OpenVPN cause problems for you - you will not get any DNS set, because the scripts rely on the aforementioned dhcp options being sent over f...
by MasterYous
Thu May 27, 2010 8:35 am
Forum: Viscosity Support (Mac Version)
Topic: [SOLVED] using TAP/DHCP - DNS not working
Replies: 5
Views: 8708

I would guess your problem was a timing problem. Because my method installs a delay on the route via the route-delay and up-delay commands, your negotiation of IP address probably had more time to complete so the routes are getting inserted in the right order. By the way, you can avoid the "two...
Search found 13 matches Page 1 of 2