IP address not different after connecting

230 views
Skip to first unread message

Tunnelblick Temporary

unread,
Feb 4, 2019, 6:42:20 PM2/4/19
to tunnelblick-discuss
Hi, newbie here. Can anyone help me figure out why my public apparent IP address is not different after connecting? I have "Route all IPv4 through the VPN" and "Disable IPv6" checked, I added the "redirect-gateway def1" to the opvn, and I checked "allowChangesToManuallySetNetworkSettings" because it kept throwing up a warning, but none of those things affected the problem at all. I can access sites fine-- just not anonymously. Here's the log info:



*Tunnelblick: macOS 10.14.2; Tunnelblick 3.7.9beta02 (build 5200); prior version 3.7.8 (build 5180); Admin user
git commit e776ee99c72f123303d71557a8a3d9f1f57a7f95


Configuration [filename redacted]

"Sanitized" condensed configuration file for /Library/Application Support/Tunnelblick/Shared/[filename redacted].tblk:

dev tun
proto tcp
remote us.[vpn provider redacted] 443
cipher AES-256-CBC
auth SHA256
redirect-gateway def1
resolv-retry infinite
nobind
persist-key
persist-tun
client
verb 3
auth-user-pass
verify-x509-name vpn.[vpn provider redacted] name
dhcp-option DNS 8.8.8.8
dhcp-option DNS 8.8.4.4
<ca>
[Security-related line(s) omitted]
</ca>
<cert>
[Security-related line(s) omitted]
</cert>
<key>
[Security-related line(s) omitted]
</key>


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

Non-Apple kexts that are loaded:

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  171    0 0xffffff7f85c25000 0x33000    0x33000    com.cisco.kext.acsock (4.5.0) D5CD13F0-0EAE-3A95-9ECB-970AFAFCB139 <6 5 1>
  172    0 0xffffff7f85c58000 0x88000    0x88000    com.avg.FileShield (4.0.0) 6181B24E-3160-393F-8867-B84395FA5FEF <6 5 1>
  173    0 0xffffff7f85ce0000 0x3000     0x3000     com.avg.PacketForwarder (2.1) 8AACC27B-A814-3BD6-B964-193B1D029AA4 <5 1>

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

Files in [filename redacted].tblk:
      Contents/Resources/config.ovpn

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

Configuration preferences:

autoConnect = 1
-onSystemStart = 0
useDNS = 1
-resetPrimaryInterfaceAfterDisconnect = 0
-resetPrimaryInterfaceAfterUnexpectedDisconnect = 0
-routeAllTrafficThroughVpn = 1
-useRouteUpInsteadOfUp = 1
-keychainHasUsernameAndPassword = 1
-loadTap =
-keepConnected = 1
-loggingLevel = 3
-allowChangesToManuallySetNetworkSettings = 1
-disableNetworkAccessAfterDisconnect = 0
-disableNetworkAccessAfterUnexpectedDisconnect = 0
-lastConnectionSucceeded = 1

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

Wildcard preferences:


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

Program preferences:

placeIconInStandardPositionInStatusBar = 1
launchAtNextLogin = 1
notOKToCheckThatIPAddressDidNotChangeAfterConnection = 0
tunnelblickVersionHistory = (
    "3.7.9beta02 (build 5200)",
    "3.7.8 (build 5180)",
    "3.7.7 (build 5150)",
    "3.7.4b (build 4921)",
    "3.7.4a (build 4920)",
    "3.7.2 (build 4850)",
    "3.7.1b (build 4813)",
    "3.7.1a (build 4812)",
    "3.7.0 (build 4790)"
)
lastLaunchTime = 570997632.1926939
lastLanguageAtLaunchWasRTL = 0
connectionWindowDisplayCriteria = showWhenConnecting
maxLogDisplaySize = 102400
lastConnectedDisplayName = [filename redacted]
keyboardShortcutIndex = 1
namedCredentialsThatAllConfigurationsUse = Common
updateCheckAutomatically = 1
NSWindow Frame ConnectingWindow = 445 462 389 187 0 0 1280 777
NSWindow Frame SUUpdateAlert = 330 308 620 392 0 0 1280 777
detailsWindowFrameVersion = 5200
detailsWindowFrame = {{231, 165}, {920, 468}}
detailsWindowLeftFrame = {{0, 0}, {165, 350}}
detailsWindowViewIndex = 0
detailsWindowConfigurationsTabIdentifier = settings
leftNavSelectedDisplayName = [filename redacted]
AdvancedWindowTabIdentifier = vpnCredentials
haveDealtWithOldTunTapPreferences = 1
haveDealtWithOldLoginItem = 1
haveDealtWithAfterDisconnect = 1
SUEnableAutomaticChecks = 1
SUScheduledCheckInterval = 86400
SUSendProfileInfo = 1
SULastCheckTime = 2019-02-04 18:27:00 +0000
SULastProfileSubmissionDate = 2019-01-30 18:42:31 +0000
SUHasLaunchedBefore = 1
WebKitDefaultFontSize = 16
WebKitStandardFont = Times
askedUserIfOKToCheckThatIPAddressDidNotChangeAfterConnection = 1
haveDealtWithSparkle1dot5b6 = 1
updateSendProfileInfo = 1

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

