WRT54GS will not connect wireless to WAP54G in repeater mode.
Posted on 2007-03-19
Ok, after spending the past weekend troubleshooting I've decided to come to you fellows to see if we can get it work.
Situation: Linksys AP WAP54G v2.0 (fw. 3.04) unable to connect wireless to Linksys RT WRT54GS v5.1 (fw. 1.52.0).
Setup: Printer === WAP54G ))) ((( WRT54GS === ADSL Modem
192.168.10.150 192.168.10.2 192.168.10.1 192.168.1.1
Wireless clients 192.168.10.100-192.168.10.110
Wireless clients, AP and RT are configured correctly, that is the same SSID, same channel (11), AP in repeater mode with RT wireless MAC address filled in, WPA2-AES security setup on all players.
AP and RT are in different locations and cannot be wired together. although that setup would work. PRT is connected to AP solely to make it wireless and be accesible to clients wireles connected to either the AP or the RT.
Clients can connect to AP, but then only the PRT is accessible or they connect to the RT and can communicate to the outside world, but cannot print!
The Intel Proset Wireless client shows the SSIDwith both the AP and RT MAC address.
Note: This setup has worked flawlessly until last Friday!
What's changed? That would also be first question I would ask if someone explained the problem to me. Well, wireless security on the RT has changed to WEP. This resulted in the split-up of the network. However changing them back to the original values did recover the dual access point network, however the AP and the RT don't ARP correctly. Network monitoring showd that after a reboot of the AP it does a ARP for 192.168.10.1 (RT), but it does not get a reply. When the RT is rebooted I don't see an ARP request ffor 192.168.10.2 (AP). So, it seems the routing table in the RT is either messed up, corrupted or otherwise not as it used to be.
All trivial and obvious options have passed, reset both the AP and RT back to factory defaults, reconfigured both when everything was wired together, reloaded the firmware for the AP and upgraded the fw for the RT, but they simply don't want to communicate with each other without physical contact. Even tried to get it work with wireless security disabled. Downgrade RT back to 1.50.8 which was in charge before will be the next step, but I doubt that will help.
Similar setups have been discussed in the knowledge base, but neither has given the ultimate solution. Alternate OS firmware on the RT is not an option, since it is a v5.0
Hope someone in here will have a bright light or I will have to replae the RT.