3 weeks ago
Measuring with tcpdump on a wired EXOS port in a vlan gives a clean result,
but if one connects over wifi via an AP305c the same vlan via a SSID, there is not only the vlan traffic, but also BUM from other vlans ( arp, multicastDNS, ... )
We suspect that triggers some obscure malfunctioning on some android clients:
A scenario where a rogue 'mdns flush' clears access to the world, while the android ip is still pingable.
Via cloudiq we tried
Friday
gtac case number 03267061
2 weeks open and counting ...
This might be CVE material ...
3 weeks ago
Hello, On wired EXOS ports traffic stays strictly VLAN-isolated so tcpdump looks clean, but on the AP305c the AP acts as a proxy for multicast and broadcast (mDNS, ARP, etc.), which means some BUM traffic can be replicated or bridged in ways that make it appear as if other VLANs are bleeding in. The “multicast conversion-to-unicast always” setting only impacts multicast streams and does not stop broadcast traffic like ARP or certain mDNS behaviors, so you can still see cross-VLAN visibility depending on IGMP snooping, mDNS gateway/Bonjour proxy, or AP forwarding rules.