Tunnelblick Log:

*Tunnelblick: macOS 10.14.2; Tunnelblick 3.7.9beta02 (build 5200); prior version 3.7.8 (build 5180)
2019-02-04 15:29:46 *Tunnelblick: Attempting connection with [filename redacted]; Set nameserver = 769; monitoring connection
2019-02-04 15:29:46 *Tunnelblick: openvpnstart start [filename redacted].tblk 52527 769 0 3 0 1164080 -ptADGNWradsgnw 2.4.6-openssl-1.0.2q
2019-02-04 15:29:46 *Tunnelblick: openvpnstart log:
     OpenVPN started successfully. Command used to start OpenVPN (one argument per displayed line):
    
          /Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.4.6-openssl-1.0.2q/openvpn
          --daemon
          --log /Library/Application Support/Tunnelblick/Logs/-SLibrary-SApplication Support-STunnelblick-SShared-S[vpn provider redacted]--[country name redacted].tblk-SContents-SResources-Sconfig.ovpn.769_0_3_0_1164080.52527.openvpn.log
          --cd /Library/Application Support/Tunnelblick/Shared/[filename redacted].tblk/Contents/Resources
          --setenv IV_GUI_VER "net.tunnelblick.tunnelblick 5200 3.7.9beta02 (build 5200)"
          --verb 3
          --config /Library/Application Support/Tunnelblick/Shared/[filename redacted].tblk/Contents/Resources/config.ovpn
          --setenv TUNNELBLICK_CONFIG_FOLDER /Library/Application Support/Tunnelblick/Shared/[filename redacted].tblk/Contents/Resources
          --verb 3
          --cd /Library/Application Support/Tunnelblick/Shared/[filename redacted].tblk/Contents/Resources
          --management 127.0.0.1 52527 /Library/Application Support/Tunnelblick/cpgnmmopcnhlffmcinnbcjkkkncppicheodiedkb.mip
          --management-query-passwords
          --management-hold
          --redirect-gateway def1
          --script-security 2
          --route-up /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -9 -d -f -m -o -w -ptADGNWradsgnw
          --down /Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -9 -d -f -m -o -w -ptADGNWradsgnw

