Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 10 of 10
  1. #1

    VLAN on TL-WA701ND seems not working properly

    Model :

    Hardware Version : Not Clear

    Firmware Version :

    ISP : [/COLOR]

    Hi everyone. I'm a newbie here and any help would be greatly appreciated.

    I'm configuring a TL-WA701ND with Multi-SSID (SSID1, SSID2, SSID3 and SSID4 with respective VLANs 1, 2, 3, and 4). This AP is connected to an 802.1Q configured trunk port of a NetGear switch (port 8) whose PVID is set to 1. The NetGear switch's port 8 is tagged on VLANs 1, 2, 3, and 4 as what is advised on the User's Guide. NetGear's port 8 is another trunk with similar config as port 7 and is connected to a firewall that also do 802.1Q. VLAN 1 is 192.168.1.0/24, VLAN 2 is 192.168.2.0/24, VLAN 3 is 192.168.3.0/24 and finally VLAN 4 is 192.168.4.0/24. Each VLAN has its own DHCP service provided by the firewall.

    Here's my problem: If i connect to SSID1 i have no issues. I can get IP address from the correct pool (192.168.1.x/24). Connecting to SSIDs 2 to 4 however cannot acquire an IP address. But if i change the PVID of port 8 to 2 and connect to SSID2 i can get an IP from the correct pool (192.168.2.x/24). Connecting to SSIDs 1, 3, and 4 however cannot acquire IP address. Same is true if i change the PVID to 3 and 4. Note that i can authenticate to all SSIDs but the problem lies on the DHCP negotiation.

    Does anyone experience this problem?

    Here are my other details:
    Firmware Version: 3.17.0 Build 140324 Rel.36563n
    Hardware Version: WA701ND v2 00000000

    Thanks in advance for your help.

  2. #2
    It doesn't make sense. And I don't think there are any problem with the 701ND. So you would better check the configuration of the port 7 and whether your firewall support VLAN? Or you could tell us the configruration of your firewall and the NetGear switch. Then maybe i could find the problem for you.
    Last edited by johnson; 03-23-2016 at 02:48.

  3. #3
    I'm pretty sure the firewall (WatchGuard) and the switch (NetGear) VLAN configuration works. Btw, the switch's port 1 is configured as VLAN1, port 2 = VLAN2, port 3 = VLAN3, and port 4 = VLAN4. Connecting computers via these ports (wired) get the correct DHCP IP Address. Been doing this type of config for years. Done this with other Access Points that does multi-SSID with VLANs and never had this issue. I'm looking at the WA701ND as a more cost effective alternative.

  4. #4
    The problem has been fixed by updating the firmware using a beta version provided by TP Link support. Now waiting for the official release of the firmware version.

  5. #5
    I appear to have the same issue with the TL-WA801ND. Is the firmware now officially released or can a link be provided for the beta download - thanks.

  6. #6
    You could better send email to vipsupport@tp-link.com for help. And you could tell your situation clearly with network topology and configurations, maybe the problem isn't blame to that.

  7. #7

    VLAN on TL WA701ND seems not working pro

    Its hard to visualise what you are saying is wrong. Can you post a screenshot? It might helpColm

  8. #8
    Open a Ticket at ticket.tp-link.com.
    It looks like the Multi SSID feature (especially the tagging) is not working correctly on many TP-Link products.

    For security reasons i would send all untagged traffic on a trunk to a non existing or unused VLAN.

  9. #9

    VLAN on TL WA701ND seems not working pro

    As Andy says, NXJMonitor does not work for i2c sensors link the ultrasonic sensor. It should work for the touch sensor and other analog sensors.

  10. #10
    Junior Member pauldsmyth is on a distinguished road
    Join Date
    Jan 2018
    Posts
    1
    Quote Originally Posted by cza View Post
    Model :

    Hardware Version : Not Clear

    Firmware Version :

    ISP : [/COLOR]

    Hi everyone. I'm a newbie here and any help would be greatly appreciated.

    I'm configuring a TL-WA701ND with Multi-SSID (SSID1, SSID2, SSID3 and SSID4 with respective VLANs 1, 2, 3, and 4). This AP is connected to an 802.1Q configured trunk port of a NetGear switch (port 8) whose PVID is set to 1. The NetGear switch's port 8 is tagged on VLANs 1, 2, 3, and 4 as what is advised on the User's Guide. NetGear's port 8 is another trunk with similar config as port 7 and is connected to a firewall that also do 802.1Q. VLAN 1 is 192.168.1.0/24, VLAN 2 is 192.168.2.0/24, VLAN 3 is 192.168.3.0/24 and finally VLAN 4 is 192.168.4.0/24. Each VLAN has its own DHCP service provided by the firewall.

    Here's my problem: If i connect to SSID1 i have no issues. I can get IP address from the correct pool (192.168.1.x/24). Connecting to SSIDs 2 to 4 however cannot acquire an IP address. But if i change the PVID of port 8 to 2 and connect to SSID2 i can get an IP from the correct pool (192.168.2.x/24). Connecting to SSIDs 1, 3, and 4 however cannot acquire IP address. Same is true if i change the PVID to 3 and 4. Note that i can authenticate to all SSIDs but the problem lies on the DHCP negotiation.

    Does anyone experience this problem?

    Here are my other details:
    Firmware Version: 3.17.0 Build 140324 Rel.36563n
    Hardware Version: WA701ND v2 00000000

    Thanks in advance for your help.
    Sorry to bring back an old thread but I have EXACTLY this problem on a 801ND. I can see from the DHCP server that the correct leases are being offered but the client requests a VLAN1 ip resulting in a DHCPNACK response. Static IP doesn't work either. It's as if the AP is tagging the DHCP request but not the rest of the traffic. I'd be very interested in any firmware that resulted in this being resolved. Support requested my response and don't seem to have paid any attention to my explaining that the rest of the network is working perfectly with the VLANS. I've sent them my topology but anticipate days of back and forth. Currently considering just putting DD-WRT on,


 

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-2018 TP-LINK Technologies Co., Ltd. All rights reserved.