Want to make an isolated subnet

I am wanting to set up an isolated subnet subordinate to my main subnet, but am seeking guidance before I go out and spend a bunch of money on stuff then find out that it won't work.
I want to place some (outdoor, in weather-proof enclosures) wireless network webcam servers onto my existing subnet. The wireless network webcam servers are TrendNet TV-IP301W (link opens in new browser window).
My existing network consists of a combo DSL modem with router and wireless. I rent the modem/router/WAP from my ISP. It does WPA2-AES, and all wireless computers connect to it using WPA2-AES.
The TrendNet webcam servers do NOT support WPA2-AES. The manufacturer has advised me that they have no plans of upgrading the firmware in that device to do so. At $300+ each, they are not something that I want to just throw away or take a big loss on eBay trying to sell.
So, I would like to hang an "isolated" WPA1-TKIP subnet (192.168.1.x) off of my existing (192.168.0.x) DSL modem subnet. My initial cut at a network topology design can be seen here (link opens in new browser window).
One of my main goals for this topology is to continue using the existing routing capabilities of the DSL modem (it can port forward to computers by hostname not IP address and those computers can have DHCP-assigned IP addresses). And, of course, the principal goal is to provide an isolated WPA1-TKIP wireless subnet for the TrendNets, from which rogue users, if they were able to surreptitiously affiliate to that subnet, could neither access any of the Macs affiliated to the 192.168.0.x home subnet nor leech free internet service at my expense.
I am looking at using two LinkSys WAP-54G routers, one in "client" mode so that its WAN side gets a DHCP-issued IPA from my DSL modem/router. The plan would be to strap it back-to-back with another WAP-54G, which would serve as the router for the TrendNets. Problem is, the first WAP54G apparently only works with another WAP54G, not with my ISP's combo modem/router/WAP.
However, it is my understanding that one of the versions of dd-wrt firmware may allow allow the first WAP-54G, when configured in client mode, to connect to a non-Linksys router. At least, this website suggests that this is the case.
The TrendNets are servers, so the only traffic that I want originating from any wirelessly affiliated device on the WPA1-TKIP subnet are "answers" to incoming webserver requests to the TrendNets. Those incoming requests would either be from computers on the 192.168.0.x subnet or from external internet traffic tunneled via ssh to one of the computers ("quicksilver") on the 192.168.0.x subnet. It would be desired to prevent rogue users affiliated to the 192.168.1.x subnet from initiating any connections going external to that 192.168.1.x.
So (finally!) my questions:
(1) has anybody ever flashed a WAP54G with this dd-wrt firmware and connected in client mode, using WPA2-AES, to a non-Linksys product?
(2) there seem to be several versions of the dd-wrt firmware loads out there, and it is not clear to me whatsoever how to select the correct one -- which one should I use?
(3) any problems seen with my proposed network topology?
(3) any hints or suggestions on how to quarantine any rogue traffic (i.e., traffic that is not TrendNet port 80 traffic) as described in the previous paragraph?
Thanks for any help that anyone can provide.

Hi j.v.
Have you tried the Linksys forums? I think you may get more help from a network type forum that uses the WAP54G than the Apple forums.
regards

Similar Messages

Maybe you are looking for