2019-02-04 15:29:46 *Tunnelblick: openvpnstart starting OpenVPN
2019-02-04 15:29:46 *Tunnelblick: Established communication with OpenVPN
2019-02-04 15:29:46 >INFO:OpenVPN Management Interface Version 1 -- type 'help' for more info
2019-02-04 15:29:46 OpenVPN 2.4.6 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [MH/RECVDA] [AEAD] built on Jan 10 2019
2019-02-04 15:29:46 library versions: OpenSSL 1.0.2q  20 Nov 2018, LZO 2.10
2019-02-04 15:29:46 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:52527
2019-02-04 15:29:46 Need hold release from management interface, waiting...
2019-02-04 15:29:46 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:52527
2019-02-04 15:29:46 MANAGEMENT: CMD 'pid'
2019-02-04 15:29:46 MANAGEMENT: CMD 'auth-retry interact'
2019-02-04 15:29:46 MANAGEMENT: CMD 'state on'
2019-02-04 15:29:46 MANAGEMENT: CMD 'state'
2019-02-04 15:29:46 MANAGEMENT: CMD 'bytecount 1'
2019-02-04 15:29:46 MANAGEMENT: CMD 'hold release'
2019-02-04 15:29:46 *Tunnelblick: Obtained VPN username and password from the Keychain
2019-02-04 15:29:46 MANAGEMENT: CMD 'username "Auth" "[username redacted]"'
2019-02-04 15:29:46 MANAGEMENT: CMD 'password [...]'
2019-02-04 15:29:46 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2019-02-04 15:29:47 MANAGEMENT: >STATE:1549322987,RESOLVE,,,,,,
2019-02-04 15:29:47 TCP/UDP: Preserving recently used remote address: [AF_INET]216.162.42.66:443
2019-02-04 15:29:47 Socket Buffers: R=[131072->131072] S=[131072->131072]
2019-02-04 15:29:47 Attempting to establish TCP connection with [AF_INET]216.162.42.66:443 [nonblock]
2019-02-04 15:29:47 MANAGEMENT: >STATE:1549322987,TCP_CONNECT,,,,,,
2019-02-04 15:29:48 TCP connection established with [AF_INET]216.162.42.66:443
2019-02-04 15:29:48 TCP_CLIENT link local: (not bound)
2019-02-04 15:29:48 TCP_CLIENT link remote: [AF_INET]216.162.42.66:443
2019-02-04 15:29:48 MANAGEMENT: >STATE:1549322988,WAIT,,,,,,
2019-02-04 15:29:48 MANAGEMENT: >STATE:1549322988,AUTH,,,,,,
2019-02-04 15:29:48 TLS: Initial packet from [AF_INET]216.162.42.66:443, sid=b07b76ed 2fa04911
2019-02-04 15:29:48 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2019-02-04 15:29:48 VERIFY X509NAME OK: CN=vpn.[vpn provider redacted]
2019-02-04 15:29:48 VERIFY OK: depth=0, CN=vpn.[vpn provider redacted]
2019-02-04 15:29:48 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
2019-02-04 15:29:48 [vpn.[vpn provider redacted]] Peer Connection Initiated with [AF_INET]216.162.42.66:443
2019-02-04 15:29:49 MANAGEMENT: >STATE:1549322989,GET_CONFIG,,,,,,
2019-02-04 15:29:49 SENT CONTROL [vpn.[vpn provider redacted]]: 'PUSH_REQUEST' (status=1)
2019-02-04 15:29:53 PUSH: Received control message: 'PUSH_REPLY,ping 3,ping-restart 10,topology subnet,ifconfig 10.11.42.129 255.240.0.0,dhcp-option DNS 109.236.87.2,dhcp-option DNS 144.217.75.55,route-gateway 10.0.0.1,redirect-gateway def1'
2019-02-04 15:29:53 OPTIONS IMPORT: timers and/or timeouts modified
2019-02-04 15:29:53 OPTIONS IMPORT: --ifconfig/up options modified
2019-02-04 15:29:53 OPTIONS IMPORT: route options modified
2019-02-04 15:29:53 OPTIONS IMPORT: route-related options modified
2019-02-04 15:29:53 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2019-02-04 15:29:53 Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
2019-02-04 15:29:53 Outgoing Data Channel: Using 256 bit message hash 'SHA256' for HMAC authentication
2019-02-04 15:29:53 Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
2019-02-04 15:29:53 Incoming Data Channel: Using 256 bit message hash 'SHA256' for HMAC authentication
2019-02-04 15:29:53 Opening utun (connect(AF_SYS_CONTROL)): Resource busy (errno=16)
2019-02-04 15:29:53 Opening utun (connect(AF_SYS_CONTROL)): Resource busy (errno=16)
2019-02-04 15:29:53 Opened utun device utun2
2019-02-04 15:29:53 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
2019-02-04 15:29:53 MANAGEMENT: >STATE:1549322993,ASSIGN_IP,,10.11.42.129,,,,
2019-02-04 15:29:53 /sbin/ifconfig utun2 delete
                                        ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address
2019-02-04 15:29:53 NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
2019-02-04 15:29:53 /sbin/ifconfig utun2 10.11.42.129 10.11.42.129 netmask 255.240.0.0 mtu 1500 up
2019-02-04 15:29:53 /sbin/route add -net 10.0.0.0 10.11.42.129 255.240.0.0
                                        add net 10.0.0.0: gateway 10.11.42.129
