![]() Tunnelblick's latest beta version fixes the problem for most users: I wonder what the underlying problem actually is. ![]() They suggest clicking that they DO NOT have config files, then replacing the sample on with the one I've been supplied by my VPN service, while others suggest that installing the beta version will fix the issue. I have no hope the VPN service help desk will be able to figure this out by themselves.ĮTA: The discussion group jkbull cited had had a recent citation of the same problem: elblick When I get the energy to research and write my own config files I'll try it again. OTOH, I'm doing nothing NSA would care about and native L2TP/IPSec is good enough for Starbucks and motels. It also uninstalled easily, given that I installed normally. OpenVPN installed easily enough, but the config file supplied by my VPN service would not load, so it was useless, at least for now. Thanks, I did try it, primarily because L2TP/IPSec is potentially compromised. The best place for help with Tunnelblick is the Tunnelblick Discussion Group.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |