Tunnelblick 4.0.0beta15 (build 5950) - mistake

[histo_ostrow]

Tunnelblick 4.0.0beta15 (build 5950) installed yesterday

Once VPN connected successfully , wifi is switching off :( look at the pictures given below, wifi icon

When returned to version 4.0.0beta 13, everything is working absolutely fine

Beta14 not tested

There is no possibility to even switch on wifi when connected thru VPN…..

Moreover, when I use OpenVPN Connect also everything works fine…..

Once tunnelblick is off, wifi is back correctly

MacOS Sonoma installed

Regards

Cezary

Sent from my MacBookPro

[Tunnelblick developer]

Please post the diagnostic info obtained by following the instructions at Read Before You Post for both 4.0.0beta13 and 4.0.0beta15. (If you can, it would help if you also posted the info from 4.0.0beta14, too.)

[histo_ostrow]

Report form Mac's Console app created by system during connection Tunnelblick in this the newest beta version:

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               process-network-changes [5918]
Path:                  /Applications/Tunnelblick.app/Contents/Resources/process-network-changes
Identifier:            process-network-changes
Version:               ???
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               0

Date/Time:             2024-02-24 18:23:08.0032 +0100
OS Version:            macOS 14.4 (23E5205c)
Report Version:        12
Anonymous UUID:        B2FE01AD-74E9-6D1A-49DE-B993515EEEF0


Time Awake Since Boot: 9600 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   process-network-changes [5918]

Application Specific Information:
abort() called


Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib               0x181f2aa60 __pthread_kill + 8
1   libsystem_pthread.dylib             0x181f62c20 pthread_kill + 288
2   libsystem_c.dylib                   0x181e6fa20 abort + 180
3   libc++abi.dylib                     0x181f19d30 abort_message + 132
4   libc++abi.dylib                     0x181f09fe8 demangling_terminate_handler() + 348
5   libobjc.A.dylib                     0x181ba81d0 _objc_terminate() + 144
6   libc++abi.dylib                     0x181f190f4 std::__terminate(void (*)()) + 16
7   libc++abi.dylib                     0x181f1c348 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 88
8   libc++abi.dylib                     0x181f1c28c __cxa_throw + 308
9   libobjc.A.dylib                     0x181b9e8f0 objc_exception_throw + 420
10  CoreFoundation                       0x1821aa9f0 _CFThrowFormattedException + 108
11  CoreFoundation                       0x18202e2ac -[__NSCFString substringWithRange:] + 280
12  process-network-changes             0x100e65120 main + 216
13  dyld                                 0x181bda0e0 start + 2360

Thread 1:
0   libsystem_pthread.dylib             0x181f5dd20 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib             0x181f5dd20 start_wqthread + 0


Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000000000000   x1: 0x0000000000000000   x2: 0x0000000000000000   x3: 0x0000000000000000
    x4: 0x0000000181f1e2cb   x5: 0x000000016ef9a770   x6: 0x000000000000006e   x7: 0x0000000000000000
    x8: 0xedda2cc65ad95741   x9: 0xedda2cc7b31c2d81  x10: 0x0000000000000200  x11: 0x000000000000000b
   x12: 0x0000000000000000  x13: 0x00000000001ff800  x14: 0x00000000000007fb  x15: 0x0000000087031817
   x16: 0x0000000000000148  x17: 0x00000001f3fc2aa0  x18: 0x0000000000000000  x19: 0x0000000000000006
   x20: 0x00000001e9c57ac0  x21: 0x0000000000000103  x22: 0x00000001e9c57ba0  x23: 0x00000001e23ec19b
   x24: 0x00000001eeaf3748  x25: 0x0000000100e68518  x26: 0x0000000000000000  x27: 0x0000000000000000
   x28: 0x0000000000000000   fp: 0x000000016ef9a6e0   lr: 0x0000000181f62c20
    sp: 0x000000016ef9a6c0   pc: 0x0000000181f2aa60 cpsr: 0x40001000
   far: 0x0000000000000000  esr: 0x56000080  Address size fault

Binary Images:
       0x100e64000 -        0x100e67fff process-network-changes (*) <3fa4ae3e-a597-369c-ae35-55ff4bf8129e> /Applications/Tunnelblick.app/Contents/Resources/process-network-changes
       0x181f21000 -        0x181f5bffb libsystem_kernel.dylib (*) <61347bab-2217-3036-89db-7014dcfbdc88> /usr/lib/system/libsystem_kernel.dylib
       0x181f5c000 -        0x181f68fff libsystem_pthread.dylib (*) <45239f06-cc53-36d0-9933-7776ac7ea2fa> /usr/lib/system/libsystem_pthread.dylib
       0x181df9000 -        0x181e77ff3 libsystem_c.dylib (*) <1aae32b6-eedc-3a8e-912e-abbe4f4dceca> /usr/lib/system/libsystem_c.dylib
       0x181f05000 -        0x181f20ffb libc++abi.dylib (*) <4fed965b-18ad-3a4f-8928-1f0a3c35345f> /usr/lib/libc++abi.dylib
       0x181b84000 -        0x181bd3d83 libobjc.A.dylib (*) <56738c8e-349b-3e17-a584-12838044dcca> /usr/lib/libobjc.A.dylib
       0x181fc4000 -        0x18249cfff com.apple.CoreFoundation (6.9) <0d151a83-1e9a-3e46-8948-20e3720fcee5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
       0x181bd4000 -        0x181c5c9db dyld (*) <f39317de-f090-3584-8d29-8547669bc1bb> /usr/lib/dyld
               0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=648.2M resident=0K(0%) swapped_out_or_unallocated=648.2M(100%)
Writable regions: Total=539.7M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=539.7M(100%)

                                VIRTUAL   REGION
REGION TYPE                        SIZE    COUNT (non-coalesced)
===========                     =======  =======
Activity Tracing                   256K        1
Kernel Alloc Once                   32K        1
MALLOC                           530.2M       13
MALLOC guard page                   96K        6
STACK GUARD                       56.0M        3
Stack                             9264K        3
__AUTH                             343K       67
__AUTH_CONST                      4088K      148
__DATA                            1767K      143
__DATA_CONST                      4177K      150
__DATA_DIRTY                       365K       58
__LINKEDIT                       525.3M        2
__OBJC_RO                         71.7M        1
__OBJC_RW                         2195K        1
__TEXT                           122.8M      157
dyld private memory                272K        2
mapped file                         64K        1
shared memory                       80K        4
===========                     =======  =======
TOTAL                              1.3G      761

--
You received this message because you are subscribed to the Google Groups "tunnelblick-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tunnelblick-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tunnelblick-discuss/7e32d3f1-70bf-4235-9dae-1864ab6ba6e4n%40googlegroups.com.

[Tunnelblick developer]

Thanks. Please post the diagnostic info obtained by following the instructions at Read Before You Post for both 4.0.0beta13 and 4.0.0beta15. (If you can, it would help if you also posted the info from 4.0.0beta14, too.)

[histo_ostrow]

Hello, as mentioned earlier, I do not suffer any problems with tunnelblick app, which works fine. Nevertheless beta 15 simply drops wifi: once app is connecting (successfully) then (literally at this moment) wifi is automatically switching off. Once connecting (tunnel) is off, wifi is immediately returning on.

When I revert back to beta 13, everything is working fine i.e. even if tunnel is active, wifi remains connected. Upgrading to beta 15 again, problem with dropping wifi returns back. There is clearly a bug in the beta 15 version, so I sent a report from the MacOS console, which appears every time I try to connect via tunnelblick Beta 15. If I install Beta 13, these reports do not appear in the MacOS console, if I install the Beta 15 version, the report is created every time I get a connection (tunnel)

To view this discussion on the web visit https://groups.google.com/d/msgid/tunnelblick-discuss/00e8d03a-32ea-42d8-a415-eb05cf0636a4n%40googlegroups.com.

[Tunnelblick developer]

Although you say you "do not suffer any problems with tunnelblick app, which works fine", obviously there is are two problems:

• It turns off Wi-Fi when you connect; and
• Tunnelblick 4.0.0beta15 crashes when you connect.

The problems could be caused by any number of things (macOS problems, Tunnelblick problems, configuration problems, etc.), and the diagnostic info will help us diagnose, and hopefully fix, them. 

So, for the third time, please post the diagnostic info obtained by following the instructions at Read Before You Post for both 4.0.0beta13 and 4.0.0beta15. (If you can, it would help if you also posted the info from 4.0.0beta14, too.)

[histo_ostrow]

*Tunnelblick: macOS 14.4 (23E5205c); Tunnelblick 4.0.0beta15 (build 5950); prior version 4.0.0beta13 (build 5930); Admin user
git commit 392fcb8abec4c14f322f159c1392a8ea4ff616e1
The Tunnelblick.app process is not being translated (arm64)
System Integrity Protection is enabled
Model: MacBookPro18,3

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

Configuration c

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

client
dev tun
proto udp
remote xxx.xxx.xxx.xxx 32000
resolv-retry infinite
nobind
persist-key
persist-tun
pkcs12 xxxxxxxx
remote-cert-tls server
tls-auth xxx.key 1
disable-dco
cipher xxxxxxxx
data-ciphers xxxxxxxxxxxxxxx
tls-ciphersuites TLS_xxxxxxxxxxxxxxxxxxx
tls-cipher xxxxxxxxxxxxxxxxxx
auth xxxxxxx
verb xxxxx
tun-mtu xxxxx
mssfix xxxxxxx
auth-nocache

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

Files in xxxxxxxx.tblk:
      Contents/Resources/c.s….xxxxxx
      Contents/Resources/xxxxxx
      Contents/Resources/xxxxxx
      Contents/Resources/xxxxxxxx
      Contents/Resources/xxxxxxxxxx

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

Configuration preferences:

autoConnect = 0
-onSystemStart = 0
-notMonitoringConnection = 0
-routeAllTrafficThroughVpn = 0
-keychainHasPrivateKey = 1
-openvpnVersion = -
-notOKToCheckThatIPAddressDidNotChangeAfterConnection = 0
-keepConnected = 1
-doNotDisconnectOnSleep = 1
-doNotDisableIpv6onTun = 0
-disableSecondaryNetworkServices = 1
-allowChangesToManuallySetNetworkSettings = 0
-lastConnectionSucceeded = 1
-tunnelDownSoundName = Blow
-tunnelUpSoundName = Glass

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

Wildcard preferences:

-notOKToCheckThatIPAddressDidNotChangeAfterConnection = 0

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

Program preferences:

launchAtNextLogin = 1
tunnelblickVersionHistory = (
    "4.0.0beta15 (build 5950)",
    "4.0.0beta13 (build 5930)",
    "4.0.0beta15 (build 5950)",
    "4.0.0beta13 (build 5930)",
    "4.0.0beta15 (build 5950)",
    "4.0.0beta13 (build 5930)",
    "4.0.0beta12 (build 5920)"
)
lastLaunchTime = 730553284.009307
showConnectedDurations = 1
lastLanguageAtLaunchWasRTL = 0
connectionWindowDisplayCriteria = showWhenConnecting
maxLogDisplaySize = 102400
lastConnectedDisplayName = xxxxxxPC
keyboardShortcutIndex = 1
updateCheckAutomatically = 1
NSWindow Frame SettingsSheetWindow = 348 153 829 548 0 0 1512 944
NSWindow Frame ConnectingWindow = 561 545 389 217 0 0 1512 944
NSWindow Frame SUStatusFrame = 556 618 400 135 0 0 1512 944
NSWindow Frame SUUpdateAlert = 446 420 620 398 0 0 1512 944
detailsWindowFrameVersion = 5950
detailsWindowFrame = {{592, 113}, {920, 522}}
detailsWindowLeftFrame = {{0, 0}, {167, 402}}
detailsWindowViewIndex = 0
detailsWindowConfigurationsTabIdentifier = log
leftNavSelectedDisplayName = xxxxxxx
AdvancedWindowTabIdentifier = connectingAndDisconnecting
haveDealtWithOldTunTapPreferences = 1
haveDealtWithAlwaysShowLoginWindow = 1
haveDealtWithOldLoginItem = 1
haveDealtWithAfterDisconnect = 1
SUEnableAutomaticChecks = 1
SUScheduledCheckInterval = 86400
SULastCheckTime = 2024-02-25 11:29:40 +0000
SUHasLaunchedBefore = 1

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

Forced preferences:

(None)

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

Deployed forced preferences:

(None)

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

Tunnelblick Kext Policy Data:



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

Tunnelblick Log:

2024-02-25 16:11:15.142298 *Tunnelblick: macOS 14.4 (23E5205c); Tunnelblick 4.0.0beta15 (build 5950); prior version 4.0.0beta13 (build 5930)
2024-02-25 16:11:15.595380 *Tunnelblick: Cannot recognize the xxxxxxxx-loadTap preference value of '(null)', so Tunnelblick will not load the tap kext
2024-02-25 16:11:15.625809 *Tunnelblick: Attempting connection with xxxxx using shadow copy; Set nameserver = 0x00000301; monitoring connection
2024-02-25 16:11:15.626385 *Tunnelblick: openvpnstart start xxxxxx.tblk 50583 0x00000301 0 1 0 0x0610c130 -ptADGNWradsgnw 2.6.9-openssl-3.0.13 <password>
2024-02-25 16:11:15.671333 *Tunnelblick: openvpnstart starting OpenVPN
2024-02-25 16:11:16.339548 OpenVPN 2.6.9 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [LZ4] [MH/RECVDA] [AEAD]
2024-02-25 16:11:16.339741 library versions: OpenSSL 3.0.13 30 Jan 2024, LZO 2.10
2024-02-25 16:11:16.341797 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:50583
2024-02-25 16:11:16.341863 Need hold release from management interface, waiting...
2024-02-25 16:11:16.892229 *Tunnelblick: openvpnstart log:
     OpenVPN started successfully.
     Command used to start OpenVPN (one argument per displayed line):
          /Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.6.9-openssl-3.0.13/openvpn
          --daemon
          --log-append /Library/Application Support/Tunnelblick/Logs/-SUsers-Sxxxxxx-SLibrary-SApplication Support-STunnelblick-SConfigurations-Sxxxxxxxx.tblk-SContents-SResources-Sconfig.ovpn.769_0_1_0_101761328.50583.openvpn.log
          --cd /Library/Application Support/Tunnelblick/Users/xxxxxx/xxxxxxxx.tblk/Contents/Resources
          --machine-readable-output
          --setenv IV_GUI_VER "net.tunnelblick.tunnelblick 5950 4.0.0beta15 (build 5950)"
          --verb 3
          --config /Library/Application Support/Tunnelblick/Users/xxxxx/xxxxxxxx.tblk/Contents/Resources/config.ovpn
          --setenv TUNNELBLICK_CONFIG_FOLDER /Library/Application Support/Tunnelblick/Users/xxxxxx/xxxxxx.tblk/Contents/Resources
          --verb 3
          --cd /Library/Application Support/Tunnelblick/Users/xxxxx/xxxxxxxx.tblk/Contents/Resources
          --management 127.0.0.1 50583 /Library/Application Support/Tunnelblick/Mips/xxxxxxxx.tblk.mip
          --setenv IV_SSO webauth
          --management-query-passwords
          --management-hold
          --script-security 2
          --route-up /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -9 -x -d -f -m -w -ptADGNWradsgnw
          --down /Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -9 -x -d -f -m -w -ptADGNWradsgnw
2024-02-25 16:11:16.902179 MANAGEMENT: Client connected from [AF_INET]xxxxxxxxxx:59031
2024-02-25 16:11:16.982094 MANAGEMENT: CMD 'pid'
2024-02-25 16:11:16.982195 MANAGEMENT: CMD 'auth-retry interact'
2024-02-25 16:11:16.982251 MANAGEMENT: CMD 'state on'
2024-02-25 16:11:16.982292 MANAGEMENT: CMD 'state'
2024-02-25 16:11:16.982364 MANAGEMENT: CMD 'bytecount 1'
2024-02-25 16:11:16.982971 *Tunnelblick: Established communication with OpenVPN
2024-02-25 16:11:16.983752 *Tunnelblick: >INFO:OpenVPN Management Interface Version 5 -- type 'help' for more info
2024-02-25 16:11:16.984511 MANAGEMENT: CMD 'hold release'
2024-02-25 16:11:16.984695 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2024-02-25 16:11:16.992966 *Tunnelblick: Obtained passphrase from the Keychain
2024-02-25 16:11:16.993566 MANAGEMENT: CMD 'password [...]'
2024-02-25 16:11:17.007718 TCP/UDP: Preserving recently used remote address: [AF_INET]xxx.xxx.xxx.xxx:xxxxxx
2024-02-25 16:11:17.007885 Socket Buffers: R=[786896->786896] S=[9216->9216]
2024-02-25 16:11:17.007908 UDPv4 link local: (not bound)
2024-02-25 16:11:17.007929 UDPv4 link remote: [AF_INET]xxx.xxx.xxx.xxx:xxx
2024-02-25 16:11:17.007974 MANAGEMENT: >STATE:1708xxxxxxxx,WAIT,,,,,,
2024-02-25 16:11:17.055034 MANAGEMENT: >STATE:1708xxxxxxxx,AUTH,,,,,,
2024-02-25 16:11:17.055173 TLS: Initial packet from [AF_INET]xxx.xxx.xxx.xxx:xxxxx, sid=c24437xxxxxxxxx
2024-02-25 16:11:17.065291 VERIFY OK: depth=1, C=xx, ST=xxxx, L=xxxxxxx, O=xxxxxx, OU=xxxxxx, CN=xxxxx, name=serverxxxx, emailAddress=xxxxx@xxxxxxx
2024-02-25 16:11:17.067104 VERIFY KU OK
2024-02-25 16:11:17.067143 Validating certificate extended key usage
2024-02-25 16:11:17.067172 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2024-02-25 16:11:17.067196 VERIFY EKU OK
2024-02-25 16:11:17.067221 VERIFY OK: depth=0, C=xx, ST=xxxx, L=xxxx, O=xxxxx, OU=xxxx, CN=xxxxxxx, name=xxxxxxx, emailAddress=xxxxxx@xx
2024-02-25 16:11:17.102363 Control Channel: TLSxxxxxxxxxxxxx
2024-02-25 16:11:17.102416 [xxxxxxx] Peer Connection Initiated with [AF_INET]xxxx.xxx.xxx.xxxxx:xxxx
2024-02-25 16:11:17.102435 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1
2024-02-25 16:11:17.102477 TLS: tls_multi_process: initial untrusted session promoted to trusted
2024-02-25 16:11:17.103063 PUSH: Received control message: 'PUSH_REPLY,route xxx.xxx.xxx.x xxx.xxx.xxx.0,route xx.xxx.xxx.0 xxx.xxx.xxx.0,sndbuf xxxxx,rcvbuf xxxx,route-gateway xx.xxx.xxx.1,topology subnet,ping xx,ping-restart 120,ifconfig xx.xxx.xxx.x xxx.xxx.xxx.0,peer-id 0,cipher xxx-xxx-xxx,protocol-flags cc-exit tls-ekm dyn-tls-crypt,tun-mtu xxxx'
2024-02-25 16:11:17.103123 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
2024-02-25 16:11:17.103144 Socket Buffers: R=[78xxxxxx->3xxxxxx] S=[xxxxx->xxxxx]
2024-02-25 16:11:17.103152 OPTIONS IMPORT: --ifconfig/up options modified
2024-02-25 16:11:17.103158 OPTIONS IMPORT: route options modified
2024-02-25 16:11:17.103165 OPTIONS IMPORT: route-related options modified
2024-02-25 16:11:17.103171 OPTIONS IMPORT: tun-mtu set to xxxx
2024-02-25 16:11:17.103640 Opened utun device utun4
2024-02-25 16:11:17.103657 MANAGEMENT: >STATE:1xxxxxx,ASSIGN_IP,,xx.xxx.xxxx.x,,,,
2024-02-25 16:11:17.103763 /sbin/ifconfig utun4 delete
                           ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address
2024-02-25 16:11:17.227336 NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
2024-02-25 16:11:17.227374 /sbin/ifconfig utun4 xx.xxx.xxxx.x xx.xxx.xxx.x netmask xxx.xxx.xxx.0 mtu xxxx up
2024-02-25 16:11:17.252158 /sbin/route add -net xx.xxx.xxx.x xx.xxx.xxx.x xx.xxx.xxx.x
                           add net xx.xxx.xxx.x: gateway xx.xxx.xxx.x
2024-02-25 16:11:17.265547 MANAGEMENT: >STATE:xxxxxxxxxxxxx,ADD_ROUTES,,,,,,
2024-02-25 16:11:17.265766 /sbin/route add -net xx.xxx.xxx.x xx.xxx.xxx.x xx.xxx.xxx.x
                           route: writing to routing socket: File exists
                           add net xx.xxx.xxx.x: gateway xx.xxx.xxx.x: File exists

2024-02-25 16:11:17.274275 /sbin/route add -net xx.xxx.xxx.x xx.xxx.xxx.x xx.xxx.xxx.x
                           route: writing to routing socket: File exists
                           add net xx.xxx.xxx.x: gateway xx.xxx.xxx.x: File exists
                           16:11:17 *Tunnelblick:  **********************************************
                           16:11:17 *Tunnelblick:  Start of output from client.up.tunnelblick.sh
                           16:11:20 *Tunnelblick:  Disabled IPv6 for 'xxxxxxxxxxxxxx'
                           16:11:20 *Tunnelblick:  Disabled IPv6 for 'Thunderbolt Bridge'
                           16:11:20 *Tunnelblick:  Disabled IPv6 for 'Wi-Fi'
                           16:11:20 *Tunnelblick:  Disabled 'Thunderbolt Bridge'
                           16:11:21 *Tunnelblick:  Disabled 'Wi-Fi'
                           16:11:21 *Tunnelblick:  DNS servers '1.1.1.1 1.0.0.1' were set manually
                           16:11:21 *Tunnelblick:  DNS servers '1.1.1.1 1.0.0.1' will be used for DNS queries when the VPN is active
                           16:11:21 *Tunnelblick:  The DNS servers include only free public DNS servers known to Tunnelblick.
                           16:11:21 *Tunnelblick:  Setting up to monitor system configuration with process-network-changes
                           16:11:21 *Tunnelblick:  Flushed the DNS cache via dscacheutil
                           16:11:21 *Tunnelblick:  /usr/sbin/discoveryutil not present. Not flushing the DNS cache via discoveryutil
                           16:11:22 *Tunnelblick:  Notified mDNSResponder that the DNS cache was flushed
                           16:11:22 *Tunnelblick:  Notified mDNSResponderHelper that the DNS cache was flushed
                           16:11:22 *Tunnelblick:  End of output from client.up.tunnelblick.sh
                           16:11:22 *Tunnelblick:  **********************************************
2024-02-25 16:11:22.155724 Initialization Sequence Completed
2024-02-25 16:11:22.155781 MANAGEMENT: >STATE:xxxxxxxxx,CONNECTED,SUCCESS,xx.xxx.xxx.x,xx.xxx.xxx.x, xxxxxxxx,,
2024-02-25 16:11:22.155842 Data Channel: cipher 'xxxxxxxxxxxxxx', peer-id: 0
2024-02-25 16:11:22.155854 Timers: ping 10, ping-restart 120
2024-02-25 16:11:22.155864 Protocol options: protocol-flags cc-exit tls-ekm dyn-tls-crypt
2024-02-25 16:11:23.287518 *Tunnelblick: Warning: DNS server address  is not being used.


2024-02-25 16:11:23.293667 *Tunnelblick: Warning: DNS server address 1.0.0.1 is being used but should not be used. That may indicate that more than one network interface is active. Tunnelblick does not support multiple active network interfaces.


2024-02-25 16:11:23.295401 *Tunnelblick: Warning: DNS server address 1.1.1.1 is being used but should not be used. That may indicate that more than one network interface is active. Tunnelblick does not support multiple active network interfaces.


2024-02-25 16:11:23.296689 *Tunnelblick: Warning: DNS server address xxxxxxxx is being used but should not be used. That may indicate that more than one network interface is active. Tunnelblick does not support multiple active network interfaces.


2024-02-25 16:11:23.297949 *Tunnelblick: Warning: DNS server address fe80::1 is being used but should not be used. That may indicate that more than one network interface is active. Tunnelblick does not support multiple active network interfaces.


2024-02-25 16:11:29.049484 *Tunnelblick: This computer's apparent public IP address (xx.xxx.xxx.x) was unchanged after the connection was made
2024-02-25 16:11:32.869999 *Tunnelblick: process-network-changes: ServerAddresses changed from
                           *
                           * to
                           *<array> {
                           *0 : 1.1.1.1
                           *1 : 1.0.0.1
                           *}
                           *pre-VPN was
                           *
2024-02-25 16:11:32.873361 *Tunnelblick: process-network-changes: ServerAddresses changed; sending USR1 to OpenVPN (process ID ) to restart the connection.

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

Installer log:

Tunnelblick installer started 2024-02-24 11:46:03.217986; getuid() = 501; geteuid() = 0; getgid() = 20; getegid() = 20
currentDirectoryPath = '/'; 1 arguments:
     0x0101
Determined username 'xxxxx' from getuid(): 501
renamex_np() tests succeeded for /Applications
renamex_np() tests succeeded for /Library/Application Support/Tunnelblick
renamex_np() tests succeeded for /Users/xxxx/Library/Application Support/Tunnelblick/Configurations
Replaced /Library/LaunchDaemons/net.tunnelblick.tunnelblick.tunnelblickd.plist
Used launchctl to load tunnelblickd
Tunnelblick installer succeeded

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

Down log:

20:05:59 *Tunnelblick:  **********************************************
20:05:59 *Tunnelblick:  Start of output from client.down.tunnelblick.sh
20:05:59 *Tunnelblick:  Cancelled monitoring system configuration changes
20:05:59 *Tunnelblick:  Re-enabled "Thunderbolt Bridge"
20:05:59 *Tunnelblick:  Re-enabled "Wi-Fi"
20:06:00 *Tunnelblick:  Restored State:DNS
20:06:00 *Tunnelblick:  Restored Setup:DNS
20:06:00 *Tunnelblick:  Restored State:SMB
20:06:01 *Tunnelblick:  Restored DNS and SMB settings
20:06:01 *Tunnelblick:  Re-enabled IPv6 (automatic) for "xxxxxxxxxxxxx"
20:06:02 *Tunnelblick:  Re-enabled IPv6 (automatic) for "Thunderbolt Bridge"
20:06:02 *Tunnelblick:  Re-enabled IPv6 (automatic) for "Wi-Fi"
20:06:02 *Tunnelblick:  Flushed the DNS cache with dscacheutil -flushcache
20:06:03 *Tunnelblick:  Notified mDNSResponder that the DNS cache was flushed
20:06:03 *Tunnelblick:  End of output from client.down.tunnelblick.sh
20:06:03 *Tunnelblick:  **********************************************

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

Previous down log:

20:05:31 *Tunnelblick:  **********************************************
20:05:31 *Tunnelblick:  Start of output from client.down.tunnelblick.sh
20:05:31 *Tunnelblick:  Cancelled monitoring system configuration changes
20:05:31 *Tunnelblick:  Re-enabled "Thunderbolt Bridge"
20:05:31 *Tunnelblick:  Re-enabled "Wi-Fi"
20:05:32 *Tunnelblick:  Restored State:DNS
20:05:32 *Tunnelblick:  Restored Setup:DNS
20:05:32 *Tunnelblick:  Restored State:SMB
20:05:32 *Tunnelblick:  Restored DNS and SMB settings
20:05:33 *Tunnelblick:  Re-enabled IPv6 (automatic) for "xxxxxxxxxxxxxxx"
20:05:33 *Tunnelblick:  Re-enabled IPv6 (automatic) for "Thunderbolt Bridge"
20:05:34 *Tunnelblick:  Re-enabled IPv6 (automatic) for "Wi-Fi"
20:05:34 *Tunnelblick:  Flushed the DNS cache with dscacheutil -flushcache
20:05:34 *Tunnelblick:  Notified mDNSResponder that the DNS cache was flushed
20:05:35 *Tunnelblick:  End of output from client.down.tunnelblick.sh
20:05:35 *Tunnelblick:  **********************************************

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

Network services:

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

Wi-Fi Power (en0): Off

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

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
anpi2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu xxxx
options=400<CHANNEL_IO>
ether e6:d4:b8:13:a1:b2
media: none
status: inactive
anpi1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu xxxx
options=400<CHANNEL_IO>
ether e6:d4:b8:13:a1:b1
media: none
status: inactive
anpi0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu xxxx
options=400<CHANNEL_IO>
ether e6:d4:b8:13:a1:b0
media: none
status: inactive
en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu xxxx
options=400<CHANNEL_IO>
ether e6:d4:b8:13:a1:90
nd6 options=201<PERFORMNUD,DAD>
media: none
status: inactive
en5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu xxxx
options=400<CHANNEL_IO>
ether e6:d4:b8:13:a1:91
nd6 options=201<PERFORMNUD,DAD>
media: none
status: inactive
en6: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu xxxx
options=400<CHANNEL_IO>
ether e6:d4:b8:13:a1:92
nd6 options=201<PERFORMNUD,DAD>
media: none
status: inactive
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu xxxx
options=460<TSO4,TSO6,CHANNEL_IO>
ether 36:a9:bf:e4:1b:c0
media: autoselect <full-duplex>
status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu xxxx
options=460<TSO4,TSO6,CHANNEL_IO>
ether 36:a9:bf:e4:1b:c4
media: autoselect <full-duplex>
status: inactive
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=460<TSO4,TSO6,CHANNEL_IO>
ether 36:a9:bf:e4:1b:c8
media: autoselect <full-duplex>
status: inactive
en7: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu xxxx
options=404<VLAN_MTU,CHANNEL_IO>
ether f8:e4:3b:1c:50:64
inet xx.xxx.xxx.x netmask 0xffffffc0 broadcast xx.xxx.xxx.x
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (1000baseT <full-duplex>)
status: active
ap1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu xxxx
options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
ether fa:4d:89:8a:ed:5d
inet6 fe80::f84d:89ff:fe8a:ed5d%ap1 prefixlen 64 scopeid 0xe
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
en0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu xxxx
options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
ether f8:4d:89:8a:ed:5d
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: inactive
bridge0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu xxxx
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 36:a9:bf:e4:1b:c0
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 0x0
member: en1 flags=3<LEARNING,DISCOVER>
       ifmaxaddr 0 port 10 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
       ifmaxaddr 0 port 11 priority 0 path cost 0
member: en3 flags=3<LEARNING,DISCOVER>
       ifmaxaddr 0 port 12 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: <unknown type>
status: inactive
awdl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu xxxx
options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
ether 66:53:05:eb:88:c4
inet6 fe80::6453:5ff:feeb:88c4%awdl0 prefixlen 64 scopeid 0x11
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (<unknown type>)
status: inactive
llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 66:53:05:eb:88:c4
inet6 fe80::6453:5ff:feeb:88c4%llw0 prefixlen 64 scopeid 0x12
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
inet6 fe80::240b:5335:beb3:4572%utun0 prefixlen 64 scopeid 0x13
nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::9aa8:1acd:4440:11f3%utun1 prefixlen 64 scopeid 0x14
nd6 options=201<PERFORMNUD,DAD>
utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
inet6 fe80::401c:a266:d339:2495%utun2 prefixlen 64 scopeid 0x15
nd6 options=201<PERFORMNUD,DAD>
utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000
inet6 fe80::ce81:b1c:bd2c:69e%utun3 prefixlen 64 scopeid 0x16
nd6 options=201<PERFORMNUD,DAD>
vmenet0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
ether de:80:33:69:78:e7
media: autoselect
status: active
bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=3<RXCSUM,TXCSUM>
ether fa:4d:89:a8:83:64
inet 172.16.68.1 netmask 0xffffff00 broadcast xx.xxx.xxx.xvvv
inet6 fe80::f84d:89ff:fea8:8364%bridge100 prefixlen 64 scopeid 0x18
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 0x0
member: vmenet0 flags=3<LEARNING,DISCOVER>
       ifmaxaddr 0 port 23 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
vmenet1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu xxxx
ether ee:e6:04:e2:0d:ab
media: autoselect
status: active
bridge101: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu xxxx
options=3<RXCSUM,TXCSUM>
ether fa:4d:89:a8:83:65
inet 172.16.30.1 netmask 0xffffff00 broadcast xx.xxx.xxx.x
inet6 fe80::f84d:89ff:fea8:8365%bridge101 prefixlen 64 scopeid 0x1a
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 0x0
member: vmenet1 flags=3<LEARNING,DISCOVER>
       ifmaxaddr 0 port 25 priority 0 path cost 0
member: vmenet2 flags=3<LEARNING,DISCOVER>
       ifmaxaddr 0 port 27 priority 0 path cost 0
member: vmenet3 flags=3<LEARNING,DISCOVER>
       ifmaxaddr 0 port 28 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
vmenet2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu xxxx
ether 22:ce:7b:23:79:c0
media: autoselect
status: active
vmenet3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu xxxx
ether e6:5c:2f:27:14:bc
media: autoselect
status: active
utun4: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu xxxx
inet xx.xxx.xxx.x --> xx.xxx.xxx.x netmask 0xffffff00

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

Non-Apple kexts that are loaded:

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  261    0 0                  0x654      0x654      com.samsung.portablessd.driver (2.0.0) F77A0391-65C1-37C5-ABD2-8976DFFA8896 <57 56 5 4 3>

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

Quit Log:

2024-02-24 20:06:16.050124 applicationShouldTerminate: termination because of shutdown; delayed until 'shutdownTunnelblick' finishes)
2024-02-24 20:06:16.204738 shutDownTunnelblick: started.
2024-02-24 20:06:16.265390 shutDownTunnelblick: Starting cleanup.
2024-02-24 20:06:16.292791 cleanup: Entering cleanup
2024-02-24 20:06:16.312283 synchronized user defaults
2024-02-24 20:06:16.776967 Set up flag files for shutting down the computer and expecting all configurations to be disconnected
2024-02-24 20:06:16.777611 doDisconnectionsForShuttingDownComputer: Set 'expect disconnect 1 ALL'
2024-02-24 20:06:16.778015 Started disconnecting all configurations
2024-02-24 20:06:16.778436 Skipping cleanup because computer is shutting down or restarting
2024-02-24 20:06:16.778738 shutDownTunnelblick: Cleanup finished.
2024-02-24 20:06:16.779196 Finished shutting down Tunnelblick; allowing termination

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

