unsubscribe
-----Original Message-----
From: Wireshark-users [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of wireshark-users-request@xxxxxxxxxxxxx
Sent: Monday, August 07, 2017 8:00 AM
To: wireshark-users@xxxxxxxxxxxxx
Subject: Wireshark-users Digest, Vol 135, Issue 2
Send Wireshark-users mailing list submissions to
wireshark-users@xxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://www.wireshark.org/mailman/listinfo/wireshark-users
or, via email, send a message with subject or body 'help' to
wireshark-users-request@xxxxxxxxxxxxx
You can reach the person managing the list at
wireshark-users-owner@xxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific than "Re: Contents of Wireshark-users digest..."
Today's Topics:
1. Unsubscribe (Michael Ferrara)
----------------------------------------------------------------------
Message: 1
Date: Sun, 6 Aug 2017 14:44:52 -0700
From: Michael Ferrara <mferrara1@xxxxxxxxx>
To: wireshark-users@xxxxxxxxxxxxx
Subject: [Wireshark-users] Unsubscribe
Message-ID:
<CANB4v15mZhWp90YQsFyffymgvku2CY_D5L6DmRT7CJB3+83jSA@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
On Aug 4, 2017 7:25 AM, "Jacobo Pantoja" <jacobopantoja@xxxxxxxxx> wrote:
> Hi,
>
> I'm trying to capture network traffic between a wireless bridge made
> with two OpenWRT devices, which means they use 4 address atheros stuff
> for wireless bridge. For testing, beside the "client" AP, a non-wds
> client joined to the "master" AP.
>
> The AP is using WPA2-PSK, and I can sucessfully see decrypted traffic
> for non-wds clients, i.e. frames with both wlan.fc.ds set to 01 and to
> 10. But traffic from the "client" AP to the "master" AP (i.e. frames
> with wlan.fc.ds == 11) are not decrypted.
>
> I guess that the PSK should be the same for the non-wds clients than
> for the wds client, but perhaps I'm wrong. All the EAPOL messages are
> properly captured. Also, I don't know if the 4address Linux stuff is
> adding something non-standard that WireShark cannot deal with at this moment.
>
> Any ideas?
> ____________________________________________________________
> _______________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.wireshark.org/lists/wireshark-users/attachments/20170806/a567ff30/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
Wireshark-users mailing list
Wireshark-users@xxxxxxxxxxxxx
https://www.wireshark.org/mailman/listinfo/wireshark-users
------------------------------
End of Wireshark-users Digest, Vol 135, Issue 2
***********************************************
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
