New WAP54GP Capabilities

Discussion in 'Other Linksys Equipment' started by jtoad, Sep 29, 2006.

  1. jtoad

    jtoad Network Guru Member


    This is sort of a crosspost, I first asked this in the Networking section, but if anyone is using one or more of these slick black POE enabled boxes, maybe you can help.

    I am looking to get the best (and possibly worst) of both worlds at one of our sites: I want to provide our staff with wireless WPA access to our local LAN, while also offering free, unencrypted guest access to the internet only. We already offer guest access via dedicated wired jacks that make use of isolated VLAN ports on our Cisco Catalyst 2950 switches.

    I read that the WAP54GP access point is multi-SSID, multi-VLAN capable. Has anyone had experience with this, and will it be compatable with the VLAN implementation on the older Cisco switches? Ideally we would end up with an unencrypted, visible SSID that gets corralled into our internet only VLAN with a hotspot controller, and an encrypted, SSID hidden VLAN connecting to our internal LAN. All with one WAP, one POE enabled CAT5 wire. Sounds great, but will it work?

  2. n2tdk

    n2tdk LI Guru Member

    Just got 1 of the WAP54GP's and 1 WAP54GPE.

    The GPE was DOA, plugged into PoE switch and no response from the unit (no lights or voltage internally).

    As for the GP. Using it with a Cisco Catalyst Express 500 PoE switch (802.1q VLAN's). The VLAN Trunking works (with 1 strange issue that I'm looking into). Set the unit up on a Switch port config'd as a VLAN Trunk. VLAN ID 10 is the native one and the IP of the AP is static set in this subnet. Also have ID 30, 50 and 100.

    Setup the Multiple SSID's with each SSID in a different VLAN. That worked fine. But, before VLAN Trunking was enabled and set in the AP, WLAN clients would be handed an IP from VLAN 10 via DHCP without any issues. Once VLAN Trunking was setup, DHCP IP Address assignment is only working in the other VLAN's/SSID's. Not in the native VLAN 10 which is tied to the Main SSID and the Access Point's VLAN is set to 10 also. 30, 50 and 100 DHCP address assignment works fine. Did not have much time to packet capture this and debug it on the Cisco Router that is doing the DHCP yet. If I Static Set my Clients IP connecting to the Main SSID, ip comm's work fine. So, not a routing issue.

    Just as an FYI, SSID Broadcast ONLY can be enabled or disabled for the Main VLAN/SSID when VLAN Trunking is on. All other (Virtual) SSID's created and matched to VLAN ID's have Broadcasting disabled and can NOT be turned on.

    After the unit was up for a few hours working without issues (other then the DHCP issue above). It started going into a fit. Ip traffic flows fine for a minute, then dead for a few minutes, then up, then down, etc... The unit was not rebooting and no errors were being thrown up in the Switch. So, not sure on this issue yet either.

    Just got these late in the day yesterday and tried troubleshooting the GPE issue for awhile before returning it as DOA.....
  3. jtoad

    jtoad Network Guru Member

    Similar experience on Cisco unit


    I've been away and didn't notice this post until now. Thanks for the info. Have you figured out the weirdnesses yet? I'm evaluating the unit for deployment in my company, so my reputation might be on the line. ;{)>

    I have tried to simulate this concept with an old Cisco BR350 Workgroup Bridge, running VXWorks firmware. I was able to create trunking VLANs linked to the WVLANs, as you did, and I could only broadcast the default SSID of the unit as well. While that will work in theory, since I only want the hotspot SSID visible, it is a limiting factor. During the test, I had no problems with it going down or flaky. However, as this is the bridge version, not the AP350, I'm not sure if I would get better options with the AP version.

    (Does anyone know if a BR350 is physically the same as an AP350? There are recommendations to upgrade away from VXworks to IOS for the AP, but I don't wanna brick the thing...)

    If you (n2tdk) have any update on this unit, please share!

  4. wechan

    wechan LI Guru Member

    I have a similar case: wanna establish a wireless network for a restaurant POS system, while providing unecrypted internet access on a separate VLAN for the customers. I intend to use a WAP54G and a Dell PowerConnect 3424 switch. Let's say, I connect the WAP54G on the Port 1 of the Dell Switch. how should i configure the VLAN on the Dell Switch? do I have to match the VLAN ID on the AP and the switch? sorry that I am quite a newbie on networking stuff. :tongue:
  5. jtoad

    jtoad Network Guru Member

    Hiya from not *quite* a newbie,

    First, we're talking about WAP54GP here, the non P unit doesn't do VLANs, I think. (Tell me if I'm wrong) This unit is from the upscale, 'cisco-ized' line of units, and I was intending to match it with the Linksys POE enabled switch with VLAN support, on the probably good assumtion that they would be compatible.

    That said, I had some success matching AP VLAN to switch VLAN using the aforementioned Cisco BR350 and a Dell PC 2716. Again, my guess is that the 3000 series switches can do all the 2000 series can and more. The issue is trunking, and the different protocols used by different vendors. Here's a link to some interesting, if not totally relevant, info:

    VTP vs GVRP? Maybe you don't have to worry about it in a small environment with one switch. And... if you use a WRT54G or similar router and aftermarket firmware, you can always match wireless VLANs to physical ports, and just run two cables. (Although I'm not sure how stable their implementation of multi-SSID is. For that matter, I don't know how good the Linksys WAP54GP is either. That's the whole point of this thread!)

    Hope this helps is some way.
  6. mrrogers75

    mrrogers75 Guest

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice