On 3/2/06, Michael L Torrie <[EMAIL PROTECTED]> wrote: > > Is there a reason you're not willing to run vpnc directly with --udp as > a sanity check? Seems to me you're going about this the hard way. > > The vpnc-connect script messes with routes and things. Better to take > things one step at a time. > > Michael >
I've always been willing to run it - what do I need to do in addition to that, so that everything is configured/setup? I've attached the vpnc-connect script. Running the vanilla 'vpnc --udp /etc/vpnc/work.conf' command asks for my password, and I get the login message just like before. Running 'route' after I'm connected that way gives me: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.7.77.0 * 255.255.255.0 U 0 0 0 eth0 default TMCB-U110-C-CR9 0.0.0.0 UG 0 0 0 eth0 Which is a little different than before (no tun0 device). ip address - before - after 10.7.77.xxx - works - works 128.187.22.200 - works - works www.google.com - works - works Which is also different - but I don't think it's what I want yet, since I don't think I'm going through the tun0 device. Isn't that what's supposed to happen? Isn't vpn supposed to create some kind of 'tunnel' that my eth0 runs through to get out on the other end in the network I'm wanting? I know that the current connection isn't right, since at the MTC you have to configure your browser for the proxy before it works, but my browser still works. I figure that once I'm 'really' connected my browser _should_ fail (until I set it up), but that I'll be able to ping my work machine. Does that sound right? -Rich
vpnc-connect
Description: Binary data
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
