Implemented mDNS Service
Hello I was wondering in Omada where I can find the mDNS service ?
I have a TL-R605 router but some IoT devices (especially the once that use Apple HomeKit) do not work or better are unreachable when I put them in a different subnet using VLANs, this is very annoying.
Looking on internet everyone many tutorial (all made on Ubiquiti or sometimes other routers) explain that mDNS repeater is needed, but can't find it in Omada anywhere.
Or eventually is there a workaround or non explicit way to have this done ?
Thanks
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi All,
mDNS service 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 firmware adapted to Omada SDN Controller v5.6).
So far, mDNS service has been supported on ER8411 V1 1.0.2, ER7206 V1 1.2.3, and ER605 V2 2.1.1 as they are fully adapted to Controller v5.6. The current official firmware ER605 V1 1.2.1 is only applied to Controller v5.3, please wait for the next official firmware for mDNS feature.
BTW, TP-Link has released the ER605 V1 1.2.3 Beta firmware, which has added mDNS feature for trial. Welcome to install it and give us further feedback in the forums.
Here is a configuration guide for mDNS service for your reference.
- Copy Link
- Report Inappropriate Content
@Fae it might be implemented but is not working since you cant select service and client vlans for gateway mDNS....
- Copy Link
- Report Inappropriate Content
@R.n. I'll echo this. Unless you choose All - All - All for the three options of a gateway repeater it just doesn't work.
I want to select specific services between specific VLANs as it claims I should be able to do and yet I get no repeating at all if I do. Even if I do this I seem to have some missing services (despite me manually defining them as Bonjour services).
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Is the TL-R605 v1.0 equivalent to the ER605 V1 with respect to mDNS inclusion at the next update.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I have the ER605 v1.0 with firmware 1.2.3 Build 20230413 Rel.55948 and the OC200 with firmware 1.24.0 Build 20230328 Rel.52384 (controller v5.9.32).
I have an IoT vLAN that has my Google Home and Chromecast devices on it, as well as a "LAN" vLAN that has my mobile phone devices and Home Assistant on it. What is the proper way to configure mDNS to allow 1) casting media from my phone to the Google Homes and Chromecasts and 2) broadcasting messages from Home Assistant to the Google Homes? Here is what I've done so far:
- Created a new Bonjour service at Site Settings > Profiles > Bonjour Service with Service Name "Google Cast" and Service ID "_googlecast._tcp.local".
- Created a new mDNS rule at Site Settings > Services > mDNS with the name, "Gateway" as the Device Type, the new "Google Cast" Bonjour service (as well as "AirPlay"), the IoT vLAN as the Services Network, and the LAN vLAN as the Client Network.
However, I'm still not able to cast from my phone or Home Assistant to the Google Home. What am I missing?
- Copy Link
- Report Inappropriate Content
Well, I don't know how to write it so as not to pi$$ you off.
People reported in ER7206 that this will not work. Only Any to Any...
Looks like always - TP-Link $crewed it up.
- Copy Link
- Report Inappropriate Content
@lacrimal It's sometimes hard to follow, but I thought it wasn't working if you didn't have the newer controller firmware (5.8+, I think). Has no one gotten it working with the newest controller and router beta firmwares?
Also, when you say All to All, how exactly do I set that up? I might do that for a little while and hope for a fix soon (haha, I know).
- Copy Link
- Report Inappropriate Content
Information
Helpful: 42
Views: 79158
Replies: 255