connected to server but not to internet

95 views

Skip to first unread message

haris...@gmail.com

unread,

Mar 28, 2016, 10:59:09 AM3/28/16

to tunnelblick-discuss

I'm trying to connect to the VPN using ethernet bridging but am not able to do so. From the logs I've determined that I am able to establish a connection to the server and get an IP address. However, the internet connection doesn't work and I can't access sites using either their website address or IP address. I've followed the instructions on 'Read Before You Post' and the 'Connects Ok, but...' pages to no avail. I've pasted the Tunnelblick diagnostic info below, as well as my server.conf file. The client.conf file is included below too.

Does anyone have any idea why I'm not able to connect?

SERVER.CONF:

dh /tmp/openvpn/dh.pem

ca /tmp/openvpn/ca.crt

cert /tmp/openvpn/cert.pem

key /tmp/openvpn/key.pem

keepalive 10 120

verb 3

mute 3

syslog

writepid /var/run/openvpnd.pid

management 127.0.0.1 14

management-log-cache 100

topology subnet

script-security 2

port 1194

proto tcp-server

cipher bf-cbc

auth sha1

client-config-dir /tmp/openvpn/ccd

comp-lzo yes

tls-server

ifconfig-pool-persist /tmp/openvpn/ip-pool 86400

push "redirect-gateway def1"

tcp-nodelay

tun-mtu 1500

mtu-disc yes

server-bridge 192.168.102.1 255.255.255.0 192.168.102.201 192.168.102.220

dev tap2

persist-key

persist-tun

status openvpn-status.log

DIAGNOSTIC LOG:

*Tunnelblick: OS X 10.10.5; Tunnelblick 3.6.0a (build 4543.4546); prior version 3.5.8 (build 4270.4530); Admin user

Configuration hardrain_client_config

"Sanitized" condensed configuration file for /Users/XXXXXXX/Library/Application Support/Tunnelblick/Configurations/hardrain_client_config.tblk:

client

dev tap2

proto tcp

remote XX.XXX.XX.XXX 1194

resolv-retry infinite

nobind

persist-key

persist-tun

ca ca.crt

cert hardrain_client.crt

key hardrain_client.key

comp-lzo yes

verb 3

================================================================================

Non-Apple kexts that are loaded:

Index Refs Address Size Wired Name (Version) <Linked Against>

143 3 0xffffff7f82bad000 0x60000 0x60000 org.virtualbox.kext.VBoxDrv (5.0.10) <7 5 4 3 1>

144 0 0xffffff7f82c0d000 0x8000 0x8000 org.virtualbox.kext.VBoxUSB (5.0.10) <143 95 39 7 5 4 3 1>

145 0 0xffffff7f82c15000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (5.0.10) <143 7 5 4 3 1>

146 0 0xffffff7f82c1a000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (5.0.10) <143 5 4 1>

================================================================================

There are no unusual files in hardrain_client_config.tblk

================================================================================

Configuration preferences:

useDNS = 1

-routeAllTrafficThroughVpn = 0

-keychainHasPrivateKey = 1

-openvpnVersion =

-keepConnected = 0

-lastConnectionSucceeded = 1

-tunnelDownSoundName = None

================================================================================

Wildcard preferences:

================================================================================

Program preferences:

launchAtNextLogin = 1

notOKToCheckThatIPAddressDidNotChangeAfterConnection = 0

askedUserIfOKToCheckThatIPAddressDidNotChangeAfterConnection = 1

tunnelblickVersionHistory = (

"3.6.0a (build 4543.4546)",

"3.5.8 (build 4270.4530)"

)

lastLaunchTime = 480868462.366635

showConnectedDurations = 1

connectionWindowDisplayCriteria = showWhenConnecting

maxLogDisplaySize = 102400

lastConnectedDisplayName = hardrain_client_config

keyboardShortcutIndex = 1

updateCheckAutomatically = 0

updateSendProfileInfo = 1

NSWindow Frame SettingsSheetWindow = 1358 664 829 524 0 0 2560 1417

NSWindow Frame ConnectingWindow = 1085 923 389 187 0 0 2560 1417

detailsWindowFrameVersion = 4543.4546

detailsWindowFrame = {{1361, 255}, {920, 467}}

detailsWindowLeftFrame = {{0, 0}, {165, 350}}

detailsWindowViewIndex = 2

detailsWindowConfigurationsTabIdentifier = settings

leftNavSelectedDisplayName = hardrain_client_config

