Configuring mDNS Repeater

Released On: 2022-12-28 04:53:56Last update time: 2 weeks ago

Overview

 

mDNS (Multicast DNS) Repeater can help forward mDNS request/reply packets between different subnets/VLANs. With this function, you can create a forwarding rule to allow the devices in the specified Client VLAN to discover the mDNS service in the specified Service VLAN. You can also specify the services to be forwarded.

 

 

Configuration

 

Please follow the configuration steps below to configure the mDNS repeater via the Omada SDN Controller v5.6 or later version.  

 

1. Go to Settings > Services > mDNS 

2. Click + Create New Rule to create a new mDNS forwarding rule.

3. Specify the parameters.

 

Name: Specify the rule name for identification.

Status: Enable or disable this rule.

Device Type: Specify the device type (AP or Gateway) for which the rule takes effect.

 

  • Gateway

*mDNS support is added to Gateway since Omada SDN Controller v5.6, which requires both your Omada Router and Omada Controller upgrading to SDN 5.6.

**The Gateway type doesn't support configuring Bonjour Service until Omada SDN Controller v5.8, which requires to upgrade the Router firmware to adapt 5.8. 

 

  • For Omada SDN Controller v5.6 or 5.7:

 

Network: Specify which network that mDNS request/reply packets can cross, that is, the range of services that can be found across networks/VLANs.

 

  • For Omada SDN Controller v5.8 or later version:

 

Bonjour Service: Specify the services to be forwarded. (you can also create new Bonjour service types by click Manage Bonjour Service)

 

Service Network:

Network: Specify the network where the mDNS services are located.

Client Network:

Network: Specify the VLANs where the Client devices are located.

 

  • AP

*mDNS support is added to AP since Omada SDN Controller v5.7, which requires both your Omada EAP and Omada Controller upgrading to SDN 5.7.

 

 

Bonjour Service: Specify the services to be forwarded. (you can also create new Bonjour service types by click Manage Bonjour Service)

 

Service Network:

VLAN: Specify the VLANs where the mDNS services are located. You can enter VLAN ranges or VLAN IDs separated by comma.

Client Network:

VLAN: Specify the VLANs where the Client devices are located. You can enter VLAN ranges or VLAN IDs separated by comma.

 

 

Note: 

1) mDNS rules in AP type and Gateway type are mutually exclusive.

2) To make mDNS configuration take effect, please ensure both the AP/Gateway and Omada Controller are upgraded to the corresponding adapted firmware.

For example, to make the mDNS configuration in AP type work, ensure both your EAP and Omada Controller are upgraded to adapt to Omada SDN Controller v5.7.

 

 

0
Comment

This isn't working correctly for me , as I described in this post: https://community.tp-link.com/en/business/forum/topic/593654https://community.tp-link.com/en/business/forum/topic/593654

 

"I added "    _googlecast._tcp.local" to bonjour services, and then created an mDNS service, with the Chromecast as the VLAN SERVICE NETWORK and my laptop as the VLAN CLIENT NETWORK. But I still could not cast to the chromecast. Please let me know if this is possible? I added "    _googlecast._tcp.local" to bonjour services, and then created an mDNS service, with the Chromecast as the VLAN SERVICE NETWORK and my laptop as the VLAN CLIENT NETWORK. But I still could not cast to the chromecast. Please let me know if this is possible? " 

 

 

It seems that you need to add the bonjour services to get the Chromecast work across VLAN.

 

So far, only the mDNS in AP type has Bonjour Service that can be configured. To make the mDNS configuration in AP type take effect, we need to ensure both the EAP and Omada SDN Controller are upgraded to SDN 5.7 firmware (the firmware adapted to Omada SDN Controller v5.7). While the SDN 5.7 firmware for the EAP hasn't been released yet, you may need to wait for the EAP firmware updates to make it.

 

FYI, the mDNS in Gateway type will add the configuration for Bonjour Service in the subsequent firmware upgrades. Stay tuned!

Best Regards! :) New to TP-Link Community? >>Get Started Here<<.

mDNS randomly only works, I have checked all the settings why am I experiencing this?  and when it does it's a huge lag in response time. The capacity is very low on my setup, what is causing this to not work when I am running the firmware that should support this?  It seems when mDNS does work is only after full power cycles.  Please advise is this a bug in development or do you have to flash the rest of all devices to work.

 

Controller: OC200 1.1 Firmware 1.27.7 Build 20221206 Rel.58608

Gateway: ER605 V.20 Version: 2.1.1 Firmware version: 2.1.1 Build 20230115 Rel.77774

Switch: TL-SG2210P V3.20 Version 3.20.8 Firmware version: : 3.20.8 Build 20221130 Rel.42340

Switch: TL-SG2008 V3.0 Version 3.0.7 Firmware version: 3.0.7 Build 20221130 Rel.42340

AP: EAP235-Wall(US) V1.0 Version 3.1.0 Firmware version: 3.1.0 Build 20210721 Rel. 46004

AP: EAP235-Wall(US) V1.0 Version 3.1.0 Firmware version: 3.1.0 Build 20210721 Rel. 46004

AP: EAP225 (US) V3.0 Version 5.0.9 Firmware version: 5.0.9 Build 20220429 Rel. 43558

upload
    upload