[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2020-08-21 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 simon.leg...@gmail.com changed: What|Removed |Added CC||simon.leg...@gmail.com

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2019-11-13 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 fowl changed: What|Removed |Added CC||wireshar...@fowlsmurf.net -- You are

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2019-09-02 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 Bug 15104 depends on bug 16031, which changed state. Bug 16031 Summary: Netsh .etl files are treated as i4b, PacketLogger, or JSON files https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16031 What|Removed

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2019-09-02 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 Guy Harris changed: What|Removed |Added Depends on|6694| Referenced Bugs:

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2019-09-02 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 Guy Harris changed: What|Removed |Added Depends on||16031 Referenced Bugs:

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2019-09-02 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 Guy Harris changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2018-10-12 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 Michael Mann changed: What|Removed |Added Resolution|--- |DUPLICATE

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2018-09-12 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 --- Comment #8 from Niklas E --- (In reply to Peter Wu from comment #6) > Do you have an example packet capture file? > > I think that Dario looked into this (or it was on his wishlist), adding him > in cc. I don't have a sandbox

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2018-09-10 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 --- Comment #7 from Dario Lombardo --- > Which libraries on, for example, macOS and Linux have those APIs? They don't. My idea is to write an extcap that uses those native APIs (on windows only) that read the events and write a pcap

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2018-09-08 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 Peter Wu changed: What|Removed |Added Component|Dissection engine |Capture file support

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2018-09-05 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 Niklas E changed: What|Removed |Added Depends on||6694 --- Comment #5 from Niklas E

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2018-09-05 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 --- Comment #4 from Guy Harris --- (In reply to Niklas E from comment #2) > There is no public specification, but I was told to use APIs to read the > events from the .etl file. Perhaps those could be used? >

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2018-09-05 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 --- Comment #3 from Niklas E --- Also if you do this you would get .etl and .cap of same session: netsh trace start capture=yes filemode=circular maxsize=1024 tracefile=c:\%computername%.etl netsh trace stop Open Message Analyzer Open

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2018-09-05 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 --- Comment #2 from Niklas E --- There is no public specification, but I was told to use APIs to read the events from the .etl file. Perhaps those could be used?

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2018-09-03 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 Guy Harris changed: What|Removed |Added Severity|Normal |Enhancement

[Wireshark-bugs] [Bug 15104] Unable to open .etl Windows native network trace: netsh trace start capture=yes

2018-09-03 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15104 Niklas E changed: What|Removed |Added CC||raven...@hotmail.com