Thanks for the updates, but I no longer have access to access to hardware for testing. It is relatively easy: install the ftp/netdumpd package on a machine with low latency to the test host. Have it write dumps to /tmp:
# cd /tmp # netdumpd -D -d . -P ./netdumpd.pid
On the test host, give the mlxen interface under test an IP address; configure netdump by specifying the local and server IP address, and the next-hop router if needed:
# dumpon -c <local IP> -s <server IP> -g <gateway IP> mlxen<N> # sysctl debug.kdb.panic=1
The -g parameter can be omitted if the two hosts are on the same link. Its value can be "default," which causes it to use the current default router.
I am not worried too much about whether it makes 12 or not, just want to make sure it doesn't get lost. I didn't see any phabricator activity since August 2, which is why I asked. If it's in the queue and will land eventually, I am happy with that. Thanks!