Has anyone successfully used a source-port or destination-port filter in a packet-capture command on a waas? Anytime I try to filter on any port # I capture no packets. If I however remove the port # and run a packet-capture I capture packets and see the traffic my filter should have caught. I'm not sure if I'm looking at a bug since it seems straightforward.
packet-capture interface gigabitEthernet 0/0 source-port 1494 file-size 50000 capctx
Cisco Wide Area Application Services (universal-k9) Software Release 5.1.1d (build b7 Aug 19 2013)
Is the traffic GRE encapsulated ?
Please be aware of this BUG :
Even though it specifies an APP-Nav environment, I think the GRE issue is still there.
And the issue can still be problematic with tethereal and the "-f" option.
It seams that the bug is solved in 5.3(0.26) ... whatever that is.