Problem: the second argument to --ifconfig must be an IP address. You are using something (255.255.255.0) that looks more like a netmask

[Ender Informatics]

Hello All

A clients openvpn server on Debian works fine with windows and iMac
clients.

But on a OS X 10.6.3 Macbook we run into the following issue: The
client connects successfully but gets a strange IP Configuration on
tun0

Log shows: the second argument to --ifconfig must be an IP address.
You are using something (255.255.255.0) that looks more like a
netmask.

We tried the stable release, current beta and old 2.x. All with the
same problem.

any help is very appreciated!
Josef Ender




full logs (IP replaced), server and client config:

Failed client:

2010-06-25 17:39:57 *Tunnelblick: OS X 10.6.3; Tunnelblick 3.1beta06
(build 1890); OpenVPN 2.1.1
2010-06-25 17:40:06 *Tunnelblick: Attempting connection with openvpn;
Set nameserver = 1; monitoring connection
2010-06-25 17:40:06 *Tunnelblick: /Applications/Tunnelblick.app/
Contents/Resources/openvpnstart start openvpn.conf 1337 1 0 0 0 97
2010-06-25 17:40:07 *Tunnelblick: /Applications/Tunnelblick.app/
Contents/Resources/openvpn --cd /Users/username/Library/Application
Support/Tunnelblick/Configurations --daemon --management 127.0.0.1
1337 --config /Users/username/Library/Application Support/Tunnelblick/
Configurations/openvpn.conf --management-query-passwords --management-
hold --script-security 2 --up /Applications/Tunnelblick.app/Contents/
Resources/client.up.tunnelblick.sh -m -w -d --down /Applications/
Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -m -w -d
--up-restart
2010-06-25 17:40:07 *Tunnelblick: Attached to pipe for scripts
2010-06-25 17:40:07 SUCCESS: pid=704
2010-06-25 17:40:07 SUCCESS: real-time state notification set to ON
2010-06-25 17:40:06
2010-06-25 17:40:07 END
2010-06-25 17:40:07 SUCCESS: real-time log notification set to ON
2010-06-25 17:40:06 OpenVPN 2.1.1 i386-apple-darwin10.3.0 [SSL] [LZO2]
[PKCS11] built on Jun 7 2010
2010-06-25 17:40:06 MANAGEMENT: TCP Socket listening on 127.0.0.1:1337
2010-06-25 17:40:06 waiting...
2010-06-25 17:40:07 MANAGEMENT: Client connected from 127.0.0.1:1337
2010-06-25 17:40:07 MANAGEMENT: CMD 'pid'
2010-06-25 17:40:07 MANAGEMENT: CMD 'state on'
2010-06-25 17:40:07 MANAGEMENT: CMD 'state'
2010-06-25 17:40:07 MANAGEMENT: CMD 'log on all'
2010-06-25 17:40:07 END
2010-06-25 17:40:07 MANAGEMENT: CMD 'hold release'
2010-06-25 17:40:07 SUCCESS: hold release succeeded
2010-06-25 17:40:07 NOTE: the current --script-security setting may
allow this configuration to call user-defined scripts
2010-06-25 17:40:07 MANAGEMENT: CMD 'password [...]'
2010-06-25 17:40:07 but not yet verified
2010-06-25 17:40:07 WARNING: this configuration may cache passwords in
memory -- use the auth-nocache option to prevent this
2010-06-25 17:40:07 WARNING: file 'username.key' is group or others
accessible
2010-06-25 17:40:07 LZO compression initialized
2010-06-25 17:40:07 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:
0 ET:0 EL:0 ]
2010-06-25 17:40:07 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:
135 ET:0 EL:0 AF:3/1 ]
2010-06-25 17:40:07 Local Options hash (VER=V4): '41690919'
2010-06-25 17:40:07 Expected Remote Options hash (VER=V4): '530fdded'
2010-06-25 17:40:07 Socket Buffers: R=[42080->65536] S=[9216->65536]
2010-06-25 17:40:07 UDPv4 link local: [undef]
2010-06-25 17:40:07 UDPv4 link remote: 84.253.xx.xx:1194
2010-06-25 17:40:07
2010-06-25 17:40:07
2010-06-25 17:40:07 sid=6af53d08 e0ed4cc0
2010-06-25 17:40:12 remote='dev-type tap'
2010-06-25 17:40:12 remote='link-mtu 1574'
2010-06-25 17:40:12 remote='tun-mtu 1532'
2010-06-25 17:40:12 Data Channel Encrypt: Cipher 'BF-CBC' initialized
with 128 bit key
2010-06-25 17:40:12 Data Channel Encrypt: Using 160 bit message hash
'SHA1' for HMAC authentication
2010-06-25 17:40:12 Data Channel Decrypt: Cipher 'BF-CBC' initialized
with 128 bit key
2010-06-25 17:40:12 Data Channel Decrypt: Using 160 bit message hash
'SHA1' for HMAC authentication
2010-06-25 17:40:12 1024 bit RSA
2010-06-25 17:40:12 [server] Peer Connection Initiated with
84.253.xx.xx:1194
2010-06-25 17:40:14
2010-06-25 17:40:15 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
2010-06-25 17:40:15 ifconfig 192.168.0.202 255.255.255.0'
2010-06-25 17:40:15 OPTIONS IMPORT: timers and/or timeouts modified
2010-06-25 17:40:15 OPTIONS IMPORT: --ifconfig/up options modified
2010-06-25 17:40:15 OPTIONS IMPORT: route-related options modified
2010-06-25 17:40:15 the second argument to --ifconfig must be an IP
address. You are using something (255.255.255.0) that looks more like
a netmask. (silence this warning with --ifconfig-nowarn)
2010-06-25 17:40:15 TUN/TAP device /dev/tun0 opened
2010-06-25 17:40:15
2010-06-25 17:40:15 /sbin/ifconfig tun0 delete
2010-06-25 17:40:15 NOTE: Tried to delete pre-existing tun/tap
instance -- No Problem if failure
2010-06-25 17:40:15 /sbin/ifconfig tun0 192.168.0.202 255.255.255.0
mtu 1500 netmask 255.255.255.255 up
2010-06-25 17:40:15 /Applications/Tunnelblick.app/Contents/Resources/
client.up.tunnelblick.sh -m -w -d tun0 1500 1542 192.168.0.202
255.255.255.0 init
2010-06-25 17:40:15 Initialization Sequence Completed
2010-06-25 17:40:15 84.253.xx.xx


