When running the cisco client, it comes with several profiles installed. The 
regular one (umd?) Does split tunneling, using the 128.8.x.x addr for 
connections to campus IPs only. You want to use the "wireless" profile, or its 
equivalent, so it's forced to use that addr for every connection. 

Rob
*******************************************************************************
Robert Maxwell, CISSP, GCFA
Lead Incident Handler                      OIT Security, University of Maryland
rmaxwell at umd dot edu
GnuPG Public Key:   http://security.umd.edu/contact/Robert_Maxwell.asc
*******************************************************************************

-----Original Message-----
From: Andres Cimmarusti <[email protected]>
Date: Fri, 4 Dec 2009 19:26:33 
To: um-linux<[email protected]>
Subject: Re: [UM-LINUX] vpnc fails to connect to UMD

Thanks Richard. You were right. I unpacked the VPN.exe file for Windows XP 
using unzip in a terminal and I used NetworkManager to import the PCF files. 
Now it's connecting, but it's totally useless for what I need VPN for!

OIT website tells you that after connecting to UMD VPN, you should visit:

http://www.helpdesk.umd.edu/cgi-bin/checkip.pl
(or http://noc.net.umd.edu/cgi-bin/netmgr/whoami)

and make sure you are being given an IP address of the form: 128.8.xxx.xxx

When I do this using my browser (Iceweasel 3.0.6 with its user.agent renamed to 
Firefox) I get the following:

IP Resolution Check
For 128.8.xxx.xxx
The host name is: vpn1-xxx-xxx.umd.edu.
IP Resolution is OK
vpn1-xxx-xxx.umd.edu. resolves back to 128.8.xxx.xxx

Which I suppose means everything is working well. But in reality, when I go 
here to check my IP address:

http://www.whatismyip.com/

I get my usual router IP address. I then tried ifconfig and got the right IP 
address for tun0 but got my usual IP address for wlan0.

As a consequence when I try going on to scientific journals websites to get 
some papers I'm asked to log in to buy the article... I know I can get these 
through www.lib.umd.edu without VPN, but I wanted this to work.

OIT has some "known issues" 
http://www.helpdesk.umd.edu/topics/applications/vpn/3835/

Mine is not listed, but perhaps it has to do with some of the ports in my 
router not being open.

Andres Cimmarusti

http://terpconnect.umd.edu/~candres/


---- Original message ----
>Date: Fri, 4 Dec 2009 18:22:08 -0500
>From: Richard Matthew McCutchen <[email protected]>  
>Subject: Re: [UM-LINUX] vpnc fails to connect to UMD  
>To: [email protected]
>
>On Fri, 2009-12-04 at 16:47 -0500, Andres Cimmarusti wrote:
>> I set up vpnc (using NetworkManager and with the terminal) a few
>> months ago. It was working pretty well. Recently, I was forced to
>> change my directory password. After updating my VPN connection details
>> I've been trying to connect without any success. I also tried using my
>> old directory password to no avail. I'm using vpnc-0.5.3 in Debian
>> Lenny
>> 
>> Example of what (now) happens all the time:
>> 
>> # vpnc umd-wireless
>> vpnc: no response from target
>> 
>> Contents of my umd-wireless.conf located under /etc/vpnc/
>> 
>> # UMD-Wireless
>> IPSec gateway 128.8.7.227
>> IPSec ID UMD-TunnelAll
>[...]
>
>When I tried the VPN just now, I ran into the same problem.  Apparently
>those settings are no longer valid.  I extracted the current pcf files
>from the OIT-provided installer at
>http://www.helpdesk.umd.edu/topics/applications/vpn/4052/ and imported
>them into NetworkManager, and now the VPN works just fine.  I have put a
>zip of the pcf files on glue at:
>
>/afs/glue.umd.edu/home/glue/r/m/rmccutch/pub/vpn/umd-vpn-20091204.zip
>
>-- 
>Matt

Reply via email to