Hi, Could you let us know if you succeed? I heavily relied on UMD-Wireless on open wifi spots...
Thanks :) Mehmet. On Fri, Dec 4, 2009 at 9:33 PM, Andres Cimmarusti <[email protected]> wrote: > Success!, Thanks a lot! > > I was trying to get it running using CLI, but whenever I checked the netstat > -r command, I would get wlan0 as my default tunnel!. But after unchecking the > option in NM, netstat shows tun0 as default so it works! > > >From the man page of vpnc: > > "The vpnc daemon by itself does not set any routes, but it calls > vpnc-script to do this job. vpnc-script displays a connect banner. If the > concentrator supplies a network list for split-tunneling these net‐works are > added to the routing table. Otherwise the default-route will be modified to > point to the tunnel." > > It seems the new UMD VPN concentrator is supplying this list, which I saw as > output using netstat. I'm trying to figure out how to override it like Matt > pointed out using NM, but using just the command-line....If only I wasn't so > incompetent in shell scripting.. > > Andres Cimmarusti > > http://terpconnect.umd.edu/~candres/ > > > ---- Original message ---- >>Date: Fri, 04 Dec 2009 21:10:55 -0500 >>From: Richard Matthew McCutchen <[email protected]> >>Subject: Re: [UM-LINUX] vpnc fails to connect to UMD >>To: Andres Cimmarusti <[email protected]> >>Cc: [email protected] >> >>On Fri, 2009-12-04 at 20:03 -0500, Andres Cimmarusti wrote: >>> Yes I know that...I'm using the wireless one. It still "splits" the >>> connections... >> >>Me too. But I opened UMD-Wireless in the NetworkManager connection >>editor, went to "IPv4 Settings" -> "Routes", and unchecked "Use this >>connection only for resources on its network", and now everything goes >>through the VPN. >> >>-- >>Matt >> > -- There is a crack in everything, that's how the light gets in. Leonard Cohen
