WA-3001 and pfsense

WA-3001 and pfsense

WA-3001 and pfsense
WA-3001 and pfsense
2025-07-19 03:58:49
Tags: #Multi-SSID Mode #WA-3001
Model: TL-WA1201   TL-SG108  
Hardware Version: V12
Firmware Version:

The following thread describes my issue almost exactly.

 

https://community.tp-link.com/us/home/forum/topic/663412

 

I have a pfsense router that is also acting as a DHCP server. That router is connected to a SG108E smart switch on port 1, VLAN 1, 20, 30. On port 2 of that switch connects to a WA-3001 (AX3000) with VLAN 1 (main SSID), VLAN 20 (IOT), VLAN30 (Guest). On port 3 of that switch connects to another SG108E with VLAN1 and 20. The 2nd SG108E is for security cameras.

The WA-3001 and both smart switches connect to the DHCP server and successfully gets their IP assignments. Any device connected to any wireless connection on the WA-3001 fails to get an IP assignment.

In the DHCP logs on the pfsense server it shows that those devices send a DHCPDISCOVERY, the dhcp server responds with a DHCPOFFER but the device never sends a DHCPREQUEST which means that they fail to get an IP assignment.

 

You can't just use the DHCP server on the WA-3001 because it only uses a single subnet, which is stupid for a device that supports 4 SSID's with VLAN's. 

 

The WA-3001 comes with basically no documentation.

 

I'm begining to wonder if the fact that TP-Link doesn't even allow you to chose this AP (which is why I had to chose the TL-1201) is an indication that even they do not like this product.

 

Does anyone know why I'm having this issue, and how to fix it?

 

PS. It is really annoying how some TP-link products require a password with only letters, and others require that you use a special character.

  0      
  0      
#1
Options
2 Reply
Re:WA-3001 and pfsense
2025-07-20 07:43:11

  @Slackware1995 

 

I switched the WA-3001 to Access Point mode. 1 SSID on the 2.4G band, the switch has VLAN20 untagged to the WA-3001.

 

Magically everything works.

 

Next I'll try multi-SSID one more time.

  0  
  0  
#2
Options
Re:WA-3001 and pfsense
2025-07-20 08:12:32

  @Slackware1995 Switched to multi-SSID mode. I tried many things.

 

 

1. VLAN20 on SSID1 2.4G with no other SSID's

a) tagged port

b) untagged port

2. VLAN1 on SSID1 2.4G with no other SSID's

a) tagged port

b) untagged port

3. VLAN20 on SSID3 2.4G with no other SSID's

a) tagged port

b) untagged port

4. VLAN1 on SSID1 2.4G and VLAN20 on SSID3 2.4G with no other SSID's

a) VLAN1 tagged, VLAN20 tagged

b) VLAN1 tagged, VLAN20 untagged

c) VLAN1 untagged, VLAN20 tagged

d) VLAN1 untagged, VLAN20 untagged

 

Not a single DHCP request from a wireless client would connect to the DHCP server and get an IP assignment.

 

Revert back to Access Point mode with SSID1 2.4G configured, VLAN1 untagged, VLAN20 untagged, VLAN20 set as default VID. Magically clients connect and start working.

Conclusion, the WA-3001's multi-SSID function is broken. The main selling point of this WIFI 6 AP is the Multi-SSID functionality, which also includes a login portal for guest clients. This is something should be a killer AP for a small business and home office. If it worked, that is. TP-Link doesn't show that they care about the product by the fact that they didn't even make a real user manual and they aren't updating the firmware.

At this point it's easier for me to simply return the product and use 2 WIFI "routers". I can use a spare WIFI6 router for my guest clients and an older WIFI5 router for the IOT network as the IOT devices all run on 2.4G. It would have been nicer and simpler to have the Multi-SSID AP instead of using 2 WIFI routers in AP mode.

  0  
  0  
#3
Options