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
just out of curiosity that has nothing to do with mDNS, did you use VPN on the route you got packet drops on?, IPsec, L2TP or PPTP, I've had a lot of problems with the same but have found out that the packet loss came every time the VPN conneted or disconnected or reconnected a VPN session. tp-link came up with a fix for me after several months. back and forth with support, but it was only for IPsec. L2TP and PPTP are still not fixed.
- Copy Link
- Report Inappropriate Content
@shberge I am not using VPN with Omada, since it did not work. I had to forward a port and then I was able to establish a connection, but after reconnect it did not until I disabled/enabled the forwarded port and then it suddenly worked again. Thus I am using Wireguard on a raspberry pi, which worked/works right away (have I mentioned that I am loving this "professional" product @TP-Link?). The paket drops are from before VPN and after (even when not connected via VPN).
- Copy Link
- Report Inappropriate Content
no i don't use the vpn services on the router itself since it has no supprt for wireguard it just randomly decides to suddenly drop a packet here or there or just completely get quiet fr 30 seconds then suddenly work again i would have thought it was a hw problem but 2 routers on 2 different sites doing the same
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
She (Fae) seems consistent in replies by whole topic and not only this.
V5.6 of controler, October is pointed as probable version and time of implementation.
Considering rollout strategy in TP-Link - they give us about 4 versions of controler yearly - it is pretty sure that before next year we will get it.
I know, I am positivist but seriously - I'm considering this as reliability test for tp-link.
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
You choose to stay with this devices from some particular reason, maybe it was price or it is just working for you in for example 80%.
Know you are frustrated that development of this devices is as slow as 2 years ago. It will not expedite - we have 2 years old proof. Any other function that is not super critically will not be developed faster than 12 months for this small business devices.
I think we both agree that current TP-Link business line with Omaha controler is not something to implement in serious , complicated business environment, right ?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 42
Views: 81320
Replies: 252