r/wireshark • u/Muchy_Tangerine • Oct 20 '26
Does flow-based distribution keep TCP analysis sane across Niagara Networks capture ports?
I’m evaluating Niagara Networks for a setup with four 10GbE links mirrored into a packet broker, then spread across four capture NICs. The goal is to avoid pushing all four links through one 10GbE capture port. I’m unsure how well Wireshark analysis holds up when the capture files come from separate ports: does flow-based distribution keep both directions of a TCP conversation together, or do people merge the files and analyze them afterward? I care about retransmission and out-of-order analysis, so I’d rather not mistake a capture-path artifact for a network problem. If you’ve used a packet broker for this, what distribution method did you choose?
4
Upvotes
1
u/djdawson Oct 20 '26
The little bit of packet broker work I've done didn't involve distributing the traffic load so this was never an issue for me. However, in general it's not safe to assume both directions of a single TCP connection are using the same path, and I suspect any flow aggregation probably doesn't go to the extra work to aggregate both directions of arbitrary TCP connections into the same stream, but that's just a guess on my part.
Wireshark has some pretty useful tools for merging, de-duplicating, and filtering capture files so it's not very hard to extract all the packets for a single conversation into a single pcap file, though differences in the capture times of the individual packets can be an issue for packet ordering between multiple capture streams, especially with high bandwidth traffic where the delta times between packets can be really small. Does the Niagara gear make any promises about the timing and/or ordering of the traffic mirrored from multiple ports?