At this point, you technically have two choices. In theory, you could buy another WAP and use it near your Xbox, and have one WAP talk to the other WAP. Unfortunately, while most WAPs will do this, they have an interesting limitation: they'll either connect to the outside world and route traffic or connect to another WAP like a bridge. But not both.

The real solution is a Wireless Ethernet Bridge, such as the Linksys WET11. As you can see in Figure B (which I swiped right off Linksys' Web site), the WET11 bridge connects over an Ethernet cable to another device. Linksys is showing it connect to another hub. This means you can run another wired network near your Xbox, perhaps hooking in your TiVo and another PC. Alternatively, you can connect the WET11 directly to your Xbox or other remote PC.

FIGURE B


Linksys provides a good overview of how various network devices work together. Roll over picture for a larger image.

How well does it work?
Overall, the WET11 worked quite well. My WAP is about 35 feet away (on the same floor) from the WET11. I found that virtually all file transfers and other connections were transmitted successfully between my wired network and the Xbox, going through the bridge. The only time I had difficulty (and actually ran a long cable for the evening) was when I was trying to transfer an entire 2.4GB Linux distribution to my Xbox' 200GB hard drive. Yeah, it's hacked. Maybe someday I'll tell you more about that.

There are two negatives that have to be discussed about the WET11. First, it's pretty expensive. Best Buy sells it for $129, and the best price I found on PriceWatch was $103.89 (although there was a similar D-Link device listed on PriceWatch for $80). While there's a lot of tech going on inside this device, it's actually $30 more expensive than a complete Linksys WAP11 Wireless Access Point (and that's got four ports, a switch, and a router built in). We have to take points off our rating of this device because of price.

The second negative is that the documentation is adequate, not great. I had one hurdle to overcome that took me quite a while to figure out. It turns out the device needs its own IP address. It can get that IP address from DHCP (Dynamic Host Configuration Protocol), from the WAP, or you have to set it up ahead of time. The way you accomplish this is first hook the bridge to your PC, use the included utility to talk to the bridge, and pre-assign it an IP. Then unhook the bridge (and hook yourself back onto your home network) and plug the bridge into your Xbox.

Here's the place I got stuck for a while: your Xbox and the bridge need two separate IPs. They are both nodes on the network. While it might have been obvious to some folks, nowhere did the docs say your devices had to have different IPs. Yes, now that I'm writing this, it seems somewhat clear, but it was definitely not when I was hooking it up.

Since I hooked everything up, the network has been running without a glitch. I can recommend this product to anyone who wants to bridge their consumer devices to their wireless network -- as long as you're willing to spend a little too much to do so.

OUR RATING: 3 of 5

David Gewirtz is Chairman and Editor-in-Chief of ZATZ Publishing and is the author of The Flexible Enterprise. He can be reached at david@ZATZ.com. If you want to know more about David and see his artwork, you can visit David Gewirtz Unplugged at http://www.gewirtz.com, his personal Web site and paean to all things David.