2019-02-04 15:29:53 /sbin/route add -net 216.162.42.66 10.0.0.1 255.255.255.255
                                        add net 216.162.42.66: gateway 10.0.0.1
2019-02-04 15:29:53 /sbin/route add -net 0.0.0.0 10.0.0.1 128.0.0.0
                                        add net 0.0.0.0: gateway 10.0.0.1
2019-02-04 15:29:53 /sbin/route add -net 128.0.0.0 10.0.0.1 128.0.0.0
                                        add net 128.0.0.0: gateway 10.0.0.1
                                        **********************************************
                                        Start of output from client.up.tunnelblick.sh
                                        Retrieved from OpenVPN: name server(s) [ 8.8.8.8 8.8.4.4 109.236.87.2 144.217.75.55 ], search domain(s) [  ] and SMB server(s) [  ] and using default domain name [ openvpn ]
                                        Will allow changes to manually-set DomainName 'openvpn'
                                        Will allow changes to manually-set ServerAddresses '8.8.8.8 8.8.4.4 109.236.87.2 144.217.75.55'
                                        Setting search domains to 'openvpn' because the search domains were not set manually (or are allowed to be changed) and 'Prepend domain name to search domains' was not selected
                                        Saved the DNS and SMB configurations so they can be restored
                                        Did not change DNS ServerAddresses setting of '8.8.8.8 8.8.4.4 109.236.87.2 144.217.75.55'
                                        Did not change DNS SearchDomains setting of 'openvpn'
                                        Did not change DNS DomainName setting of 'openvpn'
                                        Did not change SMB NetBIOSName setting of ''
                                        Did not change SMB Workgroup setting of ''
                                        Did not change SMB WINSAddresses setting of ''
                                        DNS servers '8.8.8.8 8.8.4.4 109.236.87.2 144.217.75.55' will be used for DNS queries when the VPN is active
                                        NOTE: The DNS servers include one or more free public DNS servers known to Tunnelblick and one or more DNS servers not known to Tunnelblick. If used, the DNS servers not known to Tunnelblick 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
                                        Not notifying mDNSResponderHelper that the DNS cache was flushed because it is not running
                                        Setting up to monitor system configuration with process-network-changes
                                        End of output from client.up.tunnelblick.sh
                                        **********************************************
2019-02-04 15:29:56 Initialization Sequence Completed
2019-02-04 15:29:56 MANAGEMENT: >STATE:1549322996,CONNECTED,SUCCESS,10.11.42.129,216.162.42.66,443,10.0.0.4,63415
2019-02-04 15:29:57 *Tunnelblick: No 'connected.sh' script to execute
2019-02-04 15:29:58 *Tunnelblick process-network-changes: A system configuration change was ignored
2019-02-04 15:30:02 *Tunnelblick: This computer's apparent public IP address ([IP redacted]) was unchanged after the connection was made
2019-02-04 15:30:10 *Tunnelblick: Disconnecting; VPN Details… window disconnect button pressed
2019-02-04 15:30:10 *Tunnelblick: No 'pre-disconnect.sh' script to execute
2019-02-04 15:30:10 *Tunnelblick: Disconnecting using 'kill'
2019-02-04 15:30:10 event_wait : Interrupted system call (code=4)
2019-02-04 15:30:10 /sbin/route delete -net 216.162.42.66 10.0.0.1 255.255.255.255
                                        delete net 216.162.42.66: gateway 10.0.0.1
2019-02-04 15:30:10 /sbin/route delete -net 0.0.0.0 10.0.0.1 128.0.0.0
                                        delete net 0.0.0.0: gateway 10.0.0.1
2019-02-04 15:30:10 /sbin/route delete -net 128.0.0.0 10.0.0.1 128.0.0.0
                                        delete net 128.0.0.0: gateway 10.0.0.1
2019-02-04 15:30:10 Closing TUN/TAP interface
2019-02-04 15:30:10 /Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -9 -d -f -m -o -w -ptADGNWradsgnw utun2 1500 1571 10.11.42.129 255.240.0.0 init
                                        **********************************************
                                        Start of output from client.down.tunnelblick.sh
                                        Cancelled monitoring of system configuration changes
                                        Restored the DNS and SMB configurations
                                        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
                                        Not notifying mDNSResponderHelper that the DNS cache was flushed because it is not running
                                        /Library/Application Support/Tunnelblick/expect-disconnect/ALL does not exist
                                        End of output from client.down.tunnelblick.sh
                                        **********************************************
2019-02-04 15:30:10 SIGTERM[hard,] received, process exiting
2019-02-04 15:30:10 MANAGEMENT: >STATE:1549323010,EXITING,SIGTERM,,,,,
2019-02-04 15:30:11 *Tunnelblick: No 'post-disconnect.sh' script to execute
2019-02-04 15:30:12 *Tunnelblick: Expected disconnection occurred.

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

"Sanitized" full configuration file

###############################################################################
# OpenVPN 2.0 Sample Configuration File
#
# !!! AUTO-GENERATED  !!!
#
# !!! YOU HAVE TO REVIEW IT BEFORE USE AND MODIFY IT AS NECESSARY !!!
#
# This configuration file is auto-generated. You might use this config file
# However, before you try it, you should review the descriptions of the file
# to determine the necessity to modify to suitable for your real environment.
# If necessary, you have to modify a little adequately on the file.
# For example, the IP address or the hostname as a destination VPN Server
# should be confirmed.
#
# Note that to use OpenVPN 2.0, you have to put the certification file of
# the destination VPN Server on the OpenVPN Client computer when you use this
# config file. Please refer the below descriptions carefully.


###############################################################################
# Specify the type of the layer of the VPN connection.
#
# To connect to the VPN Server as a "Remote-Access VPN Client PC",
#  specify 'dev tun'. (Layer-3 IP Routing Mode)
#
# To connect to the VPN Server as a bridging equipment of "Site-to-Site VPN",
#  specify 'dev tap'. (Layer-2 Ethernet Bridgine Mode)

dev tun


###############################################################################
# Specify the underlying protocol beyond the Internet.
# Note that this setting must be correspond with the listening setting on
# the VPN Server.
#
# Specify either 'proto tcp' or 'proto tcp'.

proto tcp


###############################################################################
# The destination hostname / IP address, and port number of
# the target VPN Server.
#
# You have to specify as 'remote <HOSTNAME> <PORT>'. You can also
# specify the IP address instead of the hostname.
#
# Note that the auto-generated below hostname are a "auto-detected
# IP address" of the VPN Server. You have to confirm the correctness
# beforehand.
#
# When you want to connect to the VPN Server by using TCP protocol,
# the port number of the destination TCP port should be same as one of
# the available TCP listeners on the VPN Server.
#
# When you use UDP protocol, the port number must same as the configuration
# setting of "OpenVPN Server Compatible Function" on the VPN Server.

# Note: The below hostname is came from the Dynamic DNS Client function
#       which is running on the VPN Server. If you don't want to use
#       the Dynamic DNS hostname, replace it to either IP address or
#       other domain's hostname.

remote us.[vpn provider redacted] 443


###############################################################################
# The HTTP/HTTPS proxy setting.
#
# Only if you have to use the Internet via a proxy, uncomment the below
# two lines and specify the proxy address and the port number.
# In the case of using proxy-authentication, refer the OpenVPN manual.

;http-proxy-retry
;http-proxy [proxy server] [proxy port]


###############################################################################
# The encryption and authentication algorithm.
#
# Default setting is good. Modify it as you prefer.
# When you specify an unsupported algorithm, the error will occur.
#
# The supported algorithms are as follows:
#  cipher: [NULL-CIPHER] NULL AES-128-CBC AES-192-CBC AES-256-CBC BF-CBC
#          CAST-CBC CAST5-CBC DES-CBC DES-EDE-CBC DES-EDE3-CBC DESX-CBC
#          RC2-40-CBC RC2-64-CBC RC2-CBC
#  auth:   SHA SHA1 MD5 MD4 RMD160

cipher AES-256-CBC
auth SHA256
#auth-nocache


##############################################################################
# OpenVPN connects to the server, but the VPN does not change. Attempted
# troubleshooting for this problem goes below this line.

redirect-gateway def1


