Business Community > Gateways > mDNS Issues after ER605 update to 2.3.0
< Gateways

mDNS Issues after ER605 update to 2.3.0

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

mDNS Issues after ER605 update to 2.3.0

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
mDNS Issues after ER605 update to 2.3.0
mDNS Issues after ER605 update to 2.3.0
2025-08-19 23:01:12 - last edited 2025-08-20 01:12:52
Tags: #Firmware Update #mDNS
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.3.0

Per title, issues with mDNS broadcasts across VLANs after updating to 2.3.0. Not completely broken as broadcasted services variable make it to other VLANs but not consistent and not all devices all the time. 

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:mDNS Issues after ER605 update to 2.3.0-Solution
2025-08-20 00:53:29 - last edited 2025-08-20 01:12:52

  @nRayAffair 

nRayAffair wrote

  @Clive_A 

 

yes, probably. 
 

avahi was the initial issue that prevented mDNS from working on Omada and at that time a support engineer troubleshot my system and test deployed the eventual fix that was put into the firmware. So presumably they know how to fix it, but need to be aware that it is an issue. 

That's known if you have reported. That post is also aware by the dev team. I am not sure about the development progress or anything regarding the future bug fix.

You can wait for future firmware and its release notes. 

Recommended Solution
  1  
  1  
#4
Options
3 Reply
Re:mDNS Issues after ER605 update to 2.3.0
2025-08-20 00:38:39

  @nRayAffair 

If your described issue is similar to this one?

https://community.tp-link.com/en/business/forum/topic/823830

 

This seems to be a problem with the Avahi. 

  1  
  1  
#2
Options
Re:mDNS Issues after ER605 update to 2.3.0
2025-08-20 00:44:20

  @Clive_A 

 

yes, probably. 
 

avahi was the initial issue that prevented mDNS from working on Omada and at that time a support engineer troubleshot my system and test deployed the eventual fix that was put into the firmware. So presumably they know how to fix it, but need to be aware that it is an issue. 

  0  
  0  
#3
Options
Re:mDNS Issues after ER605 update to 2.3.0-Solution
2025-08-20 00:53:29 - last edited 2025-08-20 01:12:52

  @nRayAffair 

nRayAffair wrote

  @Clive_A 

 

yes, probably. 
 

avahi was the initial issue that prevented mDNS from working on Omada and at that time a support engineer troubleshot my system and test deployed the eventual fix that was put into the firmware. So presumably they know how to fix it, but need to be aware that it is an issue. 

That's known if you have reported. That post is also aware by the dev team. I am not sure about the development progress or anything regarding the future bug fix.

You can wait for future firmware and its release notes. 

Recommended Solution
  1  
  1  
#4
Options

Information

Helpful: 0

Views: 1004

Replies: 3

Tags

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