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
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
+ Same here
- Copy Link
- Report Inappropriate Content
anyone ? It's very frustrating to have no chance to access all the bonjour devices (Apple/HomeKit compatible devices/Air Print printers/some Smart TV and others) a part from putting them in the same subnet having potential issues of security.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@WilcoV with your setup are you able to let airprint or bonjour in general able to see devices in different subnets?
- Copy Link
- Report Inappropriate Content
@Xstreem will work for the devices which supports bonjour. That's not the case for the most important devices: infra components, like the EAP's, switch and router.
- Copy Link
- Report Inappropriate Content
Any new news?
Is there a solution?
- Copy Link
- Report Inappropriate Content
so no answers from TP-Link on this ?
I just have seen a new update of the router firmware and just crap things. Nothing serious was added or fixed.
Still can't see the VPN connected clients, no mDNS function, useless ACL just versus WAN on not versus LAN.
Those things have been asked several times and time ago and we get nothing just a useless update plus no answers from TP-Link.
So disappointed I chosen this system and spent money here
- Copy Link
- Report Inappropriate Content
@Xstreem Of course all of my new Omada gear is out for delivery today and now I find out it can't even handle mDNS between VLANs... What a disappointment! Did you find any sort of interim solution? If so I'd be very interested in what you've done for now. Hopefully TP-Link fixes this ASAP!
- Copy Link
- Report Inappropriate Content
@atvking no i didn't and no one from tp-link support is helping. The best answer you get maybe is that it will be included in next updates, like many other features requested from me and other users in the past the reality is that I haven't seen nothing if not crap updates. Can't believe the system is new and requires to be constantly upgraded and in reality they stay still. I'm so disappointed!
and just for the router i also have pointed out things on the switches, e.g. Poe schedule is bugged and other things requested to fix/change/add in previous post, but again NOTHING!
Also seems they just copy their competitor staying in any case below them and don't try to make their own system, completely out and blind from the community but the system is intended for professional use....no words
- Copy Link
- Report Inappropriate Content
@Xstreem That sucks! I hope they can get their s*** together and address some of the major issues. I decided to opt for TP-Link/Omada hardware over Ubiquiti/Unifi because of my good experiences with consumer-grade TP-Link products in the past... I'm starting to think that was a mistake :(
- Copy Link
- Report Inappropriate Content
Information
Helpful: 42
Views: 79102
Replies: 255