interface after connection:

tun0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.0.202 --> 255.255.255.0 netmask 0xffffffff
open (pid 704)




successfully connected Client:


Thu 01/01/70 01:00 AM: SUCCESS: pid=97905
Thu 01/01/70 01:00 AM: SUCCESS: real-time state notification set to ON
Thu 01/01/70 01:00 AM: SUCCESS: real-time log notification set to ON
Sat 06/26/10 11:01 AM: OpenVPN 2.1_rc15 i386-apple-darwin9.5.0 [SSL]
[LZO2] built on Nov 19 2008
Sat 06/26/10 11:01 AM: MANAGEMENT: TCP Socket listening on
127.0.0.1:1337
Sat 06/26/10 11:01 AM: waiting...
Sat 06/26/10 11:01 AM: MANAGEMENT: Client connected from
127.0.0.1:1337
Thu 01/01/70 01:00 AM: END
Thu 01/01/70 01:00 AM: SUCCESS: hold release succeeded
Sat 06/26/10 11:01 AM: NOTE: the current --script-security setting may
allow this configuration to call user-defined scripts
Thu 01/01/70 01:00 AM: but not yet verified
Sat 06/26/10 11:01 AM: WARNING: this configuration may cache passwords
in memory -- use the auth-nocache option to prevent this
Sat 06/26/10 11:01 AM: WARNING: file 'username.key' is group or others
accessible
Sat 06/26/10 11:01 AM: LZO compression initialized
Sat 06/26/10 11:01 AM: Control Channel MTU parms [ L:1574 D:138 EF:38
EB:0 ET:0 EL:0 ]
Sat 06/26/10 11:01 AM: Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:
135 ET:32 EL:0 AF:3/1 ]
Sat 06/26/10 11:01 AM: Local Options hash (VER=V4): 'd79ca330'
Sat 06/26/10 11:01 AM: Expected Remote Options hash (VER=V4):
'f7df56b8'
Sat 06/26/10 11:01 AM: Socket Buffers: R=[42080->65536] S=[9216-
>65536]
Sat 06/26/10 11:01 AM: UDPv4 link local: [undef]
Sat 06/26/10 11:01 AM: UDPv4 link remote: 84.253.xx.xx:1194
Sat 06/26/10 11:01 AM:
Sat 06/26/10 11:01 AM:
Sat 06/26/10 11:01 AM: sid=44473136 3130bb74
Sat 06/26/10 11:01 AM: Data Channel Encrypt: Cipher 'BF-CBC'
initialized with 128 bit key
Sat 06/26/10 11:01 AM: Data Channel Encrypt: Using 160 bit message
hash 'SHA1' for HMAC authentication
Sat 06/26/10 11:01 AM: Data Channel Decrypt: Cipher 'BF-CBC'
initialized with 128 bit key
Sat 06/26/10 11:01 AM: Data Channel Decrypt: Using 160 bit message
hash 'SHA1' for HMAC authentication
Sat 06/26/10 11:01 AM: 1024 bit RSA
Sat 06/26/10 11:01 AM: [server] Peer Connection Initiated with
84.253.xx.xx:1194
Sat 06/26/10 11:01 AM:
Sat 06/26/10 11:01 AM: SENT CONTROL [server]:
'PUSH_REQUEST' (status=1)
Sat 06/26/10 11:01 AM: ifconfig 192.168.0.201 255.255.255.0'
Sat 06/26/10 11:01 AM: OPTIONS IMPORT: timers and/or timeouts modified
Sat 06/26/10 11:01 AM: OPTIONS IMPORT: --ifconfig/up options modified
Sat 06/26/10 11:01 AM: OPTIONS IMPORT: route-related options modified
Sat 06/26/10 11:01 AM: TUN/TAP device /dev/tap0 opened
Sat 06/26/10 11:01 AM:
Sat 06/26/10 11:01 AM: /sbin/ifconfig tap0 delete
Sat 06/26/10 11:01 AM: NOTE: Tried to delete pre-existing tun/tap
instance -- No Problem if failure
Sat 06/26/10 11:01 AM: /sbin/ifconfig tap0 192.168.0.201 netmask
255.255.255.0 mtu 1500 up
Sat 06/26/10 11:01 AM: Initialization Sequence Completed
Sat 06/26/10 11:01 AM: 84.253.xx.xx





