Allllllright chums,

I am updateing this thread in case any one ever has the same difficulties that I had. However, I would first like to humbly thanks sec_ware, for whom without I would be totally lost on this.

Sec_ware's last post about the router being the issue would have been correct, however the router I was using (the D-Link) did not support static routes (a quick call to technical support confirmed this). Afterwards, sec_ware and I exchanged a total of 13 PMs trying to get this to work! And eventually we got it working just great!

Here's the short version of how we got this to work (without all the technical hurdles),

We needed a way for the D-Link router to think that the data from 10.0.0.99 was coming from 192.168.0.102 so it wouldn't get confused with the packet IP. Then we needed a way for 192.168.0.102 to be able to figure out how to forward the packets on to thier original sender on the alternate LAN. Setting up a proxy server did the trick just perfectly...

Read allllll about it! http://www.aboutdebian.com/proxy.htm

After this was done, I was finally able to access the internet via 10.0.0.99 by sucessfully doing a tracert to 194.109.137.218 (www.aboutdebian.com) however, when I tried doing a tracert to www.aboutdebian.com using it's domain name, no dice. This was obviously because something was wrong with the 10.0.0.99's DNS settings.

The solution to this in my case was to build a basic LAN, DNS server on 192.168.0.102. Which may sound difficult, but was probly one of the most easiest things I have ever done reguarding this project.

Read about how to do that here... http://www.aboutdebian.com/dns.htm

After that, 10.0.0.99 had full internet functionality!

And that ladies and gents is how you setup a DHCP/Proxy/DNS server . Once again just want to thank sec_ware for taking the time out of his schedule to help me out doing this. Sec, you da techie !