On Sat, 16 Jul 2011 16:13:58 -0400, News <(E-Mail Removed)> wrote:
>80 feet across, 30 feet up through wood floors and wood lath wall
>construction. No metal in either.
Is it just lath and wall board, or lath and *PLASTER*? Anything with
water inside is difficult to penetrate. I ran wireless in the SCZ
City Veteran's hall, which was all lath and plaster on the inside
walls. It was totally impossible to penetrate even one wall, much
less 3 walls. However, it worked well down the hallways, and would
penetrate the wood doors easily. So, I stuffed the place with access
points and antennas. It works, but not through the walls. However,
if it's just wallboard, you have a chance of making this work.
If it were not for the slant path, I might suggest going through the
outside of the building. I've run CAT5 out windows and back in again
in desperation. Wi-Fi will also exit through one window, bounce off
the neighborhing building, and re-enter through another window.
However, with a slant path, forget it.
>Less than 100 feet slant distance; but right, not "LOS".
Yep. It's not LOS.
>OK, for numbers, I presently get 48Mbps association between the Thinkpad
>laptop 3x2 antenna and the Actiontec. Pretty reasonable, actually.
Impressive. Is that while moving traffic, or just at idle? 802.11
tends to slow down as the errors increase, and then speed up when the
traffic stops. Measure your thruput with Jperf (or Iperf) and see
what the wireless link can really do.
<http://openmaniak.com/iperf.php>
<http://ssli.ee.washington.edu/courses/ee299/labs/How_to_Jperf.pdf>
You'll need a 2nd machine to act as a server. Use TCP speeds, not
UDP. Bug me if you need setup help.
Another really simple test is ping. Just ping the other end of the
link at the usual 1 second intervals. Run it for at least 5 minutes.
Watch the latency numbers. If the numbers are a constant number of
msec, you win. However, if the numbers increase erratically, vary
radically, or show no response, then you are experiencing packet loss.
The added latency is cause by packet retransmissions, which show up as
additional time needed to send/return a ping packet. It will work
with packet loss and increased latency, but you won't get full
throughput. The usual cause is co-channel interference, but it can
also be caused by reflections and varying signal strength.
Here's my wireless path to the neighbors. It's usually fairly stable,
but I intentionally fired up my iPhone which provided the necessary
interference.
C:\>ping -t 192.168.1.105
Pinging 192.168.1.105 with 32 bytes of data:
Reply from 192.168.1.105: bytes=32 time=3ms TTL=64
Reply from 192.168.1.105: bytes=32 time=3ms TTL=64
Reply from 192.168.1.105: bytes=32 time=15ms TTL=64
Reply from 192.168.1.105: bytes=32 time=113ms TTL=64
Reply from 192.168.1.105: bytes=32 time=182ms TTL=64
Reply from 192.168.1.105: bytes=32 time=45ms TTL=64
Reply from 192.168.1.105: bytes=32 time=3ms TTL=64
Reply from 192.168.1.105: bytes=32 time=3ms TTL=64
Reply from 192.168.1.105: bytes=32 time=88ms TTL=64
>Thinking Engenius EOC-2611P or EAP-3660, both ends @ 600mw.
I suggest you look at Ubiquiti products instead.
<http://www.ubnt.com>
I favor devices with external antennas (i.e. Bullet)
<http://www.ubnt.com/bullet>
but the build in antenna variety also works well. If you expect
interference on 2.4, think about 5.7GHz.
>On further consideration?
If you can get a reliable 48Mbit/sec association, while moving
traffic, without any interference, it's possible to extend your
20Mbits/sec service.
>(Can't do powerline; have tried this and find my 200A panel not friendly.)
There are power line networking bridges (i.e. ferrite transformers)
that will take care of that problem. More common problems are
interference from other HomePlug users and interference from motor and
switcher noise.
--
Jeff Liebermann
(E-Mail Removed)
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558