How to Configure mDNS on the Omada Controller
Omada Software Controller( V5 ) , Omada Cloud-Based Controller
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
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(Access Points)
*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 the 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.
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or