https://wiki.wireshark.org/Wi-Fi <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 <reinoudkoorns...@gmail.com> 
> 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.murab...@gmail.com> 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 <reinoudkoorns...@gmail.com> 
>>> 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@wireshark.org>
>>> Archives:    https://www.wireshark.org/lists/wireshark-users
>>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>>>            mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
>> 
>> ___________________________________________________________________________
>> Sent via:    Wireshark-users mailing list <wireshark-users@wireshark.org>
>> Archives:    https://www.wireshark.org/lists/wireshark-users
>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>>             mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@wireshark.org>
> Archives:    https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>             mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe

Reply via email to