Business Community > All Threads > Clients on Second Access Point don't get an IP adress with tagged SSID
< All Threads

Clients on Second Access Point don't get an IP adress with tagged SSID

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Clients on Second Access Point don't get an IP adress with tagged SSID

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Clients on Second Access Point don't get an IP adress with tagged SSID
Clients on Second Access Point don't get an IP adress with tagged SSID
2023-03-27 17:49:42 - last edited 2023-04-10 09:24:25
Tags: #VLAN & Multi-Networks
Model: EAP655-Wall  
Hardware Version: V1
Firmware Version: 1.0.0

Hello,
I need your help: I have two EAP in series, with the second EAP clients do not get an IP address with tagged SSID.

 

I have set up the following SSID:

  • SSID1 (private): untagged
  • SSID2 (guest): untagged, guest
  • SSID3 (work): VLAN 10

 

Hardware setup, see picture:

hardware setup

 

On AP1, the ETH1-ETH3 VLAN are deactivated, i.e. no VLAN is entered.

 

Error description:

Clients do not receive an IP address in SSID3 on AP2 or the connection fails.
SSID1 and SSID2 works fine on AP1. SSID1, SSID2 and SSID3 on AP1 works fine.

 

Does anyone have a tip on what I could change so that SSID3 on AP2 works?

Thank you and best regards

Christian

  0      
 
  0      
 
#1
Options
2 Accepted Solutions
Re:Clients on Second Access Point don't get an IP adress with tagged SSID-Solution
2023-04-10 09:23:58 - last edited 2023-04-10 09:24:25

Hi all,

 

I'd like to update the post with a solution here.

 

TP-Link has released the Beta firmware to fix the ETH Port VLAN issues.
EAP650-Wall | EAP655-Wall - Tagging ETH Port May Stop Other Tagged VLANs From Passing Through

 

You may take your time to upgrade the Beta firmware and confirm the issue you encountered has been resolved.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  2  
  2  
#7
Options
Re:Clients on Second Access Point don't get an IP adress with tagged SSID-Solution
2023-04-12 05:59:52 - last edited 2023-04-12 06:01:12

Hi @d0ugmac1,

 

EAP615-Wall has released the official firmware version EAP615-Wall(EU)_V1_1.1.3 Build 20220921 which has fixed the ETH Port VLAN issue.

As for the EAP235-Wall, please refer to this Solution post to upgrade the Beta firmware.

 

If you have any issues after trying the Beta firmware, please feel free to start a thread from here.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  0  
  0  
#9
Options
8 Reply
Re:Clients on Second Access Point don't get an IP adress with tagged SSID
2023-03-27 18:35:17

  @CS2 

 

There is a long history of bugs with the wall APs and VLAN tags on ports.  For instance, let's say that you are using ETH3 for POE passthrough to the downstream AP.  I'm betting there is an issue with that port having both tagged and untagged traffic on it.

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#2
Options
Re:Clients on Second Access Point don't get an IP adress with tagged SSID
2023-03-27 20:06:13

Yes, it is ETH3.

  0  
  0  
#3
Options
Re:Clients on Second Access Point don't get an IP adress with tagged SSID
2023-03-28 10:03:52

Hello @CS2 ,

 

Could you please send some screenshots to show the VLAN settings on the ETH-ports?

Could you confirm if you set the port VLAN ID on any ETH-ports, especially Eth 3?

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#4
Options
Re:Clients on Second Access Point don't get an IP adress with tagged SSID
2023-03-28 12:20:41 - last edited 2023-03-28 20:11:45

EAP655:

 

TL-SG2008P:

 

If I set a VLANID at ETH3, none of the SSIDs work any more: I then no longer receive an IP address with the clients.

  0  
  0  
#5
Options
Re:Clients on Second Access Point don't get an IP adress with tagged SSID
2023-03-29 02:28:05

Hello @CS2 ,

 

Thank you so much for taking the time to post the issue on TP-Link community!

 

To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID230349901, please check your email box and ensure the support email is well received. Thanks!

Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.

 

Many thanks for your great cooperation and patience!

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#6
Options
Re:Clients on Second Access Point don't get an IP adress with tagged SSID-Solution
2023-04-10 09:23:58 - last edited 2023-04-10 09:24:25

Hi all,

 

I'd like to update the post with a solution here.

 

TP-Link has released the Beta firmware to fix the ETH Port VLAN issues.
EAP650-Wall | EAP655-Wall - Tagging ETH Port May Stop Other Tagged VLANs From Passing Through

 

You may take your time to upgrade the Beta firmware and confirm the issue you encountered has been resolved.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  2  
  2  
#7
Options
Re:Clients on Second Access Point don't get an IP adress with tagged SSID
2023-04-10 15:04:08

@Hank21  Wow!, kudos to you and the development team for the fast turnaround on the firmware fix! 

 

 

 

I am wondering if this fix will propagate to other models as I'm pretty sure the EAP615-wall has the same problem?  I will also mock up CS2's topology with EAP235-walls as well.

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#8
Options
Re:Clients on Second Access Point don't get an IP adress with tagged SSID-Solution
2023-04-12 05:59:52 - last edited 2023-04-12 06:01:12

Hi @d0ugmac1,

 

EAP615-Wall has released the official firmware version EAP615-Wall(EU)_V1_1.1.3 Build 20220921 which has fixed the ETH Port VLAN issue.

As for the EAP235-Wall, please refer to this Solution post to upgrade the Beta firmware.

 

If you have any issues after trying the Beta firmware, please feel free to start a thread from here.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  0  
  0  
#9
Options

Information

Helpful: 0

Views: 684

Replies: 8

Tags

VLAN & Multi-Networks
Related Articles
Clients with preferred access-point
375 0
Clients get this message Unable to get ip address
859 0
Issues with DHCP, clients get same iP addresses
1588 0
Adding second pair of CPE210s to network; clients can't get IP address
562 0
Installing a second EAP110 access point
325 0
Devices can't get IP address from CPE610 as access point
283 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.