AdvancedWindowTabIdentifier = connectingAndDisconnecting

haveDealtWithSparkle1dot5b6 = 1

haveDealtWithOldTunTapPreferences = 1

haveDealtWithOldLoginItem = 1

SUEnableAutomaticChecks = 0

SUFeedURL = https://www.tunnelblick.net/appcast-s.rss

SUScheduledCheckInterval = 86400

SUSendProfileInfo = 1

SULastCheckTime = 2016-03-11 19:53:13 +0000

SUHasLaunchedBefore = 1

WebKitDefaultFontSize = 16

WebKitStandardFont = Times

================================================================================

Tunnelblick Log:

2016-03-28 10:34:28 *Tunnelblick: OS X 10.10.5; Tunnelblick 3.6.0a (build 4543.4546); prior version 3.5.8 (build 4270.4530)

2016-03-28 10:34:29 *Tunnelblick: Attempting connection with hardrain_client_config using shadow copy; Set nameserver = 1; monitoring connection

2016-03-28 10:34:29 *Tunnelblick: openvpnstart start hardrain_client_config.tblk 1337 1 0 1 0 1065330 -ptADGNWradsgnw 2.3.10

2016-03-28 10:34:29 *Tunnelblick: openvpnstart log:

Loading tap-signed.kext

OpenVPN started successfully. Command used to start OpenVPN (one argument per displayed line):

/Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.3.10/openvpn

--daemon

--log

/Library/Application Support/Tunnelblick/Logs/-SUsers-xxxxxxxxx-SLibrary-SApplication Support-STunnelblick-SConfigurations-Shardrain_client_config.tblk-SContents-SResources-Sconfig.ovpn.1_0_1_0_1065330.1337.openvpn.log

--cd

/Library/Application Support/Tunnelblick/Users/xxxxxxxx/hardrain_client_config.tblk/Contents/Resources

--verb

--config

/Library/Application Support/Tunnelblick/Users/xxxxxxxxx/hardrain_client_config.tblk/Contents/Resources/config.ovpn

--cd

/Library/Application Support/Tunnelblick/Users/xxxxxxxx/hardrain_client_config.tblk/Contents/Resources

--management

127.0.0.1

1337

--management-query-passwords

--management-hold

--script-security

--up

/Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -9 -a -d -f -m -w -ptADGNWradsgnw

--down

/Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -9 -a -d -f -m -w -ptADGNWradsgnw

--route-pre-down

/Applications/Tunnelblick.app/Contents/Resources/client.route-pre-down.tunnelblick.sh -9 -a -d -f -m -w -ptADGNWradsgnw

2016-03-28 10:34:29 *Tunnelblick: Established communication with OpenVPN

2016-03-28 10:34:29 *Tunnelblick: Obtained VPN passphrase from the Keychain

2016-03-28 10:34:29 OpenVPN 2.3.10 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [PKCS11] [MH] [IPv6] built on Mar 19 2016

2016-03-28 10:34:29 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.09

2016-03-28 10:34:29 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:1337

2016-03-28 10:34:29 Need hold release from management interface, waiting...

2016-03-28 10:34:29 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:1337

2016-03-28 10:34:29 MANAGEMENT: CMD 'pid'

2016-03-28 10:34:29 MANAGEMENT: CMD 'state on'

2016-03-28 10:34:29 MANAGEMENT: CMD 'state'

2016-03-28 10:34:29 MANAGEMENT: CMD 'bytecount 1'

2016-03-28 10:34:29 MANAGEMENT: CMD 'hold release'

2016-03-28 10:34:29 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.

2016-03-28 10:34:29 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2016-03-28 10:34:29 MANAGEMENT: CMD 'password [...]'

2016-03-28 10:34:29 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

2016-03-28 10:34:29 Socket Buffers: R=[131072->131072] S=[131072->131072]

2016-03-28 10:34:29 Attempting to establish TCP connection with [AF_INET]xx.xxx.xx.xxx:1194 [nonblock]

2016-03-28 10:34:29 MANAGEMENT: >STATE:1459175669,TCP_CONNECT,,,

2016-03-28 10:34:29 *Tunnelblick: openvpnstart starting OpenVPN

2016-03-28 10:34:31 TCP connection established with [AF_INET]xx.xxx.xx.xxx:1194

2016-03-28 10:34:31 TCPv4_CLIENT link local: [undef]

2016-03-28 10:34:31 TCPv4_CLIENT link remote: [AF_INET]xx.xxx.xx.xxx:1194

