Wireshark-bugs: [Wireshark-bugs] [Bug 11115] wireshark-qt Follow UDP Stream Segmentation Fault
Comment # 3
on bug 11115
from ryanlmcmurray@gmail.com
(In reply to ryanlmcmurray from comment #2)
> Created attachment 13556 [details]
> created via Follow UDP Stream of Frame 1 of .pcap and Save As
>
> hello alexis,
> installed wireshark 1.99.x (install procedure below), and Follow UDP Stream
> on Frame 1 now does not result in seg fault; however, Save As "test.ts"
> (attached) results in "test.ts" not accurately representing the MPEG-TS data
> in the .pcap.
>
> steps to repro:
> 1. Follow UDP Stream of Frame 1
> 2. Show data as Hex Dump shows:
> 00000000 47 40 00 10 00 00 b0 0d 00 01 c1 00 00 00 01 e0 G@...... ........
>
> in Wireshark main window, Frame 1 in Hex Dump section shows:
> 0000 01 00 5e 33 fe 11 00 25 b5 1a a0 6f 08 00 45 00 ..^3...% ...o..E.
>
> this doesn't seem right. should i open a new bug to track this and we close
> this one?
>
> steps to install wireshark 1.99.5:
>
> $ brew reinstall --devel wireshark --with-qt
> ==> Reinstalling wireshark with --with-qt
> ==> Downloading
> https://www.wireshark.org/download/src/all-versions/wireshark-1.99.5.tar.bz2
> ########################################################################
> 100.0%
> ==> ./configure --disable-silent-rules
> --prefix=/usr/local/Cellar/wireshark/1.99.5 --with-gnutls --disable-gtktest
> --with-qt
> ==> make
> ==> make install
> ==> Caveats
> If your list of available capture interfaces is empty
> (default OS X behavior), try the following commands:
>
> curl https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3373 -o
> ChmodBPF.tar.gz
> tar zxvf ChmodBPF.tar.gz
> open ChmodBPF/Install\ ChmodBPF.app
>
> This adds a launch daemon that changes the permissions of your BPF
> devices so that all users in the 'admin' group - all users with
> 'Allow user to administer this computer' turned on - have both read
> and write access to those devices.
>
> See bug report:
> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3760
> ==> Summary
ah sorry. the hex data mismatch was simply due to Save as correctly stripping
off the ethernet, Frame, IP, and UDP headers/data; however, i would expect
"test.ts" to be playable via a video decoder (mpv, vlc, ffplay, etc.) and it is
not, so something seems to be going wrong with the Follow UDP Stream > Save As
functionality.
You are receiving this mail because:
- You are watching all bug changes.
