On 8/7/2010 2:25 AM, David Woodhouse wrote: > Yeah, in that case you were definitely connected to the VPN and > keepalives were working, etc. > > It looks like the addresses and routing weren't configured properly. > > Precisely what is /etc/openconnect.script and is it executable? On > CentOS you ought to be able to use --script /etc/vpnc/vpnc-script. > Thank you for the quick responses! /etc/openconnect.script is a straight copy of http://git.infradead.org/users/dwmw2/vpnc-scripts.git/blob_plain/HEAD:/vpnc-script I couldn't see anywhere indicating I was supposed to modify it. It is executable. [root at VM-MKLinux ~]# ll /etc/openconnect.script -rwxr-xr-x 1 root root 18337 Aug 6 22:43 /etc/openconnect.script I did not modify it at all. I don't have /etc/vpnc/vpnc-script on my machine. I assume that is becuase I don't have vpnc installed. > What is the output if 'ifconfig tun0' and 'route -n' while openconnect > is running, and what's in /etc/resolv.conf? [root at VM-MKLinux ~]# ifconfig tun0 tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.70.6.102 P-t-P:10.70.6.102 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) [root at VM-MKLinux ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.85.0.10 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 10.85.0.11 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 216.248.9.102 75.151.54.46 255.255.255.255 UGH 0 0 0 eth0 75.151.54.40 0.0.0.0 255.255.255.248 U 0 0 0 eth0 10.70.6.0 0.0.0.0 255.255.255.0 U 0 0 0 tun0 172.27.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 10.85.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 10.92.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 0.0.0.0 75.151.54.46 0.0.0.0 UG 0 0 0 eth0 [root at VM-MKLinux ~]# cat /etc/resolv.conf #@VPNC_GENERATED@ -- this file is generated by vpnc # and will be overwritten by vpnc # as long as the above mark is intact search unix nameserver 10.85.0.10 nameserver 10.85.0.11 I'm guessing all the 0.0.0.0 in the gateways above is an issue. > Don't send 'webvpn' cookies to the mailing list, btw -- those are *all* > that's required to allow a client to connect using your authenticated > session. > Sorry about that. I blanked out my username and killed my session before I sent that. I assumed the cookie data wouldn't be useful once my session was dead. I won't send it again.
