pfSense

If I understand this correctly, the following patch should cover it:
https://redmine.pfsense.org/issues/13382

Apply the contents of the .diff file using the System Patches package.

I can't say whether the patch makes any difference or not; I cannot apply it:

Patch does not apply cleanly (detail)
Patch does not revert cleanly (detail)

Debug Result: Fail

/usr/bin/patch --directory='/' -t  --strip '2' -i '/var/patches/62fbe7c0b421e.patch' --check --forward --ignore-whitespace

Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/usr/local/www/diag_packet_capture.php b/src/usr/local/www/diag_packet_capture.php
|index b6d2fecc97508aff4dd8f1f39f073693a23ff607..18a92df24f283e5bcded2f932cb459bd1b5b521c 100755
|--- a/src/usr/local/www/diag_packet_capture.php
|+++ b/src/usr/local/www/diag_packet_capture.php
--------------------------
Patching file usr/local/www/diag_packet_capture.php using Plan A...
Hunk #1 failed at 28.
1 out of 1 hunks failed while patching usr/local/www/diag_packet_capture.php
done

Are there perhaps baseline differences in diag_packet_capture.php between 2.6.0 and 2.7.0?

• Installs cleanly with the System Patches tool
• Provides the option to capture on wan_stf
• Successfully downloads the .cap file with IPV6 traffic

One minor issue: when the maximum number of packets is set to zero, the tcpdump command line still has a limit parameter " -c 0", and no capture occurs. I changed line 1226 to:

$cmd_count = $input_count == 0 ? "" : sprintf(' -c %d', $input_count);

ALso -- and I suspect this is a limitation of tcpdump -- but it would be ideal if the PPPOE and WAN_STF (6RD) connection could be captured simultaneously as WAN. This would mirror the behavior on the firewall rules page.