# OS X 10.4.7 the DHCP-acquired DNS information is not "merged" into the System
# to make the interface functional, all by itself - *except* for one small thing: as of # - that's not directly a problem as the OS X DHCP client should do everything we need # - this means the DHCP acquisition can't complete until after this script exits # until *after* this script returns this makes sense: this script could fail in which # packets are queued up on the interface (and not actually sent over the openvpn tunnel) # - on testing w/ openvpn 2.0.5, and tcpdump on the tap interface as soon as it comes up, # to the server is available for use (ditto 'up-delay' at least for UDP) # - up: openvpn calls the 'up' script after the tun/tap interface is created, but before the link # Use in your OpenVPN config file as follows: # incorporate the DHCP-supplied DNS configuration # - uses ipconfig to acquire a DHCP lease via the OpenVPN tap interface, and scutil to
#Openvpn tunnelblick error mac osx
# A script to be used as an OpenVPN bridged (tap) up/down script on Mac OSX 10.4 Meine MacBooks versuchen sich mit folgenden Einstellungen per Tunnelblick zu verbinden: Key server.key # Local peer's private key Tls-server # Enable TLS and assume server role during TLS handshakeĬa ca.crt # Certificate authority (CA) fileĭh dh1024.pem # File containing Diffie Hellman parametersĬert server.crt # Local peer's signed certificate Keepalive 15 60 # Simplify the expression of -pingĭaemon # Become a daemon after all initializationĬlient-to-client # tells OpenVPN to internally route client-to-client trafficĭuplicate-cn # Allow multiple clients with the same common name Dev tap0 # TUN/TAP virtual network device
0 kommentar(er)
