I posted this on the Avahi Github issue, but I felt it was appropriate here as well:
--- I've been researching this issue for my company. We specifically need to pass the mDNS portion of the BCT, so our scope is limited, but I do have some insights. There is a definitely an issue if you are broadcasting a service with the "%h" wildcard as the service name. During the service collision portion, this falls down, but, if you are broadcasting under any other static name, you can get much further. Newer versions of the test seem to require that specific services need to be broadcasted. This is not mentioned in the documentation anywhere, but, if I simple broadcast the _smb._tcp. service with any static name (e.g. "Living Room" or "SMB"), then the mDNS test does pass for BCT 1.5.0. Technically we have to pass the mDNS portion of the test on BCT 1.3.1. With the set up above, we fail one test, and that's because one reply comes back from Avahi too quickly. Interestingly enough, BCT 1.3.3 seems to have addressed the timing issue, allowing slightly better tolerances. I believe the response in question needs to come in between the 250ms and 750ms window, and Avahi appears to come in slightly before that window. In the newer versions of BCT, this isn't an issue. I imagine either BCT 1.3.1 has too tight of tolerances, or isn't sampling improperly. There are actually very strict instructions on setting up the test environment, and I even found that with the strict network set up, it could still potentially fail. You need an AirPort Extreme set up to act as an access point and that is it. No DHCP, no network connection, and crucially, no SMB broadcast if you're using a Time Capsule (this can break the test). The test machine was a MacBook Air running macOS 10.12 and connected via ethernet. The Avahi machine was an Asus laptop running Ubuntu 18.10 (Avahi 0.7) connected via wifi. Everything is link local. This all comes from the "Bonjour Conformance Test for Wi-Fi Alliance Version 0.1" document. We're exploring whether we can actually use the 1.5.0 test, as this would make Avahi simply work in the mDNS portion of the test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409872 Title: avahi-0.6.31 doesn't pass Apple conformance test To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/1409872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