Server config:

#################################################
# Sample OpenVPN 2.0 config file for #
# multi-client server. #
# #
# This file is for the server side #
# of a many-clients <-> one-server #
# OpenVPN configuration. #
# #
# OpenVPN also supports #
# single-machine <-> single-machine #
# configurations (See the Examples page #
# on the web site for more info). #
# #
# This config should work on Windows #
# or Linux/BSD systems. Remember on #
# Windows to quote pathnames and use #
# double backslashes, e.g.: #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
# #
# Comments are preceded with '#' or ';' #
#################################################

# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one. You will need to
# open up this port on your firewall.
port 1194

# TCP or UDP server?
;proto tcp
proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
dev tap0
;dev tun0

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one. On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key). Each client
# and the server must have their own cert and
# key file. The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys. Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert server.crt
key server.key # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys.
dh dh1024.pem

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
;server 10.8.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file. If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface. Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0. Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients. Leave this line commented
# out unless you are ethernet bridging.
server-bridge 192.168.0.10 255.255.255.0 192.168.0.200 192.168.0.220

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses. You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# Push routes to the client to allow it
# to reach other private subnets behind
# the server. Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
# openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
;tls-auth ta.key 0 # This file is secret

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC # Blowfish (default)
;cipher AES-128-CBC # AES
;cipher DES-EDE3-CBC # Triple-DES

# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100

# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
;user nobody
;group nogroup

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it. Use one
# or the other (but not both).
log openvpn.log












client config:

##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however each client should have #
# its own cert and key files. #
# #
# On Windows, you might want to rename this #
# file so it has a .ovpn extension #
##############################################

# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client

# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
dev tap
;dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one. On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap

# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
;proto tcp
proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
;remote my-server-2 1194
remote 84.253.xx.xx 1194

# Choose a random host from the remote
# list for load-balancing. Otherwise
# try hosts in the order specified.
;remote-random

# Keep trying indefinitely to resolve the
# host name of the OpenVPN server. Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite

# Most clients don't need to bind to
# a specific local port number.
nobind

# Downgrade privileges after initialization (non-Windows only)
;user nobody
;group nogroup

# Try to preserve some state across restarts.
persist-key
persist-tun

# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here. See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]

# Wireless networks often produce a lot
# of duplicate packets. Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings

# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
ca ca.crt
cert username.crt
key username.key

# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server". This is an
# important precaution to protect against
# a potential attack discussed here:
# http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server". The build-key-server
# script in the easy-rsa folder will do this.
ns-cert-type server

# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x

# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo

# Set log file verbosity.
verb 3

# Silence repeating messages
;mute 20

[jkbull...gmail.com]

Hmmm. It looks like OpenVPN falls back to using TUN when it sees what
it is interpreting as an error in the IPCONFIG.

Is the iMac client using Tunnelblick? If so, can you post the full
log?

"Set nameserver" is checked for the failed connection (which runs a
script), but no script is being run for the successful connection.
Have you tried it with "Set nameserver" unchecked?

[Ender Informatics]

Many thanks for your reply

I agree to the fall back to tun. I got the same error on systems I
accidentially set the interface to tun.

I will retry with set nameserver unchecked.

iMac uses Tunnelblick as well.
Here the full log:

[Jonathan K. Bullard]

Sorry, I hadn't realized that you already had posted a "success log", which must have come from an iMac.

I noticed that it is using an earlier version of OpenVPN, 2.1_rc15, which means it is also using an earlier version of Tunnelblick. I think it is using Tunnelblick 3.0b10, which (if I remember correctly) uses that version of OpenVPN.

So I suggest that try Tunnelblick 3.0b10 on the MacBook Pro. It is available at http://code.google.com/p/tunnelblick/wiki/DownloadsEntry. If it works, go ahead and use that.

If you're willing to try to help find the cause of the problem, which I would appreciate, try later and later 3.0bxx versions until it fails, and let me know which one fails. Maybe I can figure out something from that.

--
You received this message because you are subscribed to the Google Groups "tunnelblick-discuss" group.
To post to this group, send email to tunnelbli...@googlegroups.com.
To unsubscribe from this group, send email to tunnelblick-dis...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tunnelblick-discuss?hl=en.

[Josef Ender]

Many thanks for your support and sorry for my late response.

Our client is on vacation so it will take some time until I can try again.

I will follow your advice and try the new beta.

Many thanks again! I really appreciate your support.

Josef Ender

--
Josef Ender, ender informatics gmbh
http://www.ender-informatics.ch

> 127.0.0.1:1337 <http://127.0.0.1:1337>

> Sat 06/26/10 11:01 AM: waiting...
> Sat 06/26/10 11:01 AM: MANAGEMENT: Client connected from

> 127.0.0.1:1337 <http://127.0.0.1:1337>

> On Jun 29, 5:52 am, "jkbull...gmail.com <http://gmail.com>"

> <jkbull...@gmail.com <mailto:jkbull...@gmail.com>> wrote:
> > Hmmm. It looks like OpenVPN falls back to using TUN when it sees what
> > it is interpreting as an error in the IPCONFIG.
> >
> > Is the iMac client using Tunnelblick? If so, can you post the full
> > log?
> >
> > "Set nameserver" is checked for the failed connection (which runs a
> > script), but no script is being run for the successful connection.
> > Have you tried it with "Set nameserver" unchecked?
>
> --
> You received this message because you are subscribed to the Google
> Groups "tunnelblick-discuss" group.
> To post to this group, send email to
> tunnelbli...@googlegroups.com

> <mailto:tunnelbli...@googlegroups.com>.

> To unsubscribe from this group, send email to
> tunnelblick-dis...@googlegroups.com

> <mailto:tunnelblick-discuss%2Bunsu...@googlegroups.com>.