| | Re: repeater
"Eric" <email@example.com> wrote in message
> <firstname.lastname@example.org> wrote in message
> news:email@example.com oups.com...
>>I have a a remote section of my house that uses wireless. I have
>> a linksys wireless n router. I want to add a repeater between the
>> router and user as the connection is weak. What is my best choice?
> As John pointed out, repeating reduces your bandwidth. In fact, it cuts
> your pipe in half.
> If all you do is pass internet traffic, it probably won't be noticable --
> but if you pass a lot of LAN traffic around, repeating is quite ugly.
> The "best" choice is another, standalone, seperate, wireless access
> point -- running as a standalone, seperate, wireless access point.
> If running CAT5 to where you want the additional WAP isn't practical, what
> you could do (and I'm doing this), is get both a wireless-ethernet bridge
> and a new WAP. The bridge, acting as a client, brings your pipe in from
> the air and into the WAP over ethernet. Config the WAP with the same SSID
> as the WAP that you want to "repeat", but use a different channel. You
> now have a "repeater", but without cutting the pipe in half.
Oh, yeah, bring the bridge online before the second WAP or the bridge may
lock into the second's WAP's and go into a useless loop.
My DLink bridge stays locked with the "originating" WAP, if its brought up
before the second WAP. (As both have same SSID's).
Better bridges probably can be locked onto an SSID by MAC and channel, I'd