> 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?
Kinda. Going back to what I spoke about where after a connection, for all intents and purposes, you disconnect from your network and connect to your work network. If you connected with the --udp option and you have a route table that you have pasted above, it tells me that everything will work because you are now (POSSIBLY) in a case similar to the church's vpn connections. You have both your vpn connection _and_ your previous functionality. Therefore, your browser will go through your previous connection with the route tables you have pasted, and not be blocked by any settings that you have/don't have. In sum (because I ramble), connecting with the tables you have shown will yield a) a browser that works without configuring for a proxy and b) a pingable work machine. If b) fails, you are not REALLY connected. That is the only test you have to verify you are tunneled or not. A browser that's working after you run your connect command is not a reliable test for tunnel. > > -Rich > -- Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer -------------------- 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
