![]() ![]() ![]() 08:46:27.391335 *Tunnelblick: Attempting connection with AAAA using shadow copy Set nameserver = 769 monitoring connection Log file trying to VPN to work from home. Iptables -t nat -A POSTROUTING -o `get_wanface` -j MASQUERADE Iptables -I OUTPUT -i `get_wanface` -dport 443 -j ACCEPT Iptables -I OUTPUT -i `get_wanface` -dport 1194 -j ACCEPT Setenv opt tls-version-min 1.0 or-highest My home router/DNS is .1 and that DNS being wrongly used instead of the work DNS. Here is an example where I query the DNS when I am VPN'ed into the work DNS. However, when I VPN from home to other VPN servers, the remote DNS is used and everything works fine. It seems that when I am home and trying to connect to work, I end up with my home router being the DNS (.1) and not the work DNS. I have no issues VPNing to work from Starbucks or any location outside of my home. TUNNELBLICK 2.0 PROI am currently having trouble using an OpenVPN config on Tunnelblick 3.8.0beta01 (build 5330) on my MacBook Pro using Mojave 10.14.5 to VPN into work from home with my home Netgear 7000 router running DD-WRT v3.0-r38159 std (01/02/19). TUNNELBLICK 2.0 HOW TOMy theory is that it centers around DHCP lease time but I haven't been able to figure out how to check that on OSX with an OpenVPN tun interface.Posted: Fri 18:40 Post subject: OpenVPN Client DNS Issues at Home, Fine at Other Locations I can actually watch the throughput drop to 0 within 10 seconds of the 10 minute mark. I've attempted and been able to replicate this behavior in both Tunnelblick and Viscosity. My routing table doesn't appear to change. It seems to take about 10 minutes for Viscosity to notice that the connection has failed and attempt to renegotiate. Jan 08 09:57:19: Initialization Sequence Completed Jan 08 09:57:19: NOTE: Tried to delete pre-existing tun/tap instance - No Problem if failure Jan 08 09:57:19: TUN/TAP device /dev/tun0 opened Jan 08 09:57:16: LZO compression initialized Jan 08 09:57:16: NOTE: OpenVPN 2.1 requires '-script-security 2' or higher to call user-defined scripts or executables TUNNELBLICK 2.0 VERIFICATIONJan 08 09:57:16: WARNING: No server certificate verification method has been enabled. OpenVPN 2.0-beta16 and earlier used 5000 as the default port. Jan 08 09:57:16: IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. Jan 08 09:57:15: SIGUSR1 received, process restarting Jan 08 09:57:15: Inactivity timeout (-ping-restart), restarting Jan 08 09:37:12: Initialization Sequence Completed Jan 08 09:37:12: NOTE: Tried to delete pre-existing tun/tap instance - No Problem if failure Jan 08 09:37:12: TUN/TAP device /dev/tun0 opened Jan 08 09:37:09: LZO compression initialized ![]() Jan 08 09:37:09: WARNING: this configuration may cache passwords in memory - use the auth-nocache option to prevent this Jan 08 09:37:07: NOTE: OpenVPN 2.1 requires '-script-security 2' or higher to call user-defined scripts or executables Jan 08 09:37:07: WARNING: No server certificate verification method has been enabled. Jan 08 09:37:07: IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. Jan 08 09:37:05: Connection is reachable. Jan 08 09:37:05: Checking reachability status of connection. Jan 08 09:37:05: Viscosity OpenVPN Engine Started My VPN connection seems to be fine for almost exactly 10 minutes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |