I have a UAP-AC v1 connected to the POE injector supplied with the device. I'm currently running UniFi 3.2.5 with no customizations. @UBNT-Jerry @UBNT-MikeD , perhaps my description of the problem might lead to an obvious solution?
Problem summary:
The UAP-AC almost always sort-of isolates wifi clients from multicast communications that happen on the LAN the AP is connected to. The AP has been factory reset, and there are no config overrides in the site config.properties file. I have tested with 3.2.5, 3.2.1, 3.1.13, and 2.4.6 and had the same result with each version. I factory reset, readopted, and "upgraded" the AP each time I changed the controller version.
If I connect the wireless clients to a TP-Link wireless router (configured as a bridge) connected to the same switch as the UAP-AC the problem does not occur.
What might I have done wrong, and what can be done to make multicast behave as expected? I've looked through the Knowledge Base and searched the forums a bit, but haven't come up with any promising solution.
A network diagram and detailed problem description follows:
Network diagram:
Wired: [server, mindy] <--> [dumb switch] <---> [dumb switch] <---> [UAP-AC, TP-Link]
Wifi: [campstove, kubuntu]
Server and Mindy are connected with wired ethernet. Campstove and Kubuntu are either connected to the UAP or the TP-Link, but both machines are connected to the same AP and SSID. All machines involved are in the same subnet. Kubuntu is a machine booted from a Kubuntu 14 LiveCD.
Detailed Problem Description:
On each machine, I install socat and run the following command:
socat UDP4-RECVFROM:1901,ip-add-membership=239.255.255.251:$MACHINE_IP,fork EXEC:'bash -c ./blah.sh'
blah.sh is this:
printf "%s %s\\n" `date -Ins` `hostname`
On one of the wired machines, I run the following command:
socat STDIO UDP4-DATAGRAM:239.255.255.251:1901
When I press return, I get messages back from the socat listeners like this:
2014-10-20T17:58:48,061522701-0700 server
2014-10-20T17:58:47,833022211-0700 mindy
2014-10-20T17:58:48,065617032-0700 campstove
2014-10-21T00:58:48,132129630+0000 kubuntu
On one of the WiFi machines connected to the UAP-AC, I run the same socat datagram generator, but I get back these messages when I press return:
2014-10-20T17:55:05,460369763-0700 campstove
2014-10-21T00:55:05,430976969+0000 kubuntu
It's like the WiFi-connected machines are in their own island when they try to talk to the LAN.
When I connect both of the Wifi machines to the TP-Link AP, restart the socat listener, and run the datagram generator on one of the Wifi-connected machines, I get these messages when I press return:
2014-10-20T17:58:48,534873897-0700 server
2014-10-20T17:58:48,305108774-0700 mindy
2014-10-20T17:58:48,539899075-0700 campstove
2014-10-21T00:58:48,615774097+0000 kubuntu
I also get the full set of messages when I walk over to the wired machines' datagram generator and press return.
Now, remember how I said that the UAP-AC almost always isolated the WiFi clients? If I wait for some random period of time, when I run the WiFi datagram generator, I'll get messages from all listeners on the LAN. BUT, when I run the wired datagram generator, I only get messages from the wired machines. If I restart the listeners on the WiFi machines, then the WiFi machines are back in their little island and only the wired machines can see them.
Another interesting note: For a while, I had the listener listen on port 1900; the same port as SSDP. Even though the listeners weren't listening on the SSDP multicast address (239.255.255.250), machines connected to the UAP-AC would reply to multicast SSDP discovery requests with the date and their hostname. Machines on the wired network never replied to SSDP discovery requests.
Any idea what's going wrong? How can I fix this? What more information should I supply?
