mDns Repeater not working on Controller Version 5.7.4 Linux
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Is there a reason I cannot find the mDNS repeater switch on the latest 5.7.4 of the software controller for Linux?
I deliberately went and spent $200 on an upgrade from the 605 to the ER7206 only to find the functionality I was promised to be available is not.
As you could assume I am less than amused.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Dropbear Ahh, yes the interface was changed between Omada v5.6 and v5.7. Now you can create specific mDNS (mDNS is no longer just Apple BonJour) rules and be very targeted, but it looks like there is a limit of one rule for the gateway and all the others will be at the AP level. I'm not sure why that is, and hopefully TPLink will give more explantion in the future.
For now to just "turn it on", create a new rule that will be for the device "Gateway" select which VLANs it will be active on, name it, and make sure the "Enable" is check . Hit OK, and it should go.
- Copy Link
- Report Inappropriate Content
@Dropbear Assuming you have updated the ER7206 firmware to 1.2.3. It will be under the Settings -> Services -> mDNS tab -> Create New Rule
- Copy Link
- Report Inappropriate Content
Dropbear wrote
Is there a reason I cannot find the mDNS repeater switch on the latest 5.7.4 of the software controller for Linux?
I deliberately went and spent $200 on an upgrade from the 605 to the ER7206 only to find the functionality I was promised to be available is not.
As you could assume I am less than amused.
Dear @Dropbear
This has been forwarded to the developer team for further evaluation.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Dropbear Ahh, yes the interface was changed between Omada v5.6 and v5.7. Now you can create specific mDNS (mDNS is no longer just Apple BonJour) rules and be very targeted, but it looks like there is a limit of one rule for the gateway and all the others will be at the AP level. I'm not sure why that is, and hopefully TPLink will give more explantion in the future.
For now to just "turn it on", create a new rule that will be for the device "Gateway" select which VLANs it will be active on, name it, and make sure the "Enable" is check . Hit OK, and it should go.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Dropbear can confirm that it seems to be working ... can ping machines by name on different vlans ....
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 846
Replies: 6
Voters 1
