[lug] This is a very irritating problem

[Dan Ferris]

That's the next project whenever the m0n0wall guy gets his OpenVPN 
support stable.

Dan

Kevin Fenzi wrote:

> >>>>>"Dan" == Dan Ferris <dan at usrsbin.com> writes:
>
>
> Dan> Howdy, I just got done setting up L2TP over IPSec for my wireless
> Dan> network.
>
> I'm sorry. ;)
>
> Dan> The box is a SuSE Linux 9.2 box with OpenSwan.  Before anyone
> Dan> asks, I picked OpenSWAN because
>
> Dan> a) I've used it before b) I found a really good l2tp/ipsec
> Dan> tutorial that used it.
>
> I spend several days of hard core effort trying to get ipsec working a
> few years ago. It was over complicated and confusingly documented. I
> finally gave up in disgust.
>
> Dan> Anyway, this is an extremely irritating problem.
>
> Dan> Here's the ipsec status.  Notice that there is an Active SA.
>
> Dan> ...snipp...
>
> Dan> Anyone know what I did wrong and how I can get my ipsec0
> Dan> interface back :-)
>
> I don't off hand. You might have better luck on the OpenSWAN lists?
>
> The only reason I can understand for anyone using ipsec anymore is
> that they have an endpoint that can only run ipsec (appliance, etc).
>
> Otherwise I very strongly urge you to save your sanity and switch to
> using openvpn:
>
> http://openvpn.sf.net/
>
> openvpn is easy to use, easy to setup, well documented, works
> great. Runs on windows/osx/linux/solaris. It's better in every way
> than any of the ipsec setups I have seen.
>
> Sorry to not answer your question, just hoping to save someone from
> the evils of ipsec. :)
>
> Dan> Dan
>
> kevin

_______________________________________________
Web Page:  http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
Join us on IRC: lug.boulder.co.us port=6667 channel=#colug