I was able to fix the problem by upgrading to v18 and change Client tracking to "IP Address." The problem was the new Content filtering changed in v17 was not working well with my internal L3 routing.  ... View more

Thx, I tried, it seem's ok! ... View more

It seems the 17.10 firmware update just released and pushed to my appliance fixed this issue.  Wireless clients are now getting policy applied correctly.    ... View more

I think you are on the right track. The truth is on the wire. Wireshark from client or pcap from the appliance. If it is that chatty, you should be able to identify the high volume destinations. You could then also netstat -not to find the owning process. Or use the sysinternals tool TCPview to help you see more on the client side. ... View more