I'm dredging up this old thread to ask a clarifying question: what happens when your laptop is on the same RFC1918 subnet as the private LAN you're attempting to route to?
e.g.: In your example, s2scott, the destination subnet is 192.168.2/24. But ... what happens if where you're connecting from is in the same or an overlapping subnet? e.g.: connecting from 192.168.2.221? or 192.168.50.100 when the netmask is 255.255.0.0?
I ask because I happened to see the IPSec/NAT article just pubbed in the Journal, and thought about address collisions with NAT. Would NAT via the tun(4) device be a possible play?
http://undeadly.org/cgi?action=artic...20090127205841