2016-03-28 10:34:31 MANAGEMENT: >STATE:1459175671,WAIT,,,

2016-03-28 10:34:31 MANAGEMENT: >STATE:1459175671,AUTH,,,

2016-03-28 10:34:31 TLS: Initial packet from [AF_INET]xx.xxx.xx.xxx:1194, sid=78df554f 87a10261

2016-03-28 10:34:32 VERIFY OK: depth=1, CN=hardrain

2016-03-28 10:34:32 VERIFY OK: depth=0, CN=hardrain

2016-03-28 10:34:32 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key

2016-03-28 10:34:32 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

2016-03-28 10:34:32 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key

2016-03-28 10:34:32 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

2016-03-28 10:34:32 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA

2016-03-28 10:34:32 [hardrain] Peer Connection Initiated with [AF_INET]xx.xxx.xx.xxx:1194

2016-03-28 10:34:33 MANAGEMENT: >STATE:1459175673,GET_CONFIG,,,

2016-03-28 10:34:34 SENT CONTROL [hardrain]: 'PUSH_REQUEST' (status=1)

2016-03-28 10:34:34 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,route-gateway 192.168.102.1,ping 10,ping-restart 120,socket-flags TCP_NODELAY,ifconfig 192.168.102.201 255.255.255.0'

2016-03-28 10:34:34 OPTIONS IMPORT: timers and/or timeouts modified

2016-03-28 10:34:34 OPTIONS IMPORT: --socket-flags option modified

2016-03-28 10:34:34 OPTIONS IMPORT: --ifconfig/up options modified

2016-03-28 10:34:34 OPTIONS IMPORT: route options modified

2016-03-28 10:34:34 OPTIONS IMPORT: route-related options modified

2016-03-28 10:34:34 TUN/TAP device /dev/tap2 opened

2016-03-28 10:34:34 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0

2016-03-28 10:34:34 MANAGEMENT: >STATE:1459175674,ASSIGN_IP,,192.168.102.201,

2016-03-28 10:34:34 /sbin/ifconfig tap2 delete

ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address

2016-03-28 10:34:34 NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure

2016-03-28 10:34:34 /sbin/ifconfig tap2 192.168.102.201 netmask 255.255.255.0 mtu 1500 up

2016-03-28 10:34:34 /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -9 -a -d -f -m -w -ptADGNWradsgnw tap2 1500 1576 192.168.102.201 255.255.255.0 init

**********************************************

Start of output from client.up.tunnelblick.sh

NOTE: No network configuration changes need to be made.

WARNING: Will NOT monitor for other network configuration changes.

DNS servers '75.75.75.75 75.75.76.76' will be used for DNS queries when the VPN is active

NOTE: The DNS servers do not include any free public DNS servers known to Tunnelblick. This may cause DNS queries to fail or be intercepted or falsified even if they are directed through the VPN. Specify only known public DNS servers or DNS servers located on the VPN network to avoid such problems.

Flushed the DNS cache via dscacheutil

/usr/sbin/discoveryutil not present. Not flushing the DNS cache via discoveryutil

Notified mDNSResponder that the DNS cache was flushed

End of output from client.up.tunnelblick.sh

**********************************************

2016-03-28 10:34:37 *Tunnelblick: No 'connected.sh' script to execute

2016-03-28 10:34:37 /sbin/route add -net xx.xxx.xx.xxx 10.224.0.1 255.255.255.255

add net xx.xxx.xx.xxx: gateway 10.224.0.1

2016-03-28 10:34:37 /sbin/route add -net 0.0.0.0 192.168.102.1 128.0.0.0

add net 0.0.0.0: gateway 192.168.102.1

2016-03-28 10:34:37 /sbin/route add -net 128.0.0.0 192.168.102.1 128.0.0.0

add net 128.0.0.0: gateway 192.168.102.1

2016-03-28 10:34:37 Initialization Sequence Completed

2016-03-28 10:34:37 MANAGEMENT: >STATE:1459175677,CONNECTED,SUCCESS,192.168.102.201,xx.xxx.xx.xxx

2016-03-28 10:35:17 *Tunnelblick: After 30.0 seconds, gave up trying to fetch IP address information using the ipInfo host's name after connecting.

2016-03-28 10:36:53 *Tunnelblick: After 30.0 seconds, gave up trying to fetch IP address information using the ipInfo host's IP address after connecting.

2016-03-28 10:37:04 *Tunnelblick: Disconnecting; VPN Details… window disconnect button pressed

