Push "dhcp-option …" aren't pulled by Tunnelblick, but Viscosity!!
-
Hi all,
I've set the following options:
push "dhcp-option DOMAIN bad-nauheim.xxx.de" push "dhcp-option DNS 192.168.115.1" push "dhcp-option WINS 192.168.115.18" push "dhcp-option NTP 192.168.115.1" push "dhcp-option NBT 1"
and
push "route 192.168.115.0 255.255.255.0"
but none of the first one's get pulled…
This is my client.ovpn I use with Tunnelblick:
tls-client client pull dev tun proto udp tun-mtu 1400 tun-mtu-extra 32 ping 10 resolv-retry infinite nobind remote xxx.de 1194 ca ca.crt cert macbook-pro.crt key macbook-pro.key cipher AES-128-CBC comp-lzo verb 5 ns-cert-type server
I hope one of U has hint to solve this problem!
Edit:
Mon 11/03/08 10:20 PM: IMPORTANT: OpenVPN's default port number is now 1194
Mon 11/03/08 10:20 PM: LZO compression initialized
Mon 11/03/08 10:20 PM: WARNING: normally if you use –mssfix and/or --fragment
Mon 11/03/08 10:20 PM: Control Channel MTU parms [ L:1490 D:138 EF:38 EB:0 ET:0 EL:0 ]
Mon 11/03/08 10:20 PM: Data Channel MTU parms [ L:1490 D:1450 EF:58 EB:135 ET:32 EL:0 AF:3/1 ]
Mon 11/03/08 10:20 PM: Local Options String: 'V4
Mon 11/03/08 10:20 PM: Expected Remote Options String: 'V4
Mon 11/03/08 10:20 PM: Local Options hash (VER=V4): '1453c8cd'
Mon 11/03/08 10:20 PM: Expected Remote Options hash (VER=V4): '74806bf0'
Mon 11/03/08 10:20 PM: Socket Buffers: R=[42080->65536] S=[9216->65536]
Mon 11/03/08 10:20 PM: UDPv4 link local: [undef]
Mon 11/03/08 10:20 PM: UDPv4 link remote: xxx:1194
Mon 11/03/08 10:20 PM: TLS: Initial packet from xxx:1194
Mon 11/03/08 10:20 PM: VERIFY OK: depth=1
Mon 11/03/08 10:20 PM: VERIFY OK: nsCertType=SERVER
Mon 11/03/08 10:20 PM: VERIFY OK: depth=0
Mon 11/03/08 10:20 PM: Data Channel Encrypt: Cipher 'AES-128-CBC' initialized with 128 bit key
Mon 11/03/08 10:20 PM: Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon 11/03/08 10:20 PM: Data Channel Decrypt: Cipher 'AES-128-CBC' initialized with 128 bit key
Mon 11/03/08 10:20 PM: Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon 11/03/08 10:20 PM: Control Channel: TLSv1
Mon 11/03/08 10:20 PM: [router] Peer Connection Initiated with 217.91.96.41:1194
Mon 11/03/08 10:20 PM: SENT CONTROL [router]: 'PUSH_REQUEST' (status=1)
Mon 11/03/08 10:20 PM: PUSH: Received control message: 'PUSH_REPLY
Mon 11/03/08 10:20 PM: OPTIONS IMPORT: timers and/or timeouts modified
Mon 11/03/08 10:20 PM: OPTIONS IMPORT: –ifconfig/up options modified
Mon 11/03/08 10:20 PM: OPTIONS IMPORT: route options modified
Mon 11/03/08 10:20 PM: OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Mon 11/03/08 10:20 PM: gw 192.168.0.1
Mon 11/03/08 10:20 PM: TUN/TAP device /dev/tun0 opened
Mon 11/03/08 10:20 PM: /sbin/ifconfig tun0 delete
Mon 11/03/08 10:20 PM: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
Mon 11/03/08 10:20 PM: /sbin/ifconfig tun0 10.0.115.6 10.0.115.5 mtu 1400 netmask 255.255.255.255 up
Mon 11/03/08 10:20 PM: /sbin/route add -net 192.168.115.0 10.0.115.5 255.255.255.0
Mon 11/03/08 10:20 PM: /sbin/route add -net 10.0.115.0 10.0.115.5 255.255.255.248
Mon 11/03/08 10:20 PM: Initialization Sequence Completed
End of Edit!Greetz
MircsiczP.S.: Again answering myself: I tried another app from www.viscosityvpn.com, it works like a charm! Think I'll buy it for 9$...
-
-
Thanks a ton for the URL, Viscosity contains an opensource python script which does something similar, but not the MacOS way, it creates an entry in /etc/resolv.conf… And if I don't need to bay an app..!!!
So I'll try the way it's described and go on using Tunnelblick...
Greetz
Mircsicz -
Just for your information. I found a much easier fix for this problem with Tunnelblick. Apply the small patch from http://code.google.com/p/tunnelblick/issues/detail?id=8#c10 and everything works fine.