###############################################################################
# Other parameters necessary to connect to the VPN Server.
#
# It is not recommended to modify it unless you have a particular need.

resolv-retry infinite
nobind
persist-key
persist-tun
client
verb 3
auth-user-pass

verify-x509-name vpn.[vpn provider redacted] name

#remote-cert-tls server
#remote-cert-ku f6

dhcp-option DNS 8.8.8.8
dhcp-option DNS 8.8.4.4

###############################################################################
# The certificate file of the destination VPN Server.
#
# The CA certificate file is embedded in the inline format.
# You can replace this CA contents if necessary.
# Please note that if the server certificate is not a self-signed, you have to
# specify the signer's root certificate (CA) here.

<ca>
 [Security-related line(s) omitted]
</ca>


###############################################################################
# The client certificate file (dummy).
#
# In some implementations of OpenVPN Client software
# (for example: OpenVPN Client for iOS),
# a pair of client certificate and private key must be included on the
# configuration file due to the limitation of the client.
# So this sample configuration file has a dummy pair of client certificate
# and private key as follows.

<cert>
 [Security-related line(s) omitted]
</cert>

<key>
 [Security-related line(s) omitted]
</key>





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

Network services:

An asterisk (*) denotes that a network service is disabled.
Wi-Fi
Bluetooth PAN
Thunderbolt Bridge

Wi-Fi Power (en0): On

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

ifconfig output:

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
    options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
    inet 127.0.0.1 netmask 0xff000000
    inet6 ::1 prefixlen 128
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
    nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
XHC20: flags=0<> mtu 0
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
    options=60<TSO4,TSO6>
    ether 4a:00:04:e4:09:30
    media: autoselect <full-duplex>
    status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
    options=60<TSO4,TSO6>
    ether 4a:00:04:e4:09:31
    media: autoselect <full-duplex>
    status: inactive
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    ether f4:5c:89:98:ce:8d
    inet 10.0.0.4 netmask 0xffffff00 broadcast 10.0.0.255
    media: autoselect
    status: active
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=63<RXCSUM,TXCSUM,TSO4,TSO6>
    ether 4a:00:04:e4:09:30
    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 5 priority 0 path cost 0
    member: en2 flags=3<LEARNING,DISCOVER>
            ifmaxaddr 0 port 6 priority 0 path cost 0
    media: <unknown type>
    status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
    inet6 fe80::50f8:413f:4221:b640%utun0 prefixlen 64 scopeid 0x9
    nd6 options=201<PERFORMNUD,DAD>
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
    ether 06:5c:89:98:ce:8d
    media: autoselect
    status: inactive
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484
    ether 3a:ce:95:8f:d8:1d
    inet6 fe80::38ce:95ff:fe8f:d81d%awdl0 prefixlen 64 scopeid 0xb
    nd6 options=201<PERFORMNUD,DAD>
    media: autoselect
    status: active
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
    inet6 fe80::ecf3:9c94:5aa:c27%utun1 prefixlen 64 scopeid 0xc
    nd6 options=201<PERFORMNUD,DAD>



I took out the console log, it didn't seem helpful and it had a lot of personal/repetitive data.

Tunnelblick developer

unread,
Feb 5, 2019, 8:22:21 AM2/5/19
to tunnelblick-discuss
The only clue to what's going on that I see is here:

2019-02-04 15:29:53 Opening utun (connect(AF_SYS_CONTROL)): Resource busy (errno=16)
2019-02-04 15:29:53 Opening utun (connect(AF_SYS_CONTROL)): Resource busy (errno=16)
2019-02-04 15:29:53 Opened utun device utun2

This means that there were already "utun0" and "utun1" devices, possibly left over from earlier, failed attempts to connect. Try restarting your computer to remove them, and then try to connect again.

(The two extra utuns are also seen in the ifconfig output at the end of your post.)

Note that the "Route all IPv4 through the VPN" checkbox starts OpenVPN with the "redirect-gateway def1" option, so adding that to the configuration file is redundant. But it won't do any harm.

Tunnelblick Temporary

unread,
Feb 5, 2019, 3:18:24 PM2/5/19
to tunnelblick-discuss
Unfortunately, I restarted it several times. No luck.
Reply all
Reply to author
Forward
0 new messages