2016-03-28 10:37:05 *Tunnelblick: No 'pre-disconnect.sh' script to execute

2016-03-28 10:37:05 *Tunnelblick: Disconnecting using 'kill'

2016-03-28 10:37:05 event_wait : Interrupted system call (code=4)

2016-03-28 10:37:05 /Applications/Tunnelblick.app/Contents/Resources/client.route-pre-down.tunnelblick.sh -9 -a -d -f -m -w -ptADGNWradsgnw tap2 1500 1576 192.168.102.201 255.255.255.0 init

**********************************************

Start of output from client.route-pre-down.tunnelblick.sh

WARNING: No saved Tunnelblick DNS configuration found; not doing anything.

End of output from client.route-pre-down.tunnelblick.sh

**********************************************

2016-03-28 10:37:06 /sbin/route delete -net xx.xxx.xx.xxx 10.224.0.1 255.255.255.255

delete net xx.xxx.xx.xxx: gateway 10.224.0.1

2016-03-28 10:37:06 /sbin/route delete -net 0.0.0.0 192.168.102.1 128.0.0.0

delete net 0.0.0.0: gateway 192.168.102.1

2016-03-28 10:37:06 /sbin/route delete -net 128.0.0.0 192.168.102.1 128.0.0.0

delete net 128.0.0.0: gateway 192.168.102.1

2016-03-28 10:37:06 Closing TUN/TAP interface

2016-03-28 10:37:06 /Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -9 -a -d -f -m -w -ptADGNWradsgnw tap2 1500 1576 192.168.102.201 255.255.255.0 init

**********************************************

Start of output from client.down.tunnelblick.sh

WARNING: Not restoring DNS settings because no saved Tunnelblick DNS information was found.

Flushed the DNS cache via dscacheutil

/usr/sbin/discoveryutil not present. Not flushing the DNS cache via discoveryutil

Notified mDNSResponder that the DNS cache was flushed

End of output from client.down.tunnelblick.sh

**********************************************

2016-03-28 10:37:07 SIGTERM[hard,] received, process exiting

2016-03-28 10:37:07 MANAGEMENT: >STATE:1459175827,EXITING,SIGTERM,,

2016-03-28 10:37:07 *Tunnelblick: No 'post-disconnect.sh' script to execute

2016-03-28 10:37:07 *Tunnelblick: Expected disconnection occurred.

================================================================================

"Sanitized" full configuration file

##############################################

# 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 tap2

;dev tun2

# Windows needs the TAP-Windows 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 xx.xxx.xx.xxx TCP-1194

remote xx.xxx.xx.xxx 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 nobody

# 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.

# THE FOLLOWING _client.* FILES HAVE TO BE MODIFIED

# FOR THE EACH CLIENT

ca ca.crt

cert hardrain_client.crt

key hardrain_client.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 yes

# Set log file verbosity.

verb 3

# Silence repeating messages

;mute 20

================================================================================

ifconfig output:

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384

options=3<RXCSUM,TXCSUM>

inet6 ::1 prefixlen 128

inet 127.0.0.1 netmask 0xff000000

inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1

nd6 options=1<PERFORMNUD>

gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280

stf0: flags=0<> mtu 1280

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

ether 60:c5:47:0d:23:0e

inet6 fe80::62c5:47ff:fe0d:230e%en0 prefixlen 64 scopeid 0x4

inet 10.232.35.143 netmask 0xffe00000 broadcast 10.255.255.255

nd6 options=1<PERFORMNUD>

media: autoselect

status: active

en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

options=60<TSO4,TSO6>

ether 32:00:18:f3:e4:e0

media: autoselect <full-duplex>

status: inactive

p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304

ether 02:c5:47:0d:23:0e

media: autoselect

status: inactive

awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1452

ether e2:8f:3f:a7:ef:17

inet6 fe80::e08f:3fff:fea7:ef17%awdl0 prefixlen 64 scopeid 0x9

nd6 options=1<PERFORMNUD>

media: autoselect

status: active

bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=63<RXCSUM,TXCSUM,TSO4,TSO6>

ether 62:c5:47:d0:3c:00

Configuration:

id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0

maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200

root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0

ipfilter disabled flags 0x2

member: en1 flags=3<LEARNING,DISCOVER>

ifmaxaddr 0 port 7 priority 0 path cost 0

nd6 options=1<PERFORMNUD>

media: <unknown type>

status: inactive

utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500

