Hello everyone, I see that this solution was never clear for many so I went ahead and outlined a very simple three steps to getting remote packet captures with ROS done quick.
This post is meant to be a quick practical guide to help you capture traffic quickly for whatever your reasons may be. It can be a huge help with debugging network issues.
Step 1. Configure the packet sniffer tool on ROS to your target machine’s IP address. You can change the port, just remember to set it in step 3.
Step 2. In Wireshark, you should have an option for “UDP Listener remote capture”, click the settings gear to configure the capture options
If you don’t have this option then your problem is beyond this post and you need to reinstall Wireshark with udpdump.
Step 3. Set the port to what you have set in ROS from step 1. If you changed the port from 37008, enter the new port number here.
I’ve set “tzsp” as the payload type so that the output from my capture rules will decode natively and show up as traffic is sent from ROS to Wireshark.
You will see traffic based on the rules of your capture in the ROS packet sniffer tool so remember to check your rules twice before starting the capture.
Finally, you’ve got packets! Now, go forth and make debugging network issues easier.
If you have any issues or think I’ve missed something, please feel free to add to this thread. 
Note: This post is accurate as of ROS 7.1.1, Wireshark Version 3.6.1 (v3.6.1-0-ga0a473c7c1ba) and Npcap 1.60