10-13-2008 10:42 PM
I already have 2 WAP54G's set up as a wireless bridge.
Now I am about to add 2 more to link to a further building.
Do I
1. set all 4 WAP54G's in bridge mode? or
2. have the 2 middle ones set in repeater mode?
Thanks. Sorry, but I find the documentation ambiguous.
10-14-2008 12:27 AM
JonMac wrote:I already have 2 WAP54G's set up as a wireless bridge.
Now I am about to add 2 more to link to a further building.
Do I
1. set all 4 WAP54G's in bridge mode? or
2. have the 2 middle ones set in repeater mode?
Thanks. Sorry, but I find the documentation ambiguous.
Yo will find that you cannot mix bridge/repeater modes in the same link.
They will all have to be in bridge mode. AP1 will bridge to AP2, AP2 will bridge to AP1 & AP3, AP3 will dridge to AP2 & AP4, AP4 will bridge to AP3
Remember that all APs will have to be on the same channel, and have the same security settings.
Regards
Fred
10-14-2008 11:17 AM
10-15-2008 01:50 PM
Fred. Thanks for the help so far.
I have got the bridge working fine up to to WAP54G #3, but can't get a connection to #4, even if they are 1 foot apart.
I bridged number 4 to #3, same channel, same security.
There is no device on the LAN port for #3 - does that make a difference?
Also, why are there 4 possible entries for MAC's in bridge mode? I have been only entering the 2 you mentioned.
Thanks.
10-15-2008 07:09 PM
I have not tested bridge mode without a LAN connection but it should be possible.
So here a basic generic procedure.
Connect all devices to the power and have them where they are going to be. Give them all unique SSIDs.
Connect the WRT to the Internet as your gateway.
Set the first section of your bridge to point to the first WAP.
Goto the first WAP and set it to AP Client mode and select Site Survey. This will reveal the rue wireless MAC address of the WRT, write down the MAC address found.Repeat this for all the WAPsnoting the true MAC address for each of the devices found. We are doing this because there have been instances where the MAC address on the lable isn't the MAC address of the device.
Now go back to the first WAP and put it in Bridge mode. Enter the 2 MAC address, 1 for the WRT and the one for the second WAP
Now to go the second WAP and put it in bridge mode and enter the MAC address of the first and third WAPs
Nw to go the third WAP and place it in Bridge mode and enter the MAC address of the second WAP.
All WAPs will be in bridge mode.
All devices will be on the same channel.
All devices will have the same security.
I hope this helps.
Regards
Fred
10-16-2008 03:21 AM
Fred - the saga continues. I followed your advice and all MAC's were correct as on the box. Still AP4 not working; message: no or limited connectivity.
I then removed AP3, reset AP4 with the AP3 settings, and installed it in the AP3 position; and then that point no longer worked - that is the "bad" WAP54G was still not working.
The "bad" WAP54G responds correctly when wired into my router. I thought maybe it had a wireless problem so I configured it as a regular AP and I can pick up its SSID no problem.
It seems to me that it is defective. Is there anything else I can try before I send it back?
Jon
10-16-2008 07:50 AM
Try flashing it with the latest firmware even if it already has it.
Regards
Fred
10-18-2008 10:16 PM
Hi Fred,
Updating the firmware made no difference.
I contacted Linksys Support to ask how I return it; you might be interested in the reply:
"Dear Valued Linksys Customer,
Thank you for contacting Linksys Support.Thank you."
Go figure!
10-19-2008 03:44 AM
10-19-2008 10:32 AM
Fred,
I'm not sure it will work. I have not tested the WAP54G in bridge mode.
I use my WAP54G in client and access point mode, to extend the wireless network.
In this case, the WAP54G in client mode does not hold to the WRT54G using the MAC address. It will actually connect t othe WRT54G that is teatherd to it, cuase an endless loop network. Bad, yes very bad.
I'm wondering the the MAC problem could be an isue here too!
Its been over four months and I'm still waiting for Linksys to provide a fix. I've received one beta version to try out, but it failed.