inet6 fe80::2cda:3ae6:632c:8957%utun0 prefixlen 64 scopeid 0xb

nd6 options=1<PERFORMNUD>

utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500

inet6 fe80::1667:6da0:dc4d:8a98%utun1 prefixlen 64 scopeid 0xc

nd6 options=1<PERFORMNUD>

utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500

inet6 fe80::6555:4630:e049:ea76%utun2 prefixlen 64 scopeid 0xd

nd6 options=1<PERFORMNUD>

fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078

lladdr 00:0a:27:02:00:50:8a:c0

nd6 options=1<PERFORMNUD>

media: autoselect <full-duplex>

status: inactive

en3: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>

ether 10:dd:b1:98:b0:53

nd6 options=1<PERFORMNUD>

media: autoselect (none)

status: inactive

================================================================================

Console Log:

2016-03-28 09:58:51 Tunnelblick[23320] tcp_connection_destination_prepare_complete 34 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:58:52 Tunnelblick[23320] tcp_connection_destination_prepare_complete 35 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:58:53 Tunnelblick[23320] tcp_connection_destination_prepare_complete 36 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:58:54 Tunnelblick[23320] tcp_connection_destination_prepare_complete 37 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:58:55 Tunnelblick[23320] tcp_connection_destination_prepare_complete 38 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:58:56 Tunnelblick[23320] tcp_connection_destination_prepare_complete 39 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:58:57 Tunnelblick[23320] tcp_connection_destination_prepare_complete 40 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:58:58 Tunnelblick[23320] tcp_connection_destination_prepare_complete 41 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:58:59 Tunnelblick[23320] tcp_connection_destination_prepare_complete 42 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:59:00 Tunnelblick[23320] tcp_connection_destination_prepare_complete 43 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:59:01 Tunnelblick[23320] tcp_connection_destination_prepare_complete 44 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:59:02 Tunnelblick[23320] tcp_connection_destination_prepare_complete 45 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:59:03 Tunnelblick[23320] tcp_connection_destination_prepare_complete 46 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:59:04 Tunnelblick[23320] tcp_connection_destination_prepare_complete 47 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:59:05 Tunnelblick[23320] tcp_connection_destination_prepare_complete 48 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 09:59:06 Tunnelblick[23320] tcp_connection_destination_prepare_complete 49 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:00:22 Tunnelblick[23320] currentIPInfo(Address): IP address info could not be fetched within 94.2 seconds; the error was 'Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080000f4080 {NSUnderlyingError=0x60800025e300 "The request timed out.", NSErrorFailingURLStringKey=http://205.233.73.116/ipinfo, NSErrorFailingURLKey=http://205.233.73.116/ipinfo, _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=60, NSLocalizedDescription=The request timed out.}'; the response was '(null)'

2016-03-28 10:03:02 Tunnelblick[23320] startDisconnectingUserKnows: while already disconnecting 'hardrain_client_config'; OpenVPN state = 'DISCONNECTING'

2016-03-28 10:06:20 Tunnelblick[23320] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-hardrain_client_config' account = 'privateKey'

2016-03-28 10:07:07 Tunnelblick[23320] currentIPInfo(Name): IP address info could not be fetched within 35.4 seconds; the error was 'Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080000e5880 {NSUnderlyingError=0x60000025bd50 "The request timed out.", NSErrorFailingURLStringKey=https://www.tunnelblick.net/ipinfo, NSErrorFailingURLKey=https://www.tunnelblick.net/ipinfo, NSLocalizedDescription=The request timed out.}'; the response was '(null)'

