Connecting Access Point to router via LAN Question

I got a problem I haven't been able to solve after about a week of trying off and on and need a clue.

Situation: I have a WRT54GL router ver 1.1 original firmware. Wireless and wired LAN connections are rock solid. In an effort to extend the wireless range, I acquired a used Cisco Aironet Model AIR-AP1131AG AP. The AP is connected to a WRT54GL LAN port and I can enter AP setup via LAN desktop through IE. After manual reset to defaults on AP, I configured the AP (as best I can tell as the setup has way more options than I need) to match the WRT54GL wireless security settings, DHCP, and as root-AP. Because I am not interested in seamless roaming, I assigned the AP with a different SSID. With my laptop (T61 Atheros), I can see the AP per SSID, T61 tries to connect, but AP (or router, I don't know which) will not assign an IP. I have also tried static IP instead of DHCP but same result. I've tried to use Cisco setup manual but there's something amiss. I even changed router security to WEP from WPA2 because security settings for the AP are way over my head. Radio G channels are different on router and AP as the T61 can see both router and AP, just can't switch to AP. I disabled radio A on AP. I have googled and read and read, but my notes and brain are scrambled.

I apologize for length. Any suggestions welcome. Thanks.

 

I think you would be better off using the roaming feature to extend your range.

Are you setting the AP up in a different location or next to the router?

Use WPA security.

I would use the dd-wrt fimware in the WRT54GL, that's the reason you got the GL. It will give you a better wireless options, besides perform better.

 

I'm not sure what you mean by 'roaming feature'. Is that a router or AP feature?

The AP is connected via Cat5e about 75 ft away from the router at the other end of my home. I'm trying to extend range toward an outbuilding. The Aironet was given to me to try (free). I had WAP2 setup on the WRT54GL, but from what I have been reading, the AP should be setup with same security settings as the router. Is this incorrect thinking? I live in rural America, private property, so snoopers within shotgun range beware.

I thought about dd-wrt, but the router has been rock solid for in-home wired and wireless that I hesitate to monkey with it.

 

Yes, the security needs to be the same. Roaming means they will have the same SSID with the same auth. Which in turn it will jump to AP with the strongest signal. You can use the AP as a AP. Meaning Different SSID and security. In most cases this way the NB has a tendency to keep the original connection. You can change the prority which helps it to dis-associate to the preferred connection.

Since your trying to reach an outside building, install a beam antenna to concentrate the signal and minimize noise.

Here is a like to a company that sells outside beam antennas. With these on each end you can shoot several miles.

http://www.hyperlinktech.com/category.aspx?id=73

 

Thanks Blue. I spent some time today on the phone with a friend that supplied the Aironet. He works at Cisco, has knowledge, but not a setup engineer. We basically reset both the router and AP and rebuilt from ground up, however confirmed the AP is not assigning an IP to the NB. He's going to talk with an engineer about firmware settings. Because the AP was free, I'm going to see if we can get it to play fair. If not, I'll take you advice on beam antenna options.

 

In most cases you set the AP to a static IP. Then you have the main router issue the IP's via DHCP.

 

After reading your reply I decided to give the static IP another try. This time I used extension .155 (DHCP range .100-.149) instead of .50, entered security settings and gave it a try. The AP connected the my NB and router issued the IP just as it should have. I must have had some other configuration within the AP goofed up. The AP has far greater capacity and is way more complicated for my needs, but again, it was free. Thanks again for the nudge.

 

Blue, FYI I'm in the aluminum sided out building and have signal strength around 67%-75% at 54 Mbps, so all looks satisfactory so far. After rethinking my earlier steps (when static IP didn't work), I don't recall disconnecting the AP from the router after changing from DHCP to static and I did so this time. Maybe something didn't reset. At any rate, thanks again for nudging me in the right direction.