I'm not a terse guy, so I'll do my best to explain my situation to folks. I should note I'm a senior UNIX SA + mid-level NA, so I'm extensively familiar with IP, but 802.11/wifi stuff (and antennas, etc.) is something I have very little experience with. But you can talk tech to me, don't worry. Please read what I've written in full. Don't skim because I'm trying to cover all my bases here and give folks the necessary info they need to help me in my quest. I'll get to what I need / my situation after I explain my current setup. My current setup: I have a small network setup (very bare-bones/simple/KISS) in my flat. It consists of a Motorola SB6121 cable modem (Internet/Comcast) which hooks up to the WAN port of my Asus RT-N16 (running TomatoUSB + Toastman tomato-K26USB-1.28.7497.1MIPSR2-Toastman-RT-VPN.trx). I predominantly use the Ethernet (LAN) ports on my RT-N16 for my workstations (FreeBSD box and Windows XP box). Everything works flawlessly, with great gigE throughput. Wifi-wise, my RT-N16 set to support B/G Mixed and I use WEP128 encryption. The encryption cannot be changed because my Nintendo DSi hand-held device, which I use regularly/daily, does not support WPA or better. My current wifi devices are a Nintendo DSi (which only supports WEP/WEP128 -- WPA is not supported), and my Canon PIXMA MX860 printer. My DSi gets an excellent signal all throughout my flat (according to its own little bar/metre thing, usually 5 metres, sometimes 4). My Canon printer is about 30 feet away and claims a signal strength of 81% and link quality of 86%. I also have friends who do come over with laptops/handhelds that use wifi, so 802.11g is needed for them. I have my output power in TomatoUSB set to 80mW. I'm using channel 1 (2.412GHz), and my channel width is 20MHz (not changeable). I'm using the stock RT-N16 antennas. A noise floor analysis in TomatoUSB returns -84dBm (not sure if this is good or bad). Within TomatoUSB's "Device List", when my Canon printer is idling, it tends to report -48dBm for RSSI, and a quality rating of 36 (3 bars). Yes I know how this is calculated; noisefloor - RSSI = pos(quality rating), i.e. -84 - -48 = 36. And yes, I have read the Tomato page about RSSI and how its a pain in the ass given all the different NICs/vendors driver/methodologies. I get it. PITA. I understand. I have not done speed/network diagnostics other than what you see above. The most I've done is a "Scan" from Basic->Network, on channels 1, 6, 9, and 11. I'm in an area (SF Bay Area) where everyone and their dog has an AP, so pretty much every channel has craploads of APs seen. I do not own a laptop with a wifi card in it, so I can't run inSSIDer to get some analysis results. I do, however, have a laptop through my workplace (Microsoft) which I could borrow for a day to take home, assuming its wifi chipset is usable in inSSIDer. Please let me know if this would help, and what I should be doing inside of the tool (I've never used it), and if I should take readings from both inside my flat as well as garage (keep reading). Okay, so I think that sums up my current settings and situation there. Now on to what I'm trying to accomplish: I need access to my LAN from my garage. (My flat is on the 2nd floor, garage is on the bottom floor, but not directly below me). The distance between the two is about 120-130 feet, and there are a good 6-7 walls, plus (probably) water piping and other things like that mixed in. It's an old building (built in the late 40s). I cannot use things like native Wifi cards in my machines in the garage; Ethernet is the only choice (please don't argue with me on this. It has to do with OS drivers and so on; welcome to the world of FreeBSD! This is not negotiable for reasons I refuse to get into, thanks!) As such, my choices are using an Ethernet-to-wifi bridge or a router in Wifi Bridge mode. I chose to try the former. The first device I tried was an IOGear GWU627, hooked up to a single 1U rackmount server. This device more or less worked, except randomly during heavy network I/O, I would see the actual Ethernet (LAN) port go down, then come back up between 15-60 seconds later. The GWU627 was not rebooting (its admin page did not show packet counters resetting to 0), instead it would just drop its Ethernet link then come back up. Based on my own conclusions/analysis, the GWU627 appears to be a re-branded Trendnet device (a single-NIC version of Trendnet's TEW-640MB). These devices, when they lose wifi connection, reset the LAN/NIC as well. So to me this meant the signal level sucked. I tried increasing the RT-N16 output power all the way to 200mW but it made no difference. With the GWU627, under Device List, I would see the quality usually around 1-2 bars at most. I do not remember what the RSSI was -- sorry. So I returned this device (given the Ethernet part of it going up/down -- totally unacceptable) and next tried to a Trendnet TEW-640MB, which had the benefit of offering 4 LAN ports. This device was the worst of the bunch. The first thing I encountered, even with the latest firmware and the device set to always have a static IP (192.168.1.120), was that the device would randomly steal IP addresses from devices it saw on the local network. At one point it stole the IP address of my FreeBSD box (I confirmed this on all devices on my LAN by looking at ARP), and another time it stole the IP address of my Canon printer. This device went straight back to Amazon; such behaviour indicates a very, very badly written layer 2 and layer 3 stack. One other thing: the latest firmware for this device offered the ability to turn off LAN-port-reset when wifi went down. When disabled that annoyance, the device completely and entirely stopped working. Only a hard factory reset would make it usable again. It would lock up during boot-up. Wonderful consumer-grade quality. The next device I tried was a Cisco/Linksys WES610N, with the latest firmware. This device behaved very similar to that of the Trendnet device, although it tended to focus on stealing the IP address of my Canon printer. Whenever this would happen (and it would happen about 80% of the time, no joke), the WES610N would lock up. Visual inspection when this happened would show the device sitting idle except for one LED which was blinking at an *insane* rate: the wifi traffic LED. A power-cycle was required to get the unit working again, until it would behave the same way (after 10-15 minutes), lather rinse repeat. This unit also went back to Amazon. Like the Trendnet: high-quality consumer products. After all the above I said "fuck it" and invested in a 2nd Asus RT-N16. Well, what I ended up getting was an Asus RT-N16 Hardware Revision A1, which I did not feel comfortable keeping because it appears to have link speed negotiation problems with older revision SB6120 cable modems. (I wanted to use the Rev A1 in my flat and the older non-rev-A1 in my garage) You can read about my experience at the previous link. Because of this, I never got around to trying the unit from the garage. The next thing I bought (thinking maybe I could use my existing Asus RT-N16 in the garage, and use this new unit in my flat) was a Netgear WNR3500L. When it arrived, it was the WNR3500Lv2, which at the time only Shibby firmware supported (which I don't run; I run Toastman's firmware for a lot of reasons). In the past few days Toastman has gotten his firmware working with the WNR3500Lv2, but I haven't even unboxed the product yet. Toastman also pointed out that the WNR3500Lv2 appears to have an antenna/set that is about 2dB worse than the RT-N16, so that concerns me given what I want to do. So like I said, it's still in its box because if I need to return it to Amazon I'd rather it never be opened. Part of me is wondering if I'm just "flailing around" trying products/wasting time, or what I should be doing. Should I be considering alternate antennas for, say, an Asus RT-N16 in the garage? Should I be using directional antennas? Omni? What kind of connectors? Etc... As I said I'm not familiar with this type of hardware, so I'm hoping some other folks here can chime in and give me some good advice given what I'm trying to do. Honestly I'd just run Ethernet if I could, but I can't -- the garage as I said is not directly below my flat, it's below and over one unit, so diagonally distant from my flat/where my current router is, and my landlord will not let me drill holes or run cabling (I asked him and he looked at me like I must be joking/fucking with him. Seriously). So wifi it is. If folks could read this and let me know what a good first choice of action would be, that'd be awesome. If I need to use inSSIDer first to figure out what's a good "base environment" to start with, then move on to purchasing products (please provide links to hardware/etc. such as antennas, etc. that I can buy online), then that'd be awesome. This is a new, fun challenge that I need some insights into. Thanks folks!