2016-03-28 10:07:09 Tunnelblick[23320] tcp_connection_destination_prepare_complete 57 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:10 Tunnelblick[23320] tcp_connection_destination_prepare_complete 58 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:11 Tunnelblick[23320] tcp_connection_destination_prepare_complete 59 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:12 Tunnelblick[23320] tcp_connection_destination_prepare_complete 60 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:13 Tunnelblick[23320] tcp_connection_destination_prepare_complete 61 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:14 Tunnelblick[23320] tcp_connection_destination_prepare_complete 62 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:15 Tunnelblick[23320] tcp_connection_destination_prepare_complete 63 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:16 Tunnelblick[23320] tcp_connection_destination_prepare_complete 64 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:17 Tunnelblick[23320] tcp_connection_destination_prepare_complete 65 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:18 Tunnelblick[23320] tcp_connection_destination_prepare_complete 66 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:19 Tunnelblick[23320] tcp_connection_destination_prepare_complete 67 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:20 Tunnelblick[23320] tcp_connection_destination_prepare_complete 68 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:21 Tunnelblick[23320] tcp_connection_destination_prepare_complete 69 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:22 Tunnelblick[23320] tcp_connection_destination_prepare_complete 70 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:23 Tunnelblick[23320] tcp_connection_destination_prepare_complete 71 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:24 Tunnelblick[23320] tcp_connection_destination_prepare_complete 72 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:25 Tunnelblick[23320] tcp_connection_destination_prepare_complete 73 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:26 Tunnelblick[23320] tcp_connection_destination_prepare_complete 74 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:27 Tunnelblick[23320] tcp_connection_destination_prepare_complete 75 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:07:28 Tunnelblick[23320] tcp_connection_destination_prepare_complete 76 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:08:44 Tunnelblick[23320] currentIPInfo(Address): IP address info could not be fetched within 97.2 seconds; the error was 'Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000000f3780 {NSUnderlyingError=0x60800044e160 "The request timed out.", NSErrorFailingURLStringKey=http://205.233.73.116/ipinfo, NSErrorFailingURLKey=http://205.233.73.116/ipinfo, _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=60, NSLocalizedDescription=The request timed out.}'; the response was '(null)'

2016-03-28 10:08:59 Tunnelblick[23320] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-hardrain_client_config' account = 'privateKey'

2016-03-28 10:09:13 Tunnelblick[23320] tcp_connection_destination_prepare_complete 80 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:15 Tunnelblick[23320] tcp_connection_destination_prepare_complete 81 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:16 Tunnelblick[23320] tcp_connection_destination_prepare_complete 82 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:17 Tunnelblick[23320] tcp_connection_destination_prepare_complete 83 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:18 Tunnelblick[23320] tcp_connection_destination_prepare_complete 84 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:19 Tunnelblick[23320] tcp_connection_destination_prepare_complete 85 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:20 Tunnelblick[23320] tcp_connection_destination_prepare_complete 86 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:21 Tunnelblick[23320] tcp_connection_destination_prepare_complete 87 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:22 Tunnelblick[23320] tcp_connection_destination_prepare_complete 88 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:23 Tunnelblick[23320] tcp_connection_destination_prepare_complete 89 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:24 Tunnelblick[23320] tcp_connection_destination_prepare_complete 90 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:25 Tunnelblick[23320] tcp_connection_destination_prepare_complete 91 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:26 Tunnelblick[23320] tcp_connection_destination_prepare_complete 92 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:27 Tunnelblick[23320] tcp_connection_destination_prepare_complete 93 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:28 Tunnelblick[23320] tcp_connection_destination_prepare_complete 94 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:29 Tunnelblick[23320] tcp_connection_destination_prepare_complete 95 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:30 Tunnelblick[23320] tcp_connection_destination_prepare_complete 96 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:09:31 Tunnelblick[23320] tcp_connection_destination_prepare_complete 97 connectx to 205.233.73.116:443@0 failed: No route to host

2016-03-28 10:10:47 Tunnelblick[23320] currentIPInfo(Name): IP address info could not be fetched within 98.8 seconds; the error was 'Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000000faf80 {NSUnderlyingError=0x600000447b00 "The request timed out.", NSErrorFailingURLStringKey=https://www.tunnelblick.net/ipinfo, NSErrorFailingURLKey=https://www.tunnelblick.net/ipinfo, _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=60, NSLocalizedDescription=The request timed out.}'; the response was '(null)'

2016-03-28 10:10:47 Tunnelblick[23320] tcp_connection_destination_prepare_complete 99 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:10:48 Tunnelblick[23320] tcp_connection_destination_prepare_complete 100 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:10:49 Tunnelblick[23320] tcp_connection_destination_prepare_complete 101 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:10:50 Tunnelblick[23320] tcp_connection_destination_prepare_complete 102 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:10:51 Tunnelblick[23320] tcp_connection_destination_prepare_complete 103 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:11:25 Tunnelblick[23320] currentIPInfo(Address): IP address info could not be fetched within 37.4 seconds; the error was 'Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080000ed180 {NSUnderlyingError=0x600000442a30 "The request timed out.", NSErrorFailingURLStringKey=http://205.233.73.116/ipinfo, NSErrorFailingURLKey=http://205.233.73.116/ipinfo, NSLocalizedDescription=The request timed out.}'; the response was '(null)'

