Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Page 1 of 3 1 2 3 LastLast
Results 1 to 15 of 37
  1. #1

    Thumbs up AP500 Bridging Problem

    Model :

    Hardware Version : Not Clear

    Firmware Version :

    ISP : [/COLOR]

    Hi there,

    i just want to bring attention to a Bug on the AP500 in Multi SSID Mode!
    It bridges packets (DHCP and more) between different VLANS on the wired ethernet side.
    Wired DHCP-Clients may get IPs from other VLANS and will have ip-connectivity issues.
    If you plan to use two AP500 with Multi SSID Mode you will (!) create a l2-loop if you donīt have a proper loop detection mechanism on the switch which disconnects the AP500 automatically.
    I opened a Ticket (208545) on March 26th 2016 and there is still no firmware available to fix this behavior.

    Even after two month it is still not possible for me to use my two AP500 in Multi SSID Mode.

  2. #2
    Fixed only within a beta firmware.
    Still some other bugs left and iīm just wating for a non beta firmware and some other necessary improvements.

  3. #3
    Quote Originally Posted by deniTHOR View Post
    Fixed only within a beta firmware.
    Still some other bugs left and iīm just wating for a non beta firmware and some other necessary improvements.
    Where do you get the beta firmware from?

  4. #4
    I got it from the support after reporting and spending much time explaining the whole problem.
    It took me over two month and many many emails to get a working beta firmware.
    In the whole process i got five different beta versions and only the last one fixed it so far.

    Just open a ticket and ask for the beta firmware provided in case 208545.
    They could not tell me when a final release will be available on the website.
    If you plan to use Multi SSID it will not work properly without a new firmware!

  5. #5
    It seems I have a similar sort of problem. I create a SSID GUEST mapped to VLAN 10. Packets tagged VLAN 10 arriving on the wired interface go out the GUEST SSID as expected. But traffic from the GUEST SSID leave the AP on the wired interface untagged. I wonder if this was similarly observed by others, and @deniTHOR if the beta firmware rectified it?

  6. #6
    It seems I have a similar sort of problem. I create a SSID GUEST mapped to VLAN 10. Packets tagged VLAN 10 arriving on the wired interface go out the GUEST SSID as expected. But traffic from the GUEST SSID leave the AP on the wired interface untagged. I wonder if this was similarly observed by others, and @deniTHOR if the beta firmware rectified it?

  7. #7
    anyone try this beta firmware before? http://static.tp-link.com/resources/...-rel48929_.zip

  8. #8
    Quote Originally Posted by Kevin SG View Post
    anyone try this beta firmware before? http://static.tp-link.com/resources/...-rel48929_.zip
    Any idea what it fixes?

  9. #9
    Network loop may occur when multiple AP500s are connected to the switch if VLAN is enabled on both AP500s and switch

  10. #10
    Quote Originally Posted by lzs View Post
    It seems I have a similar sort of problem. I create a SSID GUEST mapped to VLAN 10. Packets tagged VLAN 10 arriving on the wired interface go out the GUEST SSID as expected. But traffic from the GUEST SSID leave the AP on the wired interface untagged. I wonder if this was similarly observed by others, and @deniTHOR if the beta firmware rectified it?
    Thatīs the version i got provided on my case. MultiSSID is working and you wont get a loop anymore with two APs in multiSSID Mode.
    I did not test more than that. The AP still sends out his own traffic untagged (no ntp, no logging and no management from lan side).
    The AP500 is like a beta version product - You pay money for just to find out later what will not work - And it seems TP-Link does not care much.

  11. #11
    if the beta can't fix the problem, i think it is better to report back to tp-link support so they will take a look at it.

  12. #12
    Quote Originally Posted by deniTHOR View Post
    Thatīs the version i got provided on my case. MultiSSID is working and you wont get a loop anymore with two APs in multiSSID Mode.
    I did not test more than that. The AP still sends out his own traffic untagged (no ntp, no logging and no management from lan side).
    The AP500 is like a beta version product - You pay money for just to find out later what will not work - And it seems TP-Link does not care much.
    Hi, can you tell me exactly what firmware version they provided to you?

    I was given "1.0.0 Build 20161220 Rel. 69936", it does not fix the VLAN tagging problem.

    To recap: Traffic from SSIDs mapped to any VLAN other than 1 leave the AP500's wired interface untagged. Basically, it looks like nothing leaves the AP500's wired interface tagged at all.

  13. #13
    The version from the linked zip-file was the last one i got while working on my case: AP500_un-up-ver1-0-0-P1[20160607-rel48929].bin

    They did fix my reported bugs regarding the loop and missing VLAN tags in multiSSID Mode. It worked for me but is far from perfect since i canīt manage the APs from hosts on the wired side.
    The missing management VLAN and untagged traffic sourced from the AP was not addressed.
    What i learned too was that a newer build might not have all fixes from previous builds...

  14. #14
    hi deniTHOR, try this beta firmware, it says to solve untagged traffic sourced from the AP.
    http://static.tp-link.com/AP500_eu-up-ver1-0-0-P1[20170720-rel38914].rar
    but i don't this this AP support management vlan.

  15. #15
    Quote Originally Posted by deniTHOR View Post
    The version from the linked zip-file was the last one i got while working on my case: AP500_un-up-ver1-0-0-P1[20160607-rel48929].bin

    They did fix my reported bugs regarding the loop and missing VLAN tags in multiSSID Mode. It worked for me but is far from perfect since i canīt manage the APs from hosts on the wired side.
    The missing management VLAN and untagged traffic sourced from the AP was not addressed.
    What i learned too was that a newer build might not have all fixes from previous builds...
    Unfortunately that version somehow could not install in my AP500. Unsupported hardware version. My hardware version is 1.0... didn't know there was any other hardware version at this time?


 

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright Đ 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.