Hello, I'm trying to create a subnet within my network. My main network is 10.10.10.* based, and I want my subnet to be 192.168.1.* based. I want the 192.168.1.* network to be able to get to the router/gateway(10.10.10.1) for the internet, but not be able to see anything else inside the 10.10.10.* network. I am using a linksys wireless broadband router to create the 192.168.1.* network. Can someone point me in the right direction to configure this thing properly so it acts with the specs I want?

Are you adding the linksys router to your existing network? What type of router are you using for the 10.10.10.* network? One thing to remember, SOHO routers aren't as flexible as higher-end routers so this may not be possible...I've never tried it myself. But if I were going to try it, here's what I'd do: - Plug a crossover cable from a LAN port on the existing router (providing you have one of course....I'm assuming here) to the WAN port of your linksys. - Assign an IP to the WAN port on the linksys in the 10.10.10.* subnet with appropriate information (ie: gateway, DNS etc). - Set the rest of the linksys up for the Class C subnet (ie: create your DHCP scope etc and ensure all clients point to the linksys as their gateway with your ISP's DNS address(es)). - Ensure your linksys points to the Class A router as it's gateway, also with your ISP's DNS server address(es). You might have to set up a static route in the linksys to ensure connectivity. Again, I'm not sure this will work. It would be as simple as pie on an enterprise level Cisco router but I'm not at all sure using the WAN port on the linksys in this fashion will work. If it doesn't work, you might want to look at setting up a linux box as a router for your Class C subnet. It would be fairly easy to accomplish this that way as well if you know linux. If you don't, you might try "smoothwall". It's a linux based routing setup that basically runs from a floppy disk and you could use an old junker computer for this. Other than that, you could use a windows box as your router but you'd likely need a server OS in order to provide DHCP and routing.

Connectivity works great, right out of the box; I can get out to the internet and everything. The problem I'm still having is my 192.168.1.* network can reach everything on the 10.10.10.* network. Think I might need more advanced routing solutions?

You'd have to see if the web based setup allows some sort of layer 3. I assume it can to some degree more or less. Here is how I'd do it. Keep your local lan setup as it is. Create a new lan for 192 with a new hub/switch. Connect them across a proxy or nat software on one computer with two nics. There are apps to just proxy the internet such as analogx's proxy. Almost every linux distro has some or all what you need too. Some linux distros are made to run this setup. With the computer as the nat/proxy you can enable it or configure it to a very fine degree and use it's firewalling and antivirus spyware tools across the new lan.