2016-03-28 10:11:34 spindump[81780] Saved spin report for Tunnelblick version 3.6.0a (build 4543.4546) (4543.4546) to /Library/Logs/DiagnosticReports/Tunnelblick_2016-03-28-101134_Hurricane.spin

2016-03-28 10:15:48 Tunnelblick[23320] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-hardrain_client_config' account = 'privateKey'

2016-03-28 10:16:56 Tunnelblick[23320] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-hardrain_client_config' account = 'privateKey'

2016-03-28 10:17:41 Tunnelblick[23320] currentIPInfo(Name): IP address info could not be fetched within 35.2 seconds; the error was 'Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080000fbd80 {NSUnderlyingError=0x6000004414a0 "The request timed out.", NSErrorFailingURLStringKey=https://www.tunnelblick.net/ipinfo, NSErrorFailingURLKey=https://www.tunnelblick.net/ipinfo, NSLocalizedDescription=The request timed out.}'; the response was '(null)'

2016-03-28 10:17:46 Tunnelblick[23320] tcp_connection_destination_prepare_complete 113 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:47 Tunnelblick[23320] tcp_connection_destination_prepare_complete 114 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:48 Tunnelblick[23320] tcp_connection_destination_prepare_complete 115 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:49 Tunnelblick[23320] tcp_connection_destination_prepare_complete 116 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:50 Tunnelblick[23320] tcp_connection_destination_prepare_complete 117 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:51 Tunnelblick[23320] tcp_connection_destination_prepare_complete 118 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:52 Tunnelblick[23320] tcp_connection_destination_prepare_complete 119 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:53 Tunnelblick[23320] tcp_connection_destination_prepare_complete 120 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:54 Tunnelblick[23320] tcp_connection_destination_prepare_complete 121 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:55 Tunnelblick[23320] tcp_connection_destination_prepare_complete 122 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:56 Tunnelblick[23320] tcp_connection_destination_prepare_complete 123 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:57 Tunnelblick[23320] tcp_connection_destination_prepare_complete 124 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:58 Tunnelblick[23320] tcp_connection_destination_prepare_complete 125 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:17:59 Tunnelblick[23320] tcp_connection_destination_prepare_complete 126 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:18:00 Tunnelblick[23320] tcp_connection_destination_prepare_complete 127 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:18:01 Tunnelblick[23320] tcp_connection_destination_prepare_complete 128 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:18:02 Tunnelblick[23320] tcp_connection_destination_prepare_complete 129 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:18:03 Tunnelblick[23320] tcp_connection_destination_prepare_complete 130 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:19:20 Tunnelblick[23320] currentIPInfo(Address): IP address info could not be fetched within 98.4 seconds; the error was 'Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000000f3680 {NSUnderlyingError=0x60000045e450 "The request timed out.", NSErrorFailingURLStringKey=http://205.233.73.116/ipinfo, NSErrorFailingURLKey=http://205.233.73.116/ipinfo, _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=60, NSLocalizedDescription=The request timed out.}'; the response was '(null)'

2016-03-28 10:32:11 Tunnelblick[23320] applicationShouldTerminate: termination because of Quit; delayed until 'shutdownTunnelblick' finishes

2016-03-28 10:32:11 Tunnelblick[23320] Finished shutting down Tunnelblick; allowing termination

2016-03-28 10:32:15 Tunnelblick[26189] Tunnelblick: OS X 10.10.5; Tunnelblick 3.6.0a (build 4543.4546)

2016-03-28 10:32:15 Tunnelblick[26189] Warning: preferences contain unknown preference 'NSWindow Frame NSFindPanel'

2016-03-28 10:32:16 Tunnelblick[26189] Set program update feedURL to https://www.tunnelblick.net/appcast-s.rss

2016-03-28 10:33:37 Tunnelblick[26189] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-hardrain_client_config' account = 'privateKey'

2016-03-28 10:34:19 Tunnelblick[26189] applicationShouldTerminate: termination because of Quit; delayed until 'shutdownTunnelblick' finishes

2016-03-28 10:34:19 Tunnelblick[26189] Finished shutting down Tunnelblick; allowing termination

2016-03-28 10:34:21 Tunnelblick[26352] Tunnelblick: OS X 10.10.5; Tunnelblick 3.6.0a (build 4543.4546)

2016-03-28 10:34:21 Tunnelblick[26352] Warning: preferences contain unknown preference 'NSWindow Frame NSFindPanel'

2016-03-28 10:34:22 Tunnelblick[26352] Set program update feedURL to https://www.tunnelblick.net/appcast-s.rss