Traces Log:


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

Console Log:

To view this discussion on the web visit https://groups.google.com/d/msgid/tunnelblick-discuss/4dc09f0b-6e9d-4037-a297-dfd4afb5edc7n%40googlegroups.com.

[Tunnelblick developer]

Thanks, the diagnostic info helps a lot, which is why we ask for it!

For the original problem ("wifi is switching off"), the problem appears to be the setting "Disable secondary network interfaces". You have several network services (interfaces); the primary service appears to be "ASCS-Consulting_line" (perhaps a renamed Ethernet interface?). Because of the setting, when Tunnelblick connects to the VPN, it disables the other network services, "Wi-Fi" and "Thunderbolt Bridge". When the VPN is disconnected, the services are re-enabled. So if you want to leave Wi-Fi enabled, un-check the box.

The other problem (the crash in Tunnelblick's "process-network-changes" component) is a bug in Tunnelblick 4.0.0beta15. Tunnelblick tries to implement the "Monitor network settings" checkbox in a situation that it doesn't handle properly. You should be able to avoid the crash by un-checking the "Monitor network settings" checkbox. (If it doesn't, please post new diagnostic info from connecting with the checkbox un-checked.)

Third (minor) problem: you also have a check mark in "Check if the apparent public IP address changed after connecting". In your setup, that should not be checked. Most people who use a VPN send all traffic from their computer through the VPN to the Internet. However, your setup only sends traffic destined for the VPN network through the VPN. All other traffic goes directly to the Internet without going through the VPN. That's fine, but in that case you should not check the box because it is expected that your computer's apparent public IP address will not change (because traffic to websites other than those in your VPN will not go through the VPN, so they will be from your computer's normal/regular/usual apparent public IP address).

[histo_ostrow]

I.

For the original problem ("wifi is switching off"), the problem appears to be the setting "Disable secondary network interfaces". You have several network services (interfaces); the primary service appears to be "ASCS-Consulting_line" (perhaps a renamed Ethernet interface?). yes, correct

II.

Because of the setting, when Tunnelblick connects to the VPN, it disables the other network services, "Wi-Fi" and "Thunderbolt Bridge". When the VPN is disconnected, the services are re-enabled. So if you want to leave Wi-Fi enabled, un-check the box. exactly correct ! when this option is unchecked Beta 15 does not drop wifi. But please note this option was not changed in comparison to Beta 13 and earlier versions i.e. it was always checked before.....

III.

The other problem (the crash in Tunnelblick's "process-network-changes" component) is a bug in Tunnelblick 4.0.0beta15. Tunnelblick tries to implement the "Monitor network settings" checkbox in a situation that it doesn't handle properly. You should be able to avoid the crash by un-checking the "Monitor network settings" checkbox. (If it doesn't, please post new diagnostic info from connecting with the checkbox un-checked.) Not correct. Even if unchecked, but above option checked (II nd paragraph), wifi is dropping

IV.

Third (minor) problem: you also have a check mark in "Check if the apparent public IP address changed after connecting". In your setup, that should not be checked. Most people who use a VPN send all traffic from their computer through the VPN to the Internet. However, your setup only sends traffic destined for the VPN network through the VPN. All other traffic goes directly to the Internet without going through the VPN. That's fine, but in that case you should not check the box because it is expected that your computer's apparent public IP address will not change (because traffic to websites other than those in your VPN will not go through the VPN, so they will be from your computer's normal/regular/usual apparent public IP address).

Correct, normally is unchecked, but according to your instruction, please follow point 7: https://tunnelblick.net/cBeforeYouPost.html, stating this option had to be checked. So I checked it for the purpose of gathering diagnostic data only (already unchecked)

Thank you for your stunning help and incredible skills !

To view this discussion on the web visit https://groups.google.com/d/msgid/tunnelblick-discuss/cf6cf80f-b703-40ac-b312-6034012df891n%40googlegroups.com.

[Tunnelblick developer]

II.
Because of the setting, when Tunnelblick connects to the VPN, it disables the other network services, "Wi-Fi" and "Thunderbolt Bridge". When the VPN is disconnected, the services are re-enabled. So if you want to leave Wi-Fi enabled, un-check the box. exactly correct ! when this option is unchecked Beta 15 does not drop wifi. But please note this option was not changed in comparison to Beta 13 and earlier versions i.e. it was always checked before.....

Yes, it was checked before, but it was always ignored before for setups like yours, where no OpenVPN "dhcp-option" is specified. That's why the release notes for beta 15 include:

• Allows disabling IPv6 and/or secondary network services even if no dhcp-option is specified.
  

Most people want secondary network services disabled, so that is the default. We enabled this feature in beta 15. Since the new feature affects you but you don't want it, you need to un-check the box to override the default.

III.
The other problem (the crash in Tunnelblick's "process-network-changes" component) is a bug in Tunnelblick 4.0.0beta15. Tunnelblick tries to implement the "Monitor network settings" checkbox in a situation that it doesn't handle properly. You should be able to avoid the crash by un-checking the "Monitor network settings" checkbox. (If it doesn't, please post new diagnostic info from connecting with the checkbox un-checked.) Not correct. Even if unchecked, but above option checked (II nd paragraph), wifi is dropping

Wi-Fi dropping has nothing to do with "Monitor network settings". Un-checking "Monitor network settings" should avoid the crash in process-network-changes, but that's all. It will not affect dropping Wi-Fi, which is affected only by "Disable secondary network interfaces".

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

I was trying to describe how to fix or work around two problems you were having. They are separate problems with separate fixes.

• Can you confirm that un-checking "Monitor network settings" prevents Wi-Fi from being disabled?
  
• Can you confirm that un-checking "Monitor network settings" avoids the crash in process-network-changes?
  

[histo_ostrow]

"Monitor network settings" - does not matter if it is checked or not -> always drops wifi if ",Disable secondary network interfaces" is on (checked), so this option has no influence. This is the first option in "settings"

Key-option is 4th "Disable secondary network interfaces" -> when checked wifi is dropping, when unchecked Beta 15 is going fine . Please note, according to the hint showing with this option, tunnelblick is recommending this option ON.....

[Tunnelblick developer]

I apologize, I made a copy/paste error in my earlier reply. The two questions should have been:

• Can you confirm that un-checking "Disable secondary network interfaces" prevents Wi-Fi from being disabled?
  

• Can you confirm that un-checking "Monitor network settings" avoids the crash in process-network-changes?

You've apparently answered the first question YES – ("Disable secondary network interfaces" -> when checked wifi is dropping, when unchecked Beta 15 is going fine").

But you have not answered the second question:

• Can you confirm that un-checking "Monitor network settings" avoids the crash in process-network-changes?

Please note, according to the hint showing with this option, tunnelblick is recommending this option ON.....

Correct. Both options are on by default (and "Disable secondary network interfaces" is "recommended" in its hint), because they are appropriate for most Tunnelblick setups. Your setup is unusual, so it needs unusual settings.

[histo_ostrow]

• Can you confirm that un-checking "Disable secondary network interfaces" prevents Wi-Fi from being disabled? yes
  

• Can you confirm that un-checking "Monitor network settings" avoids the crash in process-network-changes? no (details described in 1st sentence od previous mail)

"Monitor network settings" - does not matter if it is checked or not -> always drops wifi if ",Disable secondary network interfaces" is on (checked), so this option has no influence. This is the first option in "settings"

[Tunnelblick developer]

I know, and have written several times, that "Monitor network settings" does not affect dropping Wi-Fi. That's not what I'm asking.

Can you confirm that un-checking "Monitor network settings" avoids the crash in process-network-changes? no (details described in 1st sentence od previous mail)

You are saying that the process-network-changes crashes still happen even when "Monitor network settings" is not checked.

I don't see how that is possible, and would for the diagnostic info with that setting using beta 15. (And with "Disable secondary network interfaces" also not checked, since that will, as you desire, prevent Wi-Fi from being disabled.) The crash info would also be helpful.

[Tunnelblick developer]

Sorry, another typo : (

I wrote this:

I don't see how that is possible, and would for the diagnostic info with that setting using beta 15. (And with "Disable secondary network interfaces" also not checked, since that will, as you desire, prevent Wi-Fi from being disabled.) The crash info would also be helpful.

It should have been:

I don't see how that is possible, and would like to see the diagnostic info with that setting using beta 15. (And with "Disable secondary network interfaces" also not checked, since that will, as you desire, prevent Wi-Fi from being disabled.) The crash info would also be helpful.