Reviving and updating an old feature request for filtered remote packet capture

General
1

At a remote site with limited uplink bandwidth, users are having issues with DHCP. I can use remote packet capture on the support page, limited to that VLAN, but that means sending a capture of the entirety of that VLAN’s traffic which I would then limit the scope of in Wireshark on my side, for analysis.

It would be nice if the capture could be filtered at the Peplink to reduce the amount of additional throughput on the WAN.

Example filters:
capture traffic on specific tcp/udp source-port(s) and/or destination-port(s)
capture traffic with specific source-address(es) and/or destination-address(es)

The existing “Connection” dropdown could be upgraded in this way as well, like:
capture ingress and/or egress traffic on one or more of <existing options in that “Connection” dropdown>

The best version of this would allow us to implement multiple filters

*note: Sorry for the multiple edits. I have updated this post as I continued to think of how this feature could be refined for best functionality with lowest WAN throughput impact. I promise this will be the last edit.

1 Like
2

two votes for this, I often need to do remote packet capture on my wifi network; the remote capture is a nice feature in the peplink however it has zero filtering at the source as @bryan points out, making the feature far less useful. Should be simple to add at least a vlan filter, this would additionally reduce the cpu and tcp load on the router during a capture I’d image.

shaun

1 Like
3

@Eddy_Yeung What do you think can we get this added?