2016-03-28 10:34:29 Tunnelblick[26352] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-hardrain_client_config' account = 'privateKey'

2016-03-28 10:35:17 Tunnelblick[26352] currentIPInfo(Name): IP address info could not be fetched within 35.1 seconds; the error was 'Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000000f5080 {NSUnderlyingError=0x60000025d0a0 "The request timed out.", NSErrorFailingURLStringKey=https://www.tunnelblick.net/ipinfo, NSErrorFailingURLKey=https://www.tunnelblick.net/ipinfo, NSLocalizedDescription=The request timed out.}'; the response was '(null)'

2016-03-28 10:35:19 Tunnelblick[26352] tcp_connection_destination_prepare_complete 7 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:20 Tunnelblick[26352] tcp_connection_destination_prepare_complete 8 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:21 Tunnelblick[26352] tcp_connection_destination_prepare_complete 9 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:22 Tunnelblick[26352] tcp_connection_destination_prepare_complete 10 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:23 Tunnelblick[26352] tcp_connection_destination_prepare_complete 11 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:24 Tunnelblick[26352] tcp_connection_destination_prepare_complete 12 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:25 Tunnelblick[26352] tcp_connection_destination_prepare_complete 13 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:26 Tunnelblick[26352] tcp_connection_destination_prepare_complete 14 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:27 Tunnelblick[26352] tcp_connection_destination_prepare_complete 15 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:28 Tunnelblick[26352] tcp_connection_destination_prepare_complete 16 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:29 Tunnelblick[26352] tcp_connection_destination_prepare_complete 17 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:30 Tunnelblick[26352] tcp_connection_destination_prepare_complete 18 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:31 Tunnelblick[26352] tcp_connection_destination_prepare_complete 19 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:32 Tunnelblick[26352] tcp_connection_destination_prepare_complete 20 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:33 Tunnelblick[26352] tcp_connection_destination_prepare_complete 21 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:34 Tunnelblick[26352] tcp_connection_destination_prepare_complete 22 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:35 Tunnelblick[26352] tcp_connection_destination_prepare_complete 23 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:36 Tunnelblick[26352] tcp_connection_destination_prepare_complete 24 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:35:37 Tunnelblick[26352] tcp_connection_destination_prepare_complete 25 connectx to 205.233.73.116:80@0 failed: No route to host

2016-03-28 10:36:53 Tunnelblick[26352] currentIPInfo(Address): IP address info could not be fetched within 96.2 seconds; the error was 'Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080000e0100 {NSUnderlyingError=0x60800005b3c0 "The request timed out.", NSErrorFailingURLStringKey=http://205.233.73.116/ipinfo, NSErrorFailingURLKey=http://205.233.73.116/ipinfo, _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=60, NSLocalizedDescription=The request timed out.}'; the response was '(null)'

jkbull...gmail.com

unread,

Mar 28, 2016, 11:10:04 AM3/28/16

to tunnelblick-discuss, haris...@gmail.com

Bridging is problematic; the OpenVPN folks discourage it.

But without looking into your info in detail, the "dev tap2" line in your configuration file caught my eye.

Try changing it to just "dev tap" and see if that helps.

...

haris...@gmail.com

unread,

Mar 28, 2016, 11:24:26 AM3/28/16

to tunnelblick-discuss, haris...@gmail.com

Ok... I just gave that a shot (switching to just 'dev tap' in client & server) and it's still not working. Anything else I can try?

...

jkbull...gmail.com

unread,

Mar 28, 2016, 11:29:49 AM3/28/16

to tunnelblick-discuss, haris...@gmail.com

It looks like a routing/setup problem, but it could also be a problem on the server. You can try consulting OpenVPN experts:

On Monday, March 28, 2016 at 11:24:26 AM UTC-4, <> wrote:

Ok... I just gave that a shot (switching to just 'dev tap' in client & server) and it's still not working. Anything else I can try?

On Monday, March 28, 2016 at 10:59:09 AM UTC-4, haris...@gmail.com wrote:
I'm trying to connect to the VPN using ethernet bridging but am not able to do so. From the logs I've determined that I am able to establish a connection to the server and get an IP address. However, the internet connection doesn't work and I can't access sites using either their website address or IP address. I've followed the instructions on 'Read Before You Post' and the 'Connects Ok, but...' pages to no avail. I've pasted the Tunnelblick diagnostic info below, as well as my server.conf file. The client.conf file is included below too.

Does anyone have any idea why I'm not able to connect?