On Dec 22, 2007, at 6:57 PM, Sunnz wrote:
Yes I have tried an OpenVPN client on a Mac before... it feels kind of
hackish to be honest... haven't tried the Windows one yet... but if
that's the only thing that works then I don't have a choice I guess.
I can understand that. What's worked really well, for me on 10.4 and
10.5, has been tunnelblick. Pop your config in to ~/Library/openvpn,
provide a path to your keys, and it "just works." Even has a handy
little icon on upper bar.
On the back end, OpenBSD supports it beautifully. I have a system
supporting two different VPN tunnels extremely well.
Thanks for the advice!
Not a problem.
I recently went through a hunt for an L2TP daemon that would work with
OpenBSD, and after a week of fruitless searching started hacking with
IPsec for other routing/tunneling needs.
Even with ipsecctl/ipsec.conf, I found things lacking. One of the
biggest problems was a lack of fine tuned control between routers and
clients. OpenVPN suffered none of these difficulties.
Quick examples:
- I could have the tunnel and the route through the tunnel, as
separate and not related.
- Another issue with NAT traversal was immediately solved.
- The PF firewall could now be applied to a specific tun interface,
and not tied to the enc0 interface (when running 2 or 3 tunnels each
having different access needs, this counts for a fair amount).
- complexity of setting up clients and server was reduced.
I have to say I started in the same boat as yourself. I wanted simple
L2TP tunneling to an OpenBSD server.
