Okay, well, it works, but of the six Mac users in my office, I'm the only one who got it working out of the box. Everyone else is having massive issues. It's not clear, but for some reason the daemons aren't getting the ISAKMP return from the VPN server. It works fine here, on a 2x2 rev. A G5 (10.4.8), but a friend w/ a rev. B machine has no luck at all. It's a pretty buggy product. Example: the SecureClient GUI is only supposed to tickle the daemons when there's an update, but it's broken. It consumes one full CPU worth of time in UNIX system calls (300K+/sec) for no apparent return whatsoever. I actually got it to work using only the CLI tools, and now the system barely ticks over. I have to say, that having been a network engineer for over ten years now, that this product is quite possibly the worst VPN software ever. I honestly think my install is a fluke, and that it shouldn't have worked at all.

hi marp, would you please share your knowledge about using the clientin CLI only? i'm very interestred. i need to use it, but it gives me high cpu load, too, and via airport even kernel panics. thanks!