EAP235-Wall v1 - The ETH VLAN Doesn't Work Properly After Reboot [Case Closed]

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

EAP235-Wall v1 - The ETH VLAN Doesn't Work Properly After Reboot [Case Closed]

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
EAP235-Wall v1 - The ETH VLAN Doesn't Work Properly After Reboot [Case Closed]
EAP235-Wall v1 - The ETH VLAN Doesn't Work Properly After Reboot [Case Closed]
2022-01-25 09:50:20 - last edited 2023-08-18 03:00:04

Updated as of Aug 18th 2023:

 

The official firmware has been released to fix the issue mentioned in this post.

Please follow the direct download link below or visit TP-Link regional official website for upgrade.

 

EAP235-Wall(EU&US)_V1_3.1.1 Build 20230414   Release Note >

EAP235-Wall(CA)_V1_3.1.1 Build 20230510   Release Note >

EAP235-Wall(JP)_V1_3.1.1 Build 20230510   Release Note >

Note:

The release note didn't mention the fix of the ETH VLAN issue, but the above firmware has included the fix.

 

 

As the official firmware has been released to fix the issue, this thread will be locked to stop updating.

Any further issues or concerns, please feel free to Start a New Thread from HERE.

To get better assistance, you may check Tips For Efficiently Reporting an Issue In The Community.

 

This Article Applies to

 

EAP235-Wall (EU&US)_V1_3.1.0_Build 20210721 and earlier firmware

 

Background

 

Omada Wall Plate AP such as EAP235-Wall supports configuring Access VLAN for the Downlink ETH ports. With the ETH VLAN configured, the client connected to the ETH port should talk to and obtain the IP address from the assigned VLAN only.

 

 

However, we recently received feedback on the EAP235-Wall that the ETH VLAN config doesn't work properly after a reboot, the client connected to the ETH port will obtain the IP address from the default VLAN1 instead. And the correct VLAN will be assigned after reconnecting the network cable from the client.

 

Related post: EAP 235 Wall - Incorrect VLAN Assignment on LAN port after reboot

 

After investigation, it's found that the ETH VLAN doesn't take effect until the EAP235-Wall is booted completely, and manually reconnecting the cable from the client can renew the IP address to make it work as expected.

 

Available Solutions

 

The issue has been located, and it will be fixed in the subsequent firmware upgrade.

If you are looking for a quick solution, you may install the Beta firmware below to fix the issue.

 

EAP235-Wall (EU&US)_v1_3.0.0_20220111 (Beta)

Note: Please be sure you have read the Beta Test Agreement before proceeding!

 

Updated as of Aug 18th 2023:

 

The official firmware has been released to fix the issue mentioned in this post.

Please follow the direct download link below or visit TP-Link regional official website for upgrade.

 

EAP235-Wall(EU&US)_V1_3.1.1 Build 20230414   Release Note >

EAP235-Wall(CA)_V1_3.1.1 Build 20230510   Release Note >

EAP235-Wall(JP)_V1_3.1.1 Build 20230510   Release Note >

Note:

The release note didn't mention the fix of the ETH VLAN issue, but the above firmware has included the fix.

 

Recommended Threads

 

Current Available Solutions to Omada EAP Related Issues [Constantly Updated]

Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!

Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates

 

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  5      
  5      
#1
Options