Business Community > Wireless > problem with passing vlan traffic
< Wireless

problem with passing vlan traffic

problem with passing vlan traffic

problem with passing vlan traffic
problem with passing vlan traffic
2025-07-29 14:40:29 - last edited 2025-07-31 23:25:22
Model: EAP625-Outdoor HD   EAP215-Bridge KIT  
Hardware Version: V1
Firmware Version:

having a problem with vlan traffic not making it through.  default vlan 1 is working fine 

equipment:

EAP215-Bridge v1.0  1.0.4

EAP625-outdoor v1.0  1.4.3

SG2008P v3.20 v3.20.10

CPE510 v3.20 v2.2.2

I have 4 vlans:   1, 5, 10, 40(guest)

dhcp is done in omada

all devices (not the 510's) are reported in Omada

connecting to an AP gets you a correct address for that vlan.

The AP is connected to 215-brige on the port with the power and the 510 is connected to the next port.

Vlan 1 connects and passes all traffic.

the other SSID connect and get a correct IP address and gateway for their network, but then report no  internet available and they cannot reach anything in their network on the other side of the 510's.

The 510's were defaulted and set up as Access Point and Client.  Their SSID is different than anything else in the network so this is the only possible connection.

Any suggestions on what I have missed?  I do not find any configurationi on the ethernet, only the WiFi with the SSID and assoiated vlan.

 

 

 

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:problem with passing vlan traffic-Solution
2025-07-31 23:25:14 - last edited 2025-07-31 23:25:22

  @Vincent-TP 

I am sorry I did not reply sooner.   I really needed an answer as this is a production network.  I called the Business support and the issue has been identified.  in the EAP215-Bridge they neglected to include the ability to configure the switch ports.  The result is that other  than the first port (which is also power)  the other ports only have the default (vlan 1) network.

I assume someone will get busy and get this code in place.  My hope is that the code is there and tested, but somehow the menus did not get added.  The solution was to install a switch and only used the first port on the bridge until they update code.

Recommended Solution
  0  
  0  
#7
Options
7 Reply
Re:problem with passing vlan traffic
2025-07-30 07:46:22

Hi  @MikeW1 

 

Thanks for posting here.

 

the other SSID connect and get a correct IP address and gateway for their network, but then report no  internet available and they cannot reach anything in their network on the other side of the 510's.

>>>Will the clients get the expected IP addresses? for example, if connecting to the VLAN 5 SSID, will it get an IP address in the VLAN5 IP range? Or an IP in the default VLAN?

 

Please share some screenshots of your controller for better understanding of the situation:

1. The topology/Map page;

2. The device list page;

3. The LAN config page;

4. The WLAN SSID page.

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#2
Options
Re:problem with passing vlan traffic
2025-07-30 12:37:49

  @MikeW1 

on the map the CPE510's are between the two red arrows.  those 2 points were connected at lodge switch port 2.  I do not know when it decided to create a seperate segment. 

 

 

 

 

 

 

DEVICE LIST:

DEVICE NAME,IP ADDRESS,STATUS,MODEL,VERSION,UPTIME,SITE NAME,
"ROUTER-starlink","172.27.0.1","Connected","ER7206 v1.0","1.4.1","5day(s) 14h 52m 27s","PCR"
"Lodge-switch","172.27.0.54","Connected","SG2008P v3.20","3.20.10","5day(s) 14h 32m 16s","PCR"
"Lodge-switch-2","172.27.0.55","Connected","SG2008P v3.20","3.20.10","1day(s) 14h 25m 11s","PCR"
"Pav-switch","172.27.0.53","Connected","TL-SG2008P v1.0","1.0.13","2day(s) 21h 28m 43s","PCR"
"Pondside-switch","172.27.0.56","Connected","TL-SG2008P v1.0","1.0.13","10day(s) 20h 11m 3s","PCR"
"SW-B13","172.27.0.52","Connected","TL-SG2008P v1.0","1.0.13","10day(s) 20h 27m 43s","PCR"
"913a-outside","172.27.0.110","Connected","EAP225-Outdoor(US) v1.0","5.1.11","25day(s) 16m 53s","PCR"
"A5 Test unit","172.27.0.125","Connected(Wireless)","EAP625-Outdoor HD(US) v1.0","1.4.3","4day(s) 19h 42m 35s","PCR"
"B13-AP","172.27.0.102","Connected","EAP225-Outdoor(US) v1.0","5.1.11","13day(s) 22h 49m 14s","PCR"
"BR-P7COW","172.27.0.41","Connected","EAP215-Bridge(US) v1.0","1.0.4","22h 38m 58s","PCR"
"Bath Wifi6","172.27.0.124","Connected","EAP625-Outdoor HD(US) v1.0","1.4.3","3day(s) 23h 45m 47s","PCR"
"Bath to Lodge","172.27.0.24","Connected(Wireless)","EAP215-Bridge(US) v1.0","1.0.6","25day(s) 16m 52s","PCR"
"Behind D7","172.27.0.121","Connected(Wireless)","EAP225-Outdoor(US) v3.0","5.1.11","6day(s) 13h 8m 24s","PCR"
"C3/C4-ap","172.27.0.107","Connected","EAP225-Outdoor(US) v1.0","5.1.11","13day(s) 2m 20s","PCR"
"Camp Store","172.27.0.113","Connected","EAP225-Outdoor(US) v3.0","5.1.11","11day(s) 19m 1s","PCR"
"Cow Barn WIFI-6","172.27.0.122","Connected","EAP625-Outdoor HD(US) v1.0","1.4.3","3day(s) 35m 44s","PCR"
"CowP7","172.27.0.40","Connected(Wireless)","EAP215-Bridge(US) v1.0","1.0.4","11day(s) 14h 25m 52s","PCR"
"Escape to the Trees","172.27.0.104","Connected(Wireless)","EAP225-Outdoor(US) v1.0","5.1.11","6day(s) 13h 5m 44s","PCR"
"Hike-In Sites","172.27.0.115","Connected(Wireless)","EAP225-Outdoor(US) v3.0","5.1.11","1day(s) 23h 20m 43s","PCR"
"LODGE-PAV","172.27.0.43","Connected","EAP215-Bridge(US) v1.0","1.0.6","2day(s) 21h 28m 36s","PCR"
"Lodge","172.27.0.112","Connected","EAP225-Outdoor(US) v1.0","5.1.11","1day(s) 14h 23m 33s","PCR"
"Lodge North","172.27.0.114","Connected","EAP225-Outdoor(US) v3.0","5.1.11","1day(s) 14h 23m 53s","PCR"
"Lodge to Bath","172.27.0.23","Connected","EAP215-Bridge(US) v1.0","1.0.6","6day(s) 20h 11m 33s","PCR"
"P sites North","172.27.0.116","Connected(Wireless)","EAP225-Outdoor(US) v3.0","5.1.11","3day(s) 23h 53m 40s","PCR"
"P7","172.27.0.117","Connected","EAP625-Outdoor HD(US) v1.0","1.4.3","47m 8s","PCR"
"PAV WiFi 6 AP","172.27.0.123","Connected","EAP625-Outdoor HD(US) v1.0","1.4.3","2day(s) 21h 27m 37s","PCR"
"PAV-LODGE","172.27.0.42","Connected(Wireless)","EAP215-Bridge(US) v1.0","1.0.6","4day(s) 19h 53m 48s","PCR"
"Pav to Store","172.27.0.25","Connected","EAP215-Bridge(US) v1.0","1.0.6","4day(s) 21h 22m 4s","PCR"
"Plumtree House","172.27.0.127","Connected(Wireless)","EAP650(US) v1.0","1.1.3","25day(s) 16m 45s","PCR"
"Pond","172.27.0.103","Connected","EAP225-Outdoor(US) v1.0","5.1.11","7day(s) 18h 43m 31s","PCR"
"Pondside 2 Wifi6","172.27.0.129","Connected","EAP625-Outdoor HD(US) v1.0","1.4.3","3day(s) 36m 2s","PCR"
"Spare 3","172.27.0.109","Disconnected","EAP225-Outdoor(US) v1.0","5.1.11",,"PCR"
"Store to Pav","172.27.0.26","Connected(Wireless)","EAP215-Bridge(US) v1.0","1.0.6","10day(s) 19h 22m 14s","PCR"
"Tent-Shelter","172.27.0.105","Connected","EAP225-Outdoor(US) v1.0","5.1.11","12day(s) 23h 58m 55s","PCR"
 

 

 

 

 

 

 

 

 

 

 

 

 

  0  
  0  
#3
Options
Re:problem with passing vlan traffic
2025-07-30 12:41:17

  @MikeW1 

looks like that WLANs did not make it

 

 

  0  
  0  
#4
Options
Re:problem with passing vlan traffic
2025-07-30 12:43:07
and yes, they get IP and gateway for the correct vlan.
  0  
  0  
#5
Options
Re:problem with passing vlan traffic
2025-07-31 03:16:13

Hi  @MikeW1 

 

Thanks for the reply. 

 

Now that the wireless clients could get the correct IP addresses, we need to know on which steps did they be stucked.

To check it, please run some ping tests on the wireless clients separately:

How to use the Ping command

 

1. Ping the connecting EAP's IP address;

2. Ping the connecting switch's IP address;

2. Ping the VLAN interface IP;

3. Ping the router's LAN IP address;

4. Ping the gateway IP address;

5. Ping a public IP address, such as 8.8.8.8;

6. Ping a public webiste, such as google.com.

 

Please let us know the ping results.

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#6
Options
Re:problem with passing vlan traffic-Solution
2025-07-31 23:25:14 - last edited 2025-07-31 23:25:22

  @Vincent-TP 

I am sorry I did not reply sooner.   I really needed an answer as this is a production network.  I called the Business support and the issue has been identified.  in the EAP215-Bridge they neglected to include the ability to configure the switch ports.  The result is that other  than the first port (which is also power)  the other ports only have the default (vlan 1) network.

I assume someone will get busy and get this code in place.  My hope is that the code is there and tested, but somehow the menus did not get added.  The solution was to install a switch and only used the first port on the bridge until they update code.

Recommended Solution
  0  
  0  
#7
Options
Re:problem with passing vlan traffic
2025-08-01 02:03:06

Hi  @MikeW1 

 

Thank you for sharing the solution. It's very helpful.

 

When in a hurry to solve a problem, reaching out to local support can indeed provide faster assistance.

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#8
Options

Information

Helpful: 0

Views: 153

Replies: 7

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.