oneguysexperiencewithcarletonuniversityvnp2011
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | oneguysexperiencewithcarletonuniversityvnp2011 [2015/06/09 15:23] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | Connecting to Carleton University VPN with Linux | ||
+ | |||
+ | 1. Use your distro' | ||
+ | |||
+ | 2. Download the WindowsXP CISCO client from the website provided by Carleton, using the username and password supplied by Carleton. | ||
+ | |||
+ | 3. Use ' | ||
+ | |||
+ | 4. The "IPSec secret" | ||
+ | |||
+ | http:// | ||
+ | |||
+ | Decode the value of the " | ||
+ | |||
+ | 5. You are good to go. Use some variant of 'sudo vpnc-connect' | ||
+ | |||
+ | Caveats: | ||
+ | |||
+ | 1. The tiny bit of investigation I did suggested that the routing table changes were clever enough to keep the local subnet traffic routed locally, but all other traffic would be routed through the vpn. I understand that you can do more clever routing so that you could keep, say, your web surfing, through your own connection while still routing other traffic through the vpn, but I have not investigated this. | ||
+ | |||
+ | 2. The Carleton set-up seems to use password-based authentication. Superficial googling suggests that vpnc may not work so well if certificate-based authentication is required. | ||
+ | |||
+ | 3. The command-line approach described here may wreak havoc or otherwise not work with boxes running networkmanager' | ||
+ | alluded to might help in this respect. | ||
+ | |||
+ | 4. Your mileage may vary. | ||
+ | |||
+ | Credits: | ||
+ | |||
+ | http:// | ||
+ | |||
+ | Thanks also to Singer for the encouragement to 'just do it.' | ||
+ | |||
+ | Michael Walma | ||
oneguysexperiencewithcarletonuniversityvnp2011.txt · Last modified: 2015/06/09 15:23 by 127.0.0.1