192.168.1.0/24 is not forwarding through my precise box, or at least i think that's the problem that's eluding me now. my cable modem plugs into eth0 on my precise box, and eth1 provides internet connectivity to my LAN, 192.168.0.0/24. thereby both my precise and my raring boxes can ping the outside world, eg 8.8.8.8. the precise box also has a pppd tunnel, via which it can ping 192.168.1.114. i was expecting my raring box to hit that address through the same tunnel, but no such luck so far, and i don't see why not. any help? precise box: route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 69.180.166.1 0.0.0.0 UG 100 0 0 eth0 69.180.166.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth1 192.0.2.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.1.0 192.168.1.155 255.255.255.0 UG 0 0 0 ppp0 209.173.221.94 69.180.166.1 255.255.255.255 UGH 0 0 0 eth0 raring box: route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.0.6 0.0.0.0 UG 0 0 0 eth0 10.0.3.0 0.0.0.0 255.255.255.0 U 0 0 0 lxcbr0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 raring comes with something called "ufw", to which i said "stop ufw". no change. i do have a homebrew iptables firewall on the precise box. purging it didn't help either. any ideas? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20130612/9d7d3cee/attachment.html>