On Tuesday 24 August 2004 13:21, Shawn Grover wrote: > The target server is a Win2003 VPN server. I'm not sure what MS put in > there in way of VPN, guess I'll have to research this a bit more.
This will be IPSec. I'd bet money on it. This is good, both in terms of security as well as support/interoperability. > I understood the IPCop VPN configuration to be for connecting at the > firewall level - is this wrong?. I'm only looking for a workstation IPcop supports site to site VPNS, as well as being the site in a client to site topology. I was thinking that if you had a home network, you might as well just set it up as a site, and do a site to site connection. That obviously doesn't always work, and it sounds like yours is a case where it won't. > connection to a remote network. The remote network is already configured > to accept VPN traffic. Isn't it possible to set up a VPN Client utility > for this? Are there any available? or are they part of the Openswan type > packages? (Or am I stuck with an MS frame of mind that is not quite > correct?) Slow down... :) How about yes, yes, yes, and (no). :) These are generally called road warrior connections in the OSS world. I've never heard it used in the closed source side of things, though admittedly, I don't really follow/care about that side either. Start with these. Some will be irrelevant, depending on weather you authenticate with an IP/Shared Password combo, or if you use a certificate. http://www.natecarlson.com/linux/ipsec-x509.php http://www.metz.supelec.fr/metz/personnel/sabatier_fab/grid/roadwarrior.html http://www.fw-1.de/aerasec/ng/vpn-freeswan/CP-FW1-NG+Linux-FreeSWAN-RoadWarrior.html Hope that helps... Kev. _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
