On Sat, 2010-08-07 at 08:18 -0500, Matthew Kitchin (public/usenet) wrote: > > [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. No, it's fine -- there's no need to address packets to a specific gateway on a tunnel; you just shove the packets down the tube. It looks like the routes are all set up according to your VPN server's configuration. You aren't routing *everything* to the VPN; only three "Class B" subnets -- 10.85.0.0/16, 10.92.0.0/16 and 172.27.0.0/16. You seem to have DNS set up properly to point to the VPN too. What makes you say it isn't working? What have you tried? If you run 'tcpdump -i tun0 -l -n -s 1500' do you see traffic on the VPN? From your log it looks like you're sending packets but never getting anything back.
