https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7381
--- Comment #15 from Guy Harris <guy@xxxxxxxxxxxx> 2012-07-14 15:47:05 PDT ---
(In reply to comment #13)
> How about implementing two strategies:
> 1: Relaxed, where interfaces with the same names are considered to be the same
> interfaces. This would work fine for pcapng files captures on a single machine.
> 2: Mr. Proper, where if an interface name collision is present across the files
> mergecap exits.
> This mode would also allow passing mapping file(s) to mergecap, where the user
> can set up an original name -> output name per capture file and if the
> collisions can be resolved by using the mappings then mergecap would do that
> without exiting.
Or:
1. Relaxed, where interfaces with the same names and matching option values if
present for both interfaces are considered to be the same interfaces;
2. Strict, where all interfaces in all input files are considered to be
distinct even if they have matching names and attributes, with a matching file
as an option.
(This also raises the question of interfaces changing their addresses over the
course of a capture, which I'll have to raise on the pcap-ng mailing list....)
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
