Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] wifi beacons show up as malformed

From: Reinoud Koornstra <reinoudkoornstra@xxxxxxxxx>
Date: Mon, 29 Apr 2019 15:18:56 -0700
Hi Anthony,

Apparently it was turned off.
I attached the pic of it. If it's not fcs related, why could the
packets show up as malformed and when other people open up the same
file, they see the packets fine?
Thanks,

Reinoud.

On Mon, Apr 29, 2019 at 3:10 PM Anthony Murabito
<anthony.murabito@xxxxxxxxx> wrote:
>
> https://wiki.wireshark.org/Wi-Fi
>
> It’s a setting in preferences for 802.11.
>
> Some capture software will mute FCS to all zero value.
> Ideally you want FCS captured, and wireshark to be able to validate it.
>
> On Apr 29, 2019, at 6:05 PM, Reinoud Koornstra <reinoudkoornstra@xxxxxxxxx> wrote:
>
> Hi Anthony,
>
> I am not sure whether my installation is configured to assume FCS.
> Since other people do not show those packets as malformed, perhaps I
> have that set?
> What can I check this/how to turn that off?
> Thanks,
>
> Reinoud.
>
> Th
>
> On Mon, Apr 29, 2019 at 3:02 PM Anthony Murabito
> <anthony.murabito@xxxxxxxxx> wrote:
>
>
> Hello,
>
> Do your captured packets include an FCS?
> Is your wireshark installation configured to assume packets have FCS?
>
>
> On Apr 29, 2019, at 5:37 PM, Reinoud Koornstra <reinoudkoornstra@xxxxxxxxx> wrote:
>
> Hi Everyone,
>
> Ive got something other people i know are not experiencing.
> When I am opening a sniff with wifi traffic, all beacons show up as malformed.
> Same with probe responses and lots of other traffic.
> When other's I know open that file on their own machine, it shows fine.
> I seem to be the only one who's having this problem.
> I resintalled wireshark, but to no avail.
> Did anyone experience this, is there a setting or anything I can do to
> remedy this?
> Thanks,
>
> Reinoud.
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>
>
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>
>
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>              mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

Attachment: 80211_settings_wireshark.png
Description: PNG image