Hmmmm perhaps the wording here could be changed a bit.
From documentation :
"An automation is a sequence of rules, each of which is a collection of one or more match conditions. Match conditions in a rule operate as a logical AND. That is, all conditions in rule should match for the rule to be considered a match. For this reason, a match type can be used only once per rule. For example, multiple match conditions for LLDP system description cannot be added in a single rule. If multiple LLDP system description values, they should be entered as comma-separated values in the match criteria instead. Values provided in the match criteria operate as a logical OR, which means that any one of them being matched will be sufficient for the condition to be considered a match"
In the UI it is called "Match Type" and "Match criteria".
So ... would these two Automations do the same thing ? Or would one of these not work ? (see attached picture).
(Simply trying to apply a port-profile to an MR or CW AP)
Here is a pcap on that, perhaps, automated port described above.
Filtered for the client, while i try to ping it, and the client tries to reach umbrella dns.
All packets are there, but no reply in either direction.
As mentioned the default port config here is access vlan 999 that does not exists.
So since the MAC address i clearly in the switches table, and the AP is online in its proper vlan (and works), the port has been changed. But the switch seems to throw away the packets at the edge for the other vlans on that trunk ?!?!?!
