* how to get info about connected clients when iwd runs in AP mode?
@ 2021-08-06 6:30 salahaldeen.altous
2021-08-06 16:32 ` James Prestwood
2021-08-06 18:32 ` Denis Kenzior
0 siblings, 2 replies; 13+ messages in thread
From: salahaldeen.altous @ 2021-08-06 6:30 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
Hi,
I have a device which running as AP point. I would like to know every time there is a new connection/discounntion for this access point.
Does iwd API support this? DHCP is enable in AP configuration (EnableNetworkConfiguration=True)
Regards,
Salahaldeen Altous
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-06 6:30 how to get info about connected clients when iwd runs in AP mode? salahaldeen.altous
@ 2021-08-06 16:32 ` James Prestwood
2021-08-09 7:22 ` Altous, Salahaldeen
2021-08-06 18:32 ` Denis Kenzior
1 sibling, 1 reply; 13+ messages in thread
From: James Prestwood @ 2021-08-06 16:32 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
Hi,
On Fri, 2021-08-06 at 06:30 +0000, salahaldeen.altous(a)leica-camera.com
wrote:
> Hi,
>
> I have a device which running as AP point. I would like to know every
> time there is a new connection/discounntion for this access point.
> Does iwd API support this? DHCP is enable in AP configuration
> (EnableNetworkConfiguration=True)
There is an access point API, GetDiagnostics(), which returns an array
of clients (including some info about each client):
https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/doc/access-point-diagnostic-api.txt
Unfortunately you cant get notified for this via PropertyChanged since
its a DBus method rather than properties. This was done because some of
the client info can change quite frequently (RSSI, Tx/Rx rates/modes
etc) and we didn't want to flood DBus with these messages constantly.
In iwctl we actually poll this information every second.
Thanks,
James
>
> Regards,
> Salahaldeen Altous
> _______________________________________________
> iwd mailing list -- iwd(a)lists.01.org
> To unsubscribe send an email to iwd-leave(a)lists.01.org
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-06 6:30 how to get info about connected clients when iwd runs in AP mode? salahaldeen.altous
2021-08-06 16:32 ` James Prestwood
@ 2021-08-06 18:32 ` Denis Kenzior
2021-08-09 7:26 ` Altous, Salahaldeen
1 sibling, 1 reply; 13+ messages in thread
From: Denis Kenzior @ 2021-08-06 18:32 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
Hi Salahaldeen Altous,
On 8/6/21 1:30 AM, salahaldeen.altous(a)leica-camera.com wrote:
> Hi,
>
> I have a device which running as AP point. I would like to know every time there is a new connection/discounntion for this access point.
> Does iwd API support this? DHCP is enable in AP configuration (EnableNetworkConfiguration=True)
There isn't a nice API for this just yet. James pointed you to the Diagnostics
API, but that is really meant to be polled since the information changes way too
frequently and it is only useful as a 'snapshot'.
What you need is a dedicated API that would inform the application via D-Bus
when a new client has connected / disconnect. This would need to be modeled as
a D-Bus property, or perhaps using an Agent type API. Not something we have
planned to work on just yet. Patches are always welcome.
Regards,
-Denis
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-06 16:32 ` James Prestwood
@ 2021-08-09 7:22 ` Altous, Salahaldeen
2021-08-09 15:58 ` James Prestwood
0 siblings, 1 reply; 13+ messages in thread
From: Altous, Salahaldeen @ 2021-08-09 7:22 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 2819 bytes --]
Hi James,
On Fri, 2021-08-06 at 09:32 -0700, James Prestwood wrote:
> Hi,
>
> On Fri, 2021-08-06 at 06:30 +0000,
> salahaldeen.altous(a)leica-camera.com
> wrote:
> > Hi,
> >
> > I have a device which running as AP point. I would like to know
> > every
> > time there is a new connection/discounntion for this access point.
> > Does iwd API support this? DHCP is enable in AP configuration
> > (EnableNetworkConfiguration=True)
>
> There is an access point API, GetDiagnostics(), which returns an
> array
> of clients (including some info about each client):
>
> https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/doc/access-point-diagnostic-api.txt
thanks I will test it. Is there any ready python test script for it?
>
> Unfortunately you cant get notified for this via PropertyChanged
> since
> its a DBus method rather than properties. This was done because some
> of
> the client info can change quite frequently (RSSI, Tx/Rx rates/modes
> etc) and we didn't want to flood DBus with these messages constantly.
>
> In iwctl we actually poll this information every second.
I was looking for notification via PropertyChanged callback. I am using
iwd 1.13. when I run iwctl ap wlan0 show it returns always 0 client!!
is this a bug in the old version?
Access Point
Interface *
---------------------------------------------------------------------
-----------
Settable Property Value
---------------------------------------------------------------------
-----------
Started yes
Name xxxxx-5587111
Client
0
---------------------------------------------------------------------
-----------
Property Value
---------------------------------------------------------------------
-----------
Address 84:25:3f:9f:c2:54
RxBitrate 0 Kbit/s
ExpectedThroughput 14722096 Kbit/s
[iwd]#
>
> Thanks,
> James
Regards,Salahaldeen
>
> > Regards,
> > Salahaldeen Altous
> > _______________________________________________
> > iwd mailing list -- iwd(a)lists.01.org
> > To unsubscribe send an email to iwd-leave(a)lists.01.org
>
>
Leica Camera AG | Registergericht | District Court of Wetzlar: HRB966
Vorstand | Executive Board: Matthias Harsch (Vorsitzender) | Dr. Marita Paasch
Aufsichtsratsvorsitzender | Chairman of the Supervisory Board: Dr. Andreas Kaufmann
This message may contain confidential and privileged information. If it has been sent to you in error, please notify the sender immediately by replying to the message and please delete it from your computer.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-06 18:32 ` Denis Kenzior
@ 2021-08-09 7:26 ` Altous, Salahaldeen
0 siblings, 0 replies; 13+ messages in thread
From: Altous, Salahaldeen @ 2021-08-09 7:26 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]
Hi Denis,
On Fri, 2021-08-06 at 13:32 -0500, Denis Kenzior wrote:
> Hi Salahaldeen Altous,
>
> On 8/6/21 1:30 AM, salahaldeen.altous(a)leica-camera.com wrote:
> > Hi,
> >
> > I have a device which running as AP point. I would like to know
> > every time there is a new connection/discounntion for this access
> > point.
> > Does iwd API support this? DHCP is enable in AP configuration
> > (EnableNetworkConfiguration=True)
>
> There isn't a nice API for this just yet. James pointed you to the
> Diagnostics
> API, but that is really meant to be polled since the information
> changes way too
> frequently and it is only useful as a 'snapshot'.
>
> What you need is a dedicated API that would inform the application
> via D-Bus
> when a new client has connected / disconnect. This would need to be
> modeled as
> a D-Bus property, or perhaps using an Agent type API. Not something
> we have
> planned to work on just yet. Patches are always welcome.
This exactly what my application needs (to be informed via D-Bus when a
new client has connected/disconnected). I will try to check if I can
add it.
>
> Regards,
> -Denis
Regards,
Salahaldeen
Leica Camera AG | Registergericht | District Court of Wetzlar: HRB966
Vorstand | Executive Board: Matthias Harsch (Vorsitzender) | Dr. Marita Paasch
Aufsichtsratsvorsitzender | Chairman of the Supervisory Board: Dr. Andreas Kaufmann
This message may contain confidential and privileged information. If it has been sent to you in error, please notify the sender immediately by replying to the message and please delete it from your computer.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-09 7:22 ` Altous, Salahaldeen
@ 2021-08-09 15:58 ` James Prestwood
2021-08-10 5:34 ` Altous, Salahaldeen
0 siblings, 1 reply; 13+ messages in thread
From: James Prestwood @ 2021-08-09 15:58 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 3674 bytes --]
Hi,
On Mon, 2021-08-09 at 07:22 +0000, Altous, Salahaldeen wrote:
> Hi James,
>
> On Fri, 2021-08-06 at 09:32 -0700, James Prestwood wrote:
> > Hi,
> >
> > On Fri, 2021-08-06 at 06:30 +0000,
> > salahaldeen.altous(a)leica-camera.com
> > wrote:
> > > Hi,
> > >
> > > I have a device which running as AP point. I would like to know
> > > every
> > > time there is a new connection/discounntion for this access
> > > point.
> > > Does iwd API support this? DHCP is enable in AP configuration
> > > (EnableNetworkConfiguration=True)
> >
> > There is an access point API, GetDiagnostics(), which returns an
> > array
> > of clients (including some info about each client):
> >
> > https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/doc/access-point-diagnostic-api.txt
>
> thanks I will test it. Is there any ready python test script for it?
Unfortunately no. Currently only iwctl uses GetDiagnostics() which you
used below.
> >
> > Unfortunately you cant get notified for this via PropertyChanged
> > since
> > its a DBus method rather than properties. This was done because
> > some
> > of
> > the client info can change quite frequently (RSSI, Tx/Rx
> > rates/modes
> > etc) and we didn't want to flood DBus with these messages
> > constantly.
> >
> > In iwctl we actually poll this information every second.
>
>
> I was looking for notification via PropertyChanged callback. I am
> using
> iwd 1.13. when I run iwctl ap wlan0 show it returns always 0 client!!
> is this a bug in the old version?
>
> Access Point
> Interface *
> ---------------------------------------------------------------------
> -----------
> Settable Property Value
> ---------------------------------------------------------------------
> -----------
> Started yes
> Name xxxxx-5587111
>
> Client
> 0
> ---------------------------------------------------------------------
> -----------
> Property Value
> ---------------------------------------------------------------------
> -----------
> Address 84:25:3f:9f:c2:54
> RxBitrate 0 Kbit/s
> ExpectedThroughput 14722096 Kbit/s
I'll admit this may look somewhat confusing, but this is actually
printing out the one client that is connected, client 0.
I will say there is very little information here. What card are you
using?
>
> [iwd]#
>
>
> >
> > Thanks,
> > James
>
> Regards,Salahaldeen
> >
> > > Regards,
> > > Salahaldeen Altous
> > > _______________________________________________
> > > iwd mailing list -- iwd(a)lists.01.org
> > > To unsubscribe send an email to iwd-leave(a)lists.01.org
> >
> >
> Leica Camera AG | Registergericht | District Court of Wetzlar: HRB966
> Vorstand | Executive Board: Matthias Harsch (Vorsitzender) | Dr.
> Marita Paasch
> Aufsichtsratsvorsitzender | Chairman of the Supervisory Board: Dr.
> Andreas Kaufmann
>
> This message may contain confidential and privileged information. If
> it has been sent to you in error, please notify the sender
> immediately by replying to the message and please delete it from your
> computer.
Thanks,
James
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-09 15:58 ` James Prestwood
@ 2021-08-10 5:34 ` Altous, Salahaldeen
2021-08-10 8:22 ` salahaldeen.altous
2021-08-10 15:55 ` James Prestwood
0 siblings, 2 replies; 13+ messages in thread
From: Altous, Salahaldeen @ 2021-08-10 5:34 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 4239 bytes --]
Hi James,
On Mon, 2021-08-09 at 08:58 -0700, James Prestwood wrote:
> Hi,
>
> On Mon, 2021-08-09 at 07:22 +0000, Altous, Salahaldeen wrote:
> > Hi James,
> >
> > On Fri, 2021-08-06 at 09:32 -0700, James Prestwood wrote:
> > > Hi,
> > >
> > > On Fri, 2021-08-06 at 06:30 +0000,
> > > salahaldeen.altous(a)leica-camera.com
> > > wrote:
> > > > Hi,
> > > >
> > > > I have a device which running as AP point. I would like to know
> > > > every
> > > > time there is a new connection/discounntion for this access
> > > > point.
> > > > Does iwd API support this? DHCP is enable in AP configuration
> > > > (EnableNetworkConfiguration=True)
> > >
> > > There is an access point API, GetDiagnostics(), which returns an
> > > array
> > > of clients (including some info about each client):
> > >
> > > https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/doc/access-point-diagnostic-api.txt
> >
> > thanks I will test it. Is there any ready python test script for
> > it?
>
> Unfortunately no. Currently only iwctl uses GetDiagnostics() which
> you
> used below.
>
> > > Unfortunately you cant get notified for this via PropertyChanged
> > > since
> > > its a DBus method rather than properties. This was done because
> > > some
> > > of
> > > the client info can change quite frequently (RSSI, Tx/Rx
> > > rates/modes
> > > etc) and we didn't want to flood DBus with these messages
> > > constantly.
> > >
> > > In iwctl we actually poll this information every second.
> >
> > I was looking for notification via PropertyChanged callback. I am
> > using
> > iwd 1.13. when I run iwctl ap wlan0 show it returns always 0
> > client!!
> > is this a bug in the old version?
> >
> > Access Point
> > Interface *
> > -----------------------------------------------------------------
> > ----
> > -----------
> > Settable Property Value
> > -----------------------------------------------------------------
> > ----
> > -----------
> > Started yes
> > Name xxxxx-5587111
> >
> > Client
> > 0
> > -----------------------------------------------------------------
> > ----
> > -----------
> > Property Value
> > -----------------------------------------------------------------
> > ----
> > -----------
> > Address 84:25:3f:9f:c2:54
> > RxBitrate 0 Kbit/s
> > ExpectedThroughput 14722096 Kbit/s
>
> I'll admit this may look somewhat confusing, but this is actually
> printing out the one client that is connected, client 0.
>
I have connected multiple clients at this time but it returns only
client 0
> I will say there is very little information here. What card are you
> using?
>
I am using qualcomm qca9377 chip
> > [iwd]#
> >
> >
> > > Thanks,
> > > James
> >
> > Regards,Salahaldeen
> > > > Regards,
> > > > Salahaldeen Altous
> > > > _______________________________________________
> > > > iwd mailing list -- iwd(a)lists.01.org
> > > > To unsubscribe send an email to iwd-leave(a)lists.01.org
> > Leica Camera AG | Registergericht | District Court of Wetzlar:
> > HRB966
> > Vorstand | Executive Board: Matthias Harsch (Vorsitzender) | Dr.
> > Marita Paasch
> > Aufsichtsratsvorsitzender | Chairman of the Supervisory Board: Dr.
> > Andreas Kaufmann
> >
> > This message may contain confidential and privileged information.
> > If
> > it has been sent to you in error, please notify the sender
> > immediately by replying to the message and please delete it from
> > your
> > computer.
>
> Thanks,
> James
>
Leica Camera AG | Registergericht | District Court of Wetzlar: HRB966
Vorstand | Executive Board: Matthias Harsch (Vorsitzender) | Dr. Marita Paasch
Aufsichtsratsvorsitzender | Chairman of the Supervisory Board: Dr. Andreas Kaufmann
This message may contain confidential and privileged information. If it has been sent to you in error, please notify the sender immediately by replying to the message and please delete it from your computer.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-10 5:34 ` Altous, Salahaldeen
@ 2021-08-10 8:22 ` salahaldeen.altous
2021-08-10 15:55 ` James Prestwood
1 sibling, 0 replies; 13+ messages in thread
From: salahaldeen.altous @ 2021-08-10 8:22 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
> Hi James,
> On Mon, 2021-08-09 at 08:58 -0700, James Prestwood wrote:
> I have connected multiple clients at this time but it returns only
> client 0
> I am using qualcomm qca9377 chip
the output for dbus-mointer looks like this (only one client even more than one client are connected)
method call time=2754.711884 sender=:1.5 -> destination=net.connman.iwd serial=15 path=/net/connman/iwd/0/4; interface=net.connman.iwd.AccessPointDiagnostic; member=GetDiagnostics
method return time=2754.715240 sender=:1.0 -> destination=:1.5 serial=81 reply_serial=15
array [
array [
dict entry(
string "Address"
variant string "84:25:3f:9f:XX:XX"
)
dict entry(
string "TxBitrate"
variant uint32 1995880597
)
dict entry(
string "ExpectedThroughput"
variant uint32 30397488
)
]
]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-10 5:34 ` Altous, Salahaldeen
2021-08-10 8:22 ` salahaldeen.altous
@ 2021-08-10 15:55 ` James Prestwood
2021-08-10 17:38 ` Altous, Salahaldeen
1 sibling, 1 reply; 13+ messages in thread
From: James Prestwood @ 2021-08-10 15:55 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 3391 bytes --]
Hi,
<snip>
> > >
> > > I was looking for notification via PropertyChanged callback. I am
> > > using
> > > iwd 1.13. when I run iwctl ap wlan0 show it returns always 0
> > > client!!
> > > is this a bug in the old version?
> > >
> > > Access Point
> > > Interface *
> > > -----------------------------------------------------------------
> > > ----
> > > -----------
> > > Settable Property Value
> > > -----------------------------------------------------------------
> > > ----
> > > -----------
> > > Started yes
> > > Name xxxxx-5587111
> > >
> > > Client
> > > 0
> > > -----------------------------------------------------------------
> > > ----
> > > -----------
> > > Property Value
> > > -----------------------------------------------------------------
> > > ----
> > > -----------
> > > Address 84:25:3f:9f:c2:54
> > > RxBitrate 0 Kbit/s
> > > ExpectedThroughput 14722096 Kbit/s
> >
> > I'll admit this may look somewhat confusing, but this is actually
> > printing out the one client that is connected, client 0.
> >
> I have connected multiple clients at this time but it returns only
> client 0
Would there be any way you could run iwmon at the same time as "ap
wlan0 show" ? We get all this information from the nl8011 GET_STATION
API so I'm curious to see exactly what that is coming up with.
> > I will say there is very little information here. What card are you
> > using?
> >
> I am using qualcomm qca9377 chip
> > > [iwd]#
> > >
> > >
> > > > Thanks,
> > > > James
> > >
> > > Regards,Salahaldeen
> > > > > Regards,
> > > > > Salahaldeen Altous
> > > > > _______________________________________________
> > > > > iwd mailing list -- iwd(a)lists.01.org
> > > > > To unsubscribe send an email to iwd-leave(a)lists.01.org
> > > Leica Camera AG | Registergericht | District Court of Wetzlar:
> > > HRB966
> > > Vorstand | Executive Board: Matthias Harsch (Vorsitzender) | Dr.
> > > Marita Paasch
> > > Aufsichtsratsvorsitzender | Chairman of the Supervisory Board:
> > > Dr.
> > > Andreas Kaufmann
> > >
> > > This message may contain confidential and privileged information.
> > > If
> > > it has been sent to you in error, please notify the sender
> > > immediately by replying to the message and please delete it from
> > > your
> > > computer.
> >
> > Thanks,
> > James
> >
> Leica Camera AG | Registergericht | District Court of Wetzlar: HRB966
> Vorstand | Executive Board: Matthias Harsch (Vorsitzender) | Dr.
> Marita Paasch
> Aufsichtsratsvorsitzender | Chairman of the Supervisory Board: Dr.
> Andreas Kaufmann
>
> This message may contain confidential and privileged information. If
> it has been sent to you in error, please notify the sender
> immediately by replying to the message and please delete it from your
> computer.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-10 15:55 ` James Prestwood
@ 2021-08-10 17:38 ` Altous, Salahaldeen
2021-08-10 18:24 ` James Prestwood
0 siblings, 1 reply; 13+ messages in thread
From: Altous, Salahaldeen @ 2021-08-10 17:38 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 4518 bytes --]
On Tue, 2021-08-10 at 08:55 -0700, James Prestwood wrote:
> Hi,
>
> <snip>
> > > > I was looking for notification via PropertyChanged callback. I
> > > > am
> > > > using
> > > > iwd 1.13. when I run iwctl ap wlan0 show it returns always 0
> > > > client!!
> > > > is this a bug in the old version?
> > > >
> > > > Access Point
> > > > Interface *
> > > > -------------------------------------------------------------
> > > > ----
> > > > ----
> > > > -----------
> > > > Settable Property Value
> > > > -------------------------------------------------------------
> > > > ----
> > > > ----
> > > > -----------
> > > > Started yes
> > > > Name xxxxx-5587111
> > > >
> > > > Client
> > > > 0
> > > > -------------------------------------------------------------
> > > > ----
> > > > ----
> > > > -----------
> > > > Property Value
> > > > -------------------------------------------------------------
> > > > ----
> > > > ----
> > > > -----------
> > > > Address 84:25:3f:9f:c2:54
> > > > RxBitrate 0 Kbit/s
> > > > ExpectedThroughput 14722096 Kbit/s
> > >
> > > I'll admit this may look somewhat confusing, but this is actually
> > > printing out the one client that is connected, client 0.
> > >
> > I have connected multiple clients at this time but it returns only
> > client 0
>
> Would there be any way you could run iwmon at the same time as "ap
> wlan0 show" ? We get all this information from the nl8011 GET_STATION
> API so I'm curious to see exactly what that is coming up with.
>
< Request: Get Station (0x11) len 8
[ack,0x300]
58.821834
Interface Index: 4 (0x00000004)
> Result: New Station (0x13) len 32
[multi]
58.821939
Interface Index: 4 (0x00000004)
MAC Address 84:25:3F:9F:C2:54
Generation: 0 (0x00000000)
Station Info: len 0
> Complete: Get Station (0x11) len 4
[multi]
58.822000
Status: 0
At this time 2 clients were connected to this AP (2x Event: New
Station)
attached you can find the whole log before connecting the 2 clients
> > > I will say there is very little information here. What card are
> > > you
> > > using?
> > >
> > I am using qualcomm qca9377 chip
> > > > [iwd]#
> > > >
> > > >
> > > > > Thanks,
> > > > > James
> > > >
> > > > Regards,Salahaldeen
> > > > > > Regards,
> > > > > > Salahaldeen Altous
> > > > > > _______________________________________________
> > > > > > iwd mailing list -- iwd(a)lists.01.org
> > > > > > To unsubscribe send an email to iwd-leave(a)lists.01.org
> > > > Leica Camera AG | Registergericht | District Court of Wetzlar:
> > > > HRB966
> > > > Vorstand | Executive Board: Matthias Harsch (Vorsitzender) |
> > > > Dr.
> > > > Marita Paasch
> > > > Aufsichtsratsvorsitzender | Chairman of the Supervisory Board:
> > > > Dr.
> > > > Andreas Kaufmann
> > > >
> > > > This message may contain confidential and privileged
> > > > information.
> > > > If
> > > > it has been sent to you in error, please notify the sender
> > > > immediately by replying to the message and please delete it
> > > > from
> > > > your
> > > > computer.
> > >
> > > Thanks,
> > > James
> > >
> > Leica Camera AG | Registergericht | District Court of Wetzlar:
> > HRB966
> > Vorstand | Executive Board: Matthias Harsch (Vorsitzender) | Dr.
> > Marita Paasch
> > Aufsichtsratsvorsitzender | Chairman of the Supervisory Board: Dr.
> > Andreas Kaufmann
> >
> > This message may contain confidential and privileged information.
> > If
> > it has been sent to you in error, please notify the sender
> > immediately by replying to the message and please delete it from
> > your
> > computer.
>
>
Leica Camera AG | Registergericht | District Court of Wetzlar: HRB966
Vorstand | Executive Board: Matthias Harsch (Vorsitzender) | Dr. Marita Paasch
Aufsichtsratsvorsitzender | Chairman of the Supervisory Board: Dr. Andreas Kaufmann
This message may contain confidential and privileged information. If it has been sent to you in error, please notify the sender immediately by replying to the message and please delete it from your computer.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: AP-2clients.log --]
[-- Type: text/x-log, Size: 57810 bytes --]
> Event: New Station (0x13) len 60 201.523521
Interface Index: 4 (0x00000004)
MAC Address 04:D6:AA:61:41:3C
Generation: 0 (0x00000000)
Station Info: len 0
Information Elements: len 22
RSN:
Group Data Cipher Suite: len 4
CCMP (00:0f:ac) suite 04
Pairwise Cipher Suite: len 4
CCMP (00:0f:ac) suite 04
AKM Suite: len 4
PSK; RSNA PSK (00:0f:ac) suite 02
RSN capabilities: bits 2 - 3: 1 replay counter per PTKSA
RSN capabilities: bits 4 - 5: 1 replay counter per GTKSA
RSN capabilities: bit 7: Management Frame Protection Capable
01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ................
ac 02 80 00 ....
< Request: Set Station (0x12) len 32 [ack] 201.524369
Interface Index: 4 (0x00000004)
MAC Address 04:D6:AA:61:41:3C
Station Flags 2: len 8
Mask: 0x00000002
Authorized
Set: 0x00000000
< PAE: len 121 201.525273
Interface Index: 4
EAPoL: len 121
Protocol Version: 2 (802.1X-2004)
Type: 3 (Key)
Length: 117
Descriptor Type: 2
Key MIC: false
Secure: false
Error: false
Request: false
Encrypted Key Data: false
SMK Message: false
Key Descriptor Version: 2 (02)
Key Type: true
Install: false
Key ACK: true
Key Length: 16
Key Replay Counter: 1
Key NONCE
87 46 6d f1 65 ce aa 5d 28 19 d0 d2 bb 90 96 f1 .Fm.e..](.......
f0 a1 1d 06 d2 35 82 61 73 59 7c aa bf 2a dc cf .....5.asY|..*..
Key IV
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key RSC
00 00 00 00 00 00 00 00 ........
Key MIC Data
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key Data: len 22
Vendor specific: len 20
IEEE 802.11 (00:0f:ac) type: 04
PMKID KDE
00 0f ac 04 fd 5a d5 27 35 4f 32 31 96 34 b9 45 .....Z.'5O21.4.E
3e 18 1d 34 >..4
02 03 00 75 02 00 8a 00 10 00 00 00 00 00 00 00 ...u............
01 87 46 6d f1 65 ce aa 5d 28 19 d0 d2 bb 90 96 ..Fm.e..](......
f1 f0 a1 1d 06 d2 35 82 61 73 59 7c aa bf 2a dc ......5.asY|..*.
cf 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 16 dd 14 00 0f ac 04 fd 5a d5 27 35 4f 32 ..........Z.'5O2
31 96 34 b9 45 3e 18 1d 34 1.4.E>..4
> Response: Set Station (0x12) len 4 201.524443
Status: Success (0)
< Request: Get Key (0x09) len 16 [ack] 201.524516
Interface Index: 4 (0x00000004)
Key Index: 1 (0x01)
> Result: New Key (0x0b) len 52 201.524574
Interface Index: 4 (0x00000004)
Key Index: 1 (0x01)
Key Data: len 0
Key Cipher: unknown (00:00:00) suite 01 (unknown)
Key: len 20
04 00 01 00 08 00 03 00 01 00 00 00 05 00 02 00 ................
01 00 00 00 ....
> Response: Get Key (0x09) len 4 201.524593
Status: Success (0)
> RTNL: New Link (0x10) len 52 201.533498
Flags: 0 (0x000)
Sequence number: 0 (0x00000000)
Port ID: 0
IFLA Family: Unknown
IFLA Type: 1
IFLA Index: 4
IFLA ChangeMask: 0
IFLA Flags: (0x1043) [up,broadcast,running,multicast]
IfName (len:6): wlan0
Wireless: len 20
14 00 03 8c 01 00 04 d6 aa 61 41 3c 00 00 00 00 .........aA<....
00 00 00 00 ....
< PAE: len 121 201.639768
Interface Index: 4
EAPoL: len 121
Protocol Version: 2 (802.1X-2004)
Type: 3 (Key)
Length: 117
Descriptor Type: 2
Key MIC: false
Secure: false
Error: false
Request: false
Encrypted Key Data: false
SMK Message: false
Key Descriptor Version: 2 (02)
Key Type: true
Install: false
Key ACK: true
Key Length: 16
Key Replay Counter: 2
Key NONCE
b0 93 39 6d 60 09 4f f0 2c b5 3e fb f5 b8 f4 b1 ..9m`.O.,.>.....
12 c3 9f 2c 7c 15 dd 4d 33 a1 e9 df 92 ac 00 e6 ...,|..M3.......
Key IV
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key RSC
00 00 00 00 00 00 00 00 ........
Key MIC Data
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key Data: len 22
Vendor specific: len 20
IEEE 802.11 (00:0f:ac) type: 04
PMKID KDE
00 0f ac 04 fd 5a d5 27 35 4f 32 31 96 34 b9 45 .....Z.'5O21.4.E
3e 18 1d 34 >..4
02 03 00 75 02 00 8a 00 10 00 00 00 00 00 00 00 ...u............
02 b0 93 39 6d 60 09 4f f0 2c b5 3e fb f5 b8 f4 ...9m`.O.,.>....
b1 12 c3 9f 2c 7c 15 dd 4d 33 a1 e9 df 92 ac 00 ....,|..M3......
e6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 16 dd 14 00 0f ac 04 fd 5a d5 27 35 4f 32 ..........Z.'5O2
31 96 34 b9 45 3e 18 1d 34 1.4.E>..4
> PAE: len 121 201.649411
Interface Index: 4
EAPoL: len 121
Protocol Version: 1 (802.1X-2001)
Type: 3 (Key)
Length: 117
Descriptor Type: 2
Key MIC: true
Secure: false
Error: false
Request: false
Encrypted Key Data: false
SMK Message: false
Key Descriptor Version: 2 (02)
Key Type: true
Install: false
Key ACK: false
Key Length: 0
Key Replay Counter: 2
Key NONCE
fb 26 3e 75 b2 e6 a1 ea 47 81 55 02 9c 0b 41 4e .&>u....G.U...AN
07 8c a9 ce 5e 7e b3 91 7a 81 1b 1b a6 5e 36 ee ....^~..z....^6.
Key IV
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key RSC
00 00 00 00 00 00 00 00 ........
Key MIC Data
e7 7d a8 84 b3 57 ba 19 09 56 70 e2 58 da 09 4d .}...W...Vp.X..M
Key Data: len 22
RSN:
Group Data Cipher Suite: len 4
CCMP (00:0f:ac) suite 04
Pairwise Cipher Suite: len 4
CCMP (00:0f:ac) suite 04
AKM Suite: len 4
PSK; RSNA PSK (00:0f:ac) suite 02
RSN capabilities: bits 2 - 3: 1 replay counter per PTKSA
RSN capabilities: bits 4 - 5: 1 replay counter per GTKSA
RSN capabilities: bit 7: Management Frame Protection Capable
01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ................
ac 02 80 00 ....
01 03 00 75 02 01 0a 00 00 00 00 00 00 00 00 00 ...u............
02 fb 26 3e 75 b2 e6 a1 ea 47 81 55 02 9c 0b 41 ..&>u....G.U...A
4e 07 8c a9 ce 5e 7e b3 91 7a 81 1b 1b a6 5e 36 N....^~..z....^6
ee 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 e7 7d a8 84 b3 57 ba 19 09 56 70 e2 58 da 09 ..}...W...Vp.X..
4d 00 16 30 14 01 00 00 0f ac 04 01 00 00 0f ac M..0............
04 01 00 00 0f ac 02 80 00 .........
< PAE: len 155 201.658347
Interface Index: 4
EAPoL: len 155
Protocol Version: 2 (802.1X-2004)
Type: 3 (Key)
Length: 151
Descriptor Type: 2
Key MIC: true
Secure: true
Error: false
Request: false
Encrypted Key Data: true
SMK Message: false
Key Descriptor Version: 2 (02)
Key Type: true
Install: true
Key ACK: true
Key Length: 16
Key Replay Counter: 3
Key NONCE
b0 93 39 6d 60 09 4f f0 2c b5 3e fb f5 b8 f4 b1 ..9m`.O.,.>.....
12 c3 9f 2c 7c 15 dd 4d 33 a1 e9 df 92 ac 00 e6 ...,|..M3.......
Key IV
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key RSC
00 00 00 00 00 00 00 00 ........
Key MIC Data
0e d9 7d 60 0f 44 37 be 7c 8b d0 3b 2b b6 e6 35 ..}`.D7.|..;+..5
Key Data: len 56
e1 4d 00 17 d9 ec fe c7 7f 9f c2 92 3b 02 6f d4 .M..........;.o.
c2 c7 da 21 53 f7 44 ca b8 93 86 00 e4 43 bd 0f ...!S.D......C..
f9 80 b1 a7 9a d9 a8 ed be 77 0c 8d ba f4 27 a6 .........w....'.
f7 8a ab b9 bc 1d de 8d ........
02 03 00 97 02 13 ca 00 10 00 00 00 00 00 00 00 ................
03 b0 93 39 6d 60 09 4f f0 2c b5 3e fb f5 b8 f4 ...9m`.O.,.>....
b1 12 c3 9f 2c 7c 15 dd 4d 33 a1 e9 df 92 ac 00 ....,|..M3......
e6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 0e d9 7d 60 0f 44 37 be 7c 8b d0 3b 2b b6 e6 ...}`.D7.|..;+..
35 00 38 e1 4d 00 17 d9 ec fe c7 7f 9f c2 92 3b 5.8.M..........;
02 6f d4 c2 c7 da 21 53 f7 44 ca b8 93 86 00 e4 .o....!S.D......
43 bd 0f f9 80 b1 a7 9a d9 a8 ed be 77 0c 8d ba C...........w...
f4 27 a6 f7 8a ab b9 bc 1d de 8d .'.........
> PAE: len 99 201.667980
Interface Index: 4
EAPoL: len 99
Protocol Version: 1 (802.1X-2001)
Type: 3 (Key)
Length: 95
Descriptor Type: 2
Key MIC: true
Secure: true
Error: false
Request: false
Encrypted Key Data: false
SMK Message: false
Key Descriptor Version: 2 (02)
Key Type: true
Install: false
Key ACK: false
Key Length: 0
Key Replay Counter: 3
Key NONCE
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key IV
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key RSC
00 00 00 00 00 00 00 00 ........
Key MIC Data
34 61 96 74 5f 6b d5 64 3d 4b 4f e7 4f 2d 5d f1 4a.t_k.d=KO.O-].
Key Data: len 0
01 03 00 5f 02 03 0a 00 00 00 00 00 00 00 00 00 ..._............
03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 34 61 96 74 5f 6b d5 64 3d 4b 4f e7 4f 2d 5d .4a.t_k.d=KO.O-]
f1 00 00 ...
< Request: Unknown (0x00) len 56 [ack] 201.668387
> Response: Unknown (0x00) len 4 201.669552
Status: Success (0)
< Request: Set Station (0x12) len 32 [ack] 201.669646
Interface Index: 4 (0x00000004)
MAC Address 04:D6:AA:61:41:3C
Station Flags 2: len 8
Mask: 0x00000002
Authorized
Set: 0x00000002
Authorized
> Response: Set Station (0x12) len 4 201.670174
Status: Success (0)
< RTNL: Set Link (0x13) len 32 [request,ack] 201.670307
Flags: 5 (0x005)
Sequence number: 11 (0x0000000b)
Port ID: 226
IFLA Family: Unknown
IFLA Type: 0
IFLA Index: 4
IFLA ChangeMask: 0
IFLA Flags: (0x00)
LinkMode: userspace controlled (1)
OperState: up (6)
> RTNL: Error (0x02) len 20 201.670341
Flags: 0 (0x000)
Sequence number: 11 (0x0000000b)
Port ID: 226
ACK: 0
> Event: New Station (0x13) len 60 205.579638
Interface Index: 4 (0x00000004)
MAC Address 02:E1:C4:A9:29:7D
Generation: 0 (0x00000000)
Station Info: len 0
Information Elements: len 22
RSN:
Group Data Cipher Suite: len 4
CCMP (00:0f:ac) suite 04
Pairwise Cipher Suite: len 4
CCMP (00:0f:ac) suite 04
AKM Suite: len 4
PSK; RSNA PSK (00:0f:ac) suite 02
RSN capabilities: bits 2 - 3: 16 replay counters per PTKSA
RSN capabilities: bits 4 - 5: 1 replay counter per GTKSA
01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ................
ac 02 0c 00 ....
< Request: Set Station (0x12) len 32 [ack] 205.580500
Interface Index: 4 (0x00000004)
MAC Address 02:E1:C4:A9:29:7D
Station Flags 2: len 8
Mask: 0x00000002
Authorized
Set: 0x00000000
< PAE: len 121 205.581146
Interface Index: 4
EAPoL: len 121
Protocol Version: 2 (802.1X-2004)
Type: 3 (Key)
Length: 117
Descriptor Type: 2
Key MIC: false
Secure: false
Error: false
Request: false
Encrypted Key Data: false
SMK Message: false
Key Descriptor Version: 2 (02)
Key Type: true
Install: false
Key ACK: true
Key Length: 16
Key Replay Counter: 1
Key NONCE
e6 b3 21 b0 b1 5b ff 21 c9 4c a8 74 6e fb 1f 57 ..!..[.!.L.tn..W
15 e2 d0 99 28 fd 09 79 6f 77 4c 27 fb 3c 87 3e ....(..yowL'.<.>
Key IV
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key RSC
00 00 00 00 00 00 00 00 ........
Key MIC Data
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key Data: len 22
Vendor specific: len 20
IEEE 802.11 (00:0f:ac) type: 04
PMKID KDE
00 0f ac 04 08 3e b6 ad f8 c0 8f d5 00 e9 de cf .....>..........
94 76 95 66 .v.f
02 03 00 75 02 00 8a 00 10 00 00 00 00 00 00 00 ...u............
01 e6 b3 21 b0 b1 5b ff 21 c9 4c a8 74 6e fb 1f ...!..[.!.L.tn..
57 15 e2 d0 99 28 fd 09 79 6f 77 4c 27 fb 3c 87 W....(..yowL'.<.
3e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >...............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 16 dd 14 00 0f ac 04 08 3e b6 ad f8 c0 8f ..........>.....
d5 00 e9 de cf 94 76 95 66 ......v.f
> Response: Set Station (0x12) len 4 205.580567
Status: Success (0)
< Request: Get Key (0x09) len 16 [ack] 205.580641
Interface Index: 4 (0x00000004)
Key Index: 1 (0x01)
> Result: New Key (0x0b) len 52 205.580690
Interface Index: 4 (0x00000004)
Key Index: 1 (0x01)
Key Data: len 0
Key Cipher: unknown (00:00:00) suite 01 (unknown)
Key: len 20
04 00 01 00 08 00 03 00 01 00 00 00 05 00 02 00 ................
01 00 00 00 ....
> Response: Get Key (0x09) len 4 205.580709
Status: Success (0)
> RTNL: New Link (0x10) len 52 205.589016
Flags: 0 (0x000)
Sequence number: 0 (0x00000000)
Port ID: 0
IFLA Family: Unknown
IFLA Type: 1
IFLA Index: 4
IFLA ChangeMask: 0
IFLA Flags: (0x1043) [up,broadcast,running,multicast]
IfName (len:6): wlan0
Wireless: len 20
14 00 03 8c 01 00 02 e1 c4 a9 29 7d 00 00 00 00 ..........)}....
00 00 00 00 ....
< PAE: len 121 205.688753
Interface Index: 4
EAPoL: len 121
Protocol Version: 2 (802.1X-2004)
Type: 3 (Key)
Length: 117
Descriptor Type: 2
Key MIC: false
Secure: false
Error: false
Request: false
Encrypted Key Data: false
SMK Message: false
Key Descriptor Version: 2 (02)
Key Type: true
Install: false
Key ACK: true
Key Length: 16
Key Replay Counter: 2
Key NONCE
36 b3 bc cc 54 15 6c 2f 98 8d a8 99 c7 57 39 62 6...T.l/.....W9b
92 9b 06 4f cc de 77 a4 5f e0 1a 36 57 b4 8b c3 ...O..w._..6W...
Key IV
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key RSC
00 00 00 00 00 00 00 00 ........
Key MIC Data
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key Data: len 22
Vendor specific: len 20
IEEE 802.11 (00:0f:ac) type: 04
PMKID KDE
00 0f ac 04 08 3e b6 ad f8 c0 8f d5 00 e9 de cf .....>..........
94 76 95 66 .v.f
02 03 00 75 02 00 8a 00 10 00 00 00 00 00 00 00 ...u............
02 36 b3 bc cc 54 15 6c 2f 98 8d a8 99 c7 57 39 .6...T.l/.....W9
62 92 9b 06 4f cc de 77 a4 5f e0 1a 36 57 b4 8b b...O..w._..6W..
c3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 16 dd 14 00 0f ac 04 08 3e b6 ad f8 c0 8f ..........>.....
d5 00 e9 de cf 94 76 95 66 ......v.f
> PAE: len 121 205.696233
Interface Index: 4
EAPoL: len 121
Protocol Version: 2 (802.1X-2004)
Type: 3 (Key)
Length: 117
Descriptor Type: 2
Key MIC: true
Secure: false
Error: false
Request: false
Encrypted Key Data: false
SMK Message: false
Key Descriptor Version: 2 (02)
Key Type: true
Install: false
Key ACK: false
Key Length: 16
Key Replay Counter: 2
Key NONCE
ef 54 14 38 55 86 53 ac 1e 58 ec 2d 40 4d 98 51 .T.8U.S..X.-@M.Q
16 e5 94 7b a0 79 ed c9 4d 4f 8a 73 e0 26 2a 03 ...{.y..MO.s.&*.
Key IV
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key RSC
00 00 00 00 00 00 00 00 ........
Key MIC Data
03 93 79 90 45 62 db 0e 91 6b 66 54 35 7d c0 3b ..y.Eb...kfT5}.;
Key Data: len 22
RSN:
Group Data Cipher Suite: len 4
CCMP (00:0f:ac) suite 04
Pairwise Cipher Suite: len 4
CCMP (00:0f:ac) suite 04
AKM Suite: len 4
PSK; RSNA PSK (00:0f:ac) suite 02
RSN capabilities: bits 2 - 3: 16 replay counters per PTKSA
RSN capabilities: bits 4 - 5: 1 replay counter per GTKSA
01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ................
ac 02 0c 00 ....
02 03 00 75 02 01 0a 00 10 00 00 00 00 00 00 00 ...u............
02 ef 54 14 38 55 86 53 ac 1e 58 ec 2d 40 4d 98 ..T.8U.S..X.-@M.
51 16 e5 94 7b a0 79 ed c9 4d 4f 8a 73 e0 26 2a Q...{.y..MO.s.&*
03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 03 93 79 90 45 62 db 0e 91 6b 66 54 35 7d c0 ...y.Eb...kfT5}.
3b 00 16 30 14 01 00 00 0f ac 04 01 00 00 0f ac ;..0............
04 01 00 00 0f ac 02 0c 00 .........
< PAE: len 155 205.702173
Interface Index: 4
EAPoL: len 155
Protocol Version: 2 (802.1X-2004)
Type: 3 (Key)
Length: 151
Descriptor Type: 2
Key MIC: true
Secure: true
Error: false
Request: false
Encrypted Key Data: true
SMK Message: false
Key Descriptor Version: 2 (02)
Key Type: true
Install: true
Key ACK: true
Key Length: 16
Key Replay Counter: 3
Key NONCE
36 b3 bc cc 54 15 6c 2f 98 8d a8 99 c7 57 39 62 6...T.l/.....W9b
92 9b 06 4f cc de 77 a4 5f e0 1a 36 57 b4 8b c3 ...O..w._..6W...
Key IV
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key RSC
00 00 00 00 00 00 00 00 ........
Key MIC Data
e7 5d 58 a2 f0 2f ae f0 9a 25 0c 05 e7 84 0d 37 .]X../...%.....7
Key Data: len 56
da 96 d0 3a 2f 12 cc 1a a5 21 13 a5 a1 c5 41 65 ...:/....!....Ae
10 ea 65 f8 28 9c b0 d4 32 38 46 29 bc e0 e0 1a ..e.(...28F)....
90 50 81 00 4d 83 ec 14 9f 76 0b cf 86 22 3a db .P..M....v...":.
58 b4 2d 24 e8 38 1e 40 X.-$.8.@
02 03 00 97 02 13 ca 00 10 00 00 00 00 00 00 00 ................
03 36 b3 bc cc 54 15 6c 2f 98 8d a8 99 c7 57 39 .6...T.l/.....W9
62 92 9b 06 4f cc de 77 a4 5f e0 1a 36 57 b4 8b b...O..w._..6W..
c3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 e7 5d 58 a2 f0 2f ae f0 9a 25 0c 05 e7 84 0d ..]X../...%.....
37 00 38 da 96 d0 3a 2f 12 cc 1a a5 21 13 a5 a1 7.8...:/....!...
c5 41 65 10 ea 65 f8 28 9c b0 d4 32 38 46 29 bc .Ae..e.(...28F).
e0 e0 1a 90 50 81 00 4d 83 ec 14 9f 76 0b cf 86 ....P..M....v...
22 3a db 58 b4 2d 24 e8 38 1e 40 ":.X.-$.8.@
> PAE: len 99 205.707596
Interface Index: 4
EAPoL: len 99
Protocol Version: 2 (802.1X-2004)
Type: 3 (Key)
Length: 95
Descriptor Type: 2
Key MIC: true
Secure: true
Error: false
Request: false
Encrypted Key Data: false
SMK Message: false
Key Descriptor Version: 2 (02)
Key Type: true
Install: false
Key ACK: false
Key Length: 16
Key Replay Counter: 3
Key NONCE
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key IV
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Key RSC
00 00 00 00 00 00 00 00 ........
Key MIC Data
79 48 ad d8 50 56 e6 a2 9e 6e cd e4 8b 6b 5e 41 yH..PV...n...k^A
Key Data: len 0
02 03 00 5f 02 03 0a 00 10 00 00 00 00 00 00 00 ..._............
03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 79 48 ad d8 50 56 e6 a2 9e 6e cd e4 8b 6b 5e .yH..PV...n...k^
41 00 00 A..
< Request: New Key (0x0b) len 56 [ack] 205.713745
Key Data: len 16
2a 96 fc a0 37 e3 d4 2a 79 98 89 eb 86 a6 eb f3 *...7..*y.......
Key Cipher: CCMP (00:0f:ac) suite 04
MAC Address 02:E1:C4:A9:29:7D
Key Index: 0 (0x00)
Interface Index: 4 (0x00000004)
> Response: New Key (0x0b) len 4 205.716318
Status: Success (0)
< Request: Set Station (0x12) len 32 [ack] 205.716407
Interface Index: 4 (0x00000004)
MAC Address 02:E1:C4:A9:29:7D
Station Flags 2: len 8
Mask: 0x00000002
Authorized
Set: 0x00000002
Authorized
> Response: Set Station (0x12) len 4 205.717435
Status: Success (0)
< RTNL: Set Link (0x13) len 32 [request,ack] 205.717562
Flags: 5 (0x005)
Sequence number: 12 (0x0000000c)
Port ID: 226
IFLA Family: Unknown
IFLA Type: 0
IFLA Index: 4
IFLA ChangeMask: 0
IFLA Flags: (0x00)
LinkMode: userspace controlled (1)
OperState: up (6)
> RTNL: Error (0x02) len 20 205.717589
Flags: 0 (0x000)
Sequence number: 12 (0x0000000c)
Port ID: 226
ACK: 0
> Event: Frame (0x3b) len 288 236.933316
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
RX Signal dBm: -4900
Frame: len 230
Frame Type: 0x0040
Type: Management (0)
Subtype: Probe request (4)
40 00 00 00 ff ff ff ff ff ff dc a6 32 22 5f ac @...........2"_.
ff ff ff ff ff ff 40 ca 00 00 01 04 02 04 0b 16 ......@.........
32 08 0c 12 18 24 30 48 60 6c 03 01 04 2d 1a 63 2....$0H`l...-.c
10 17 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 7f 08 01 00 08 00 00 ................
00 00 40 dd 69 00 50 f2 04 10 4a 00 01 10 10 3a ..@.i.P...J....:
00 01 00 10 08 00 02 31 48 10 47 00 10 7c f5 00 .......1H.G..|..
36 ce 40 50 4d 9d fe 2b a3 39 04 32 2b 10 54 00 6.@PM..+.9.2+.T.
08 00 00 00 00 00 00 00 00 10 3c 00 01 03 10 02 ..........<.....
00 02 00 00 10 09 00 02 00 00 10 12 00 02 00 00 ................
10 21 00 01 20 10 23 00 01 20 10 24 00 01 20 10 .!.. .#.. .$.. .
11 00 01 20 10 49 00 06 00 37 2a 00 01 20 dd 11 ... .I...7*.. ..
50 6f 9a 09 02 02 00 25 00 06 05 00 44 45 04 51 Po.....%....DE.Q
06 dd 08 00 50 f2 08 00 11 00 ce dd 09 00 10 18 ....P...........
02 00 00 10 00 00 ......
RX Management Flags: 1 (0x00000001)
> Event: Frame (0x3b) len 288 236.953556
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
RX Signal dBm: -4900
Frame: len 230
Frame Type: 0x0040
Type: Management (0)
Subtype: Probe request (4)
40 00 00 00 ff ff ff ff ff ff dc a6 32 22 5f ac @...........2"_.
ff ff ff ff ff ff 50 ca 00 00 01 04 02 04 0b 16 ......P.........
32 08 0c 12 18 24 30 48 60 6c 03 01 04 2d 1a 63 2....$0H`l...-.c
10 17 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 7f 08 01 00 08 00 00 ................
00 00 40 dd 69 00 50 f2 04 10 4a 00 01 10 10 3a ..@.i.P...J....:
00 01 00 10 08 00 02 31 48 10 47 00 10 7c f5 00 .......1H.G..|..
36 ce 40 50 4d 9d fe 2b a3 39 04 32 2b 10 54 00 6.@PM..+.9.2+.T.
08 00 00 00 00 00 00 00 00 10 3c 00 01 03 10 02 ..........<.....
00 02 00 00 10 09 00 02 00 00 10 12 00 02 00 00 ................
10 21 00 01 20 10 23 00 01 20 10 24 00 01 20 10 .!.. .#.. .$.. .
11 00 01 20 10 49 00 06 00 37 2a 00 01 20 dd 11 ... .I...7*.. ..
50 6f 9a 09 02 02 00 25 00 06 05 00 44 45 04 51 Po.....%....DE.Q
06 dd 08 00 50 f2 08 00 11 00 ce dd 09 00 10 18 ....P...........
02 00 00 10 00 00 ......
RX Management Flags: 1 (0x00000001)
> Event: Frame (0x3b) len 288 236.976242
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
RX Signal dBm: -4400
Frame: len 230
Frame Type: 0x0040
Type: Management (0)
Subtype: Probe request (4)
40 00 00 00 ff ff ff ff ff ff dc a6 32 22 5f ac @...........2"_.
ff ff ff ff ff ff 60 ca 00 00 01 04 02 04 0b 16 ......`.........
32 08 0c 12 18 24 30 48 60 6c 03 01 05 2d 1a 63 2....$0H`l...-.c
10 17 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 7f 08 01 00 08 00 00 ................
00 00 40 dd 69 00 50 f2 04 10 4a 00 01 10 10 3a ..@.i.P...J....:
00 01 00 10 08 00 02 31 48 10 47 00 10 7c f5 00 .......1H.G..|..
36 ce 40 50 4d 9d fe 2b a3 39 04 32 2b 10 54 00 6.@PM..+.9.2+.T.
08 00 00 00 00 00 00 00 00 10 3c 00 01 03 10 02 ..........<.....
00 02 00 00 10 09 00 02 00 00 10 12 00 02 00 00 ................
10 21 00 01 20 10 23 00 01 20 10 24 00 01 20 10 .!.. .#.. .$.. .
11 00 01 20 10 49 00 06 00 37 2a 00 01 20 dd 11 ... .I...7*.. ..
50 6f 9a 09 02 02 00 25 00 06 05 00 44 45 04 51 Po.....%....DE.Q
06 dd 08 00 50 f2 08 00 11 00 ce dd 09 00 10 18 ....P...........
02 00 00 10 00 00 ......
RX Management Flags: 1 (0x00000001)
> Event: Frame (0x3b) len 288 236.996832
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
RX Signal dBm: -4400
Frame: len 230
Frame Type: 0x0040
Type: Management (0)
Subtype: Probe request (4)
40 00 00 00 ff ff ff ff ff ff dc a6 32 22 5f ac @...........2"_.
ff ff ff ff ff ff 70 ca 00 00 01 04 02 04 0b 16 ......p.........
32 08 0c 12 18 24 30 48 60 6c 03 01 05 2d 1a 63 2....$0H`l...-.c
10 17 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 7f 08 01 00 08 00 00 ................
00 00 40 dd 69 00 50 f2 04 10 4a 00 01 10 10 3a ..@.i.P...J....:
00 01 00 10 08 00 02 31 48 10 47 00 10 7c f5 00 .......1H.G..|..
36 ce 40 50 4d 9d fe 2b a3 39 04 32 2b 10 54 00 6.@PM..+.9.2+.T.
08 00 00 00 00 00 00 00 00 10 3c 00 01 03 10 02 ..........<.....
00 02 00 00 10 09 00 02 00 00 10 12 00 02 00 00 ................
10 21 00 01 20 10 23 00 01 20 10 24 00 01 20 10 .!.. .#.. .$.. .
11 00 01 20 10 49 00 06 00 37 2a 00 01 20 dd 11 ... .I...7*.. ..
50 6f 9a 09 02 02 00 25 00 06 05 00 44 45 04 51 Po.....%....DE.Q
06 dd 08 00 50 f2 08 00 11 00 ce dd 09 00 10 18 ....P...........
02 00 00 10 00 00 ......
RX Management Flags: 1 (0x00000001)
> Event: Frame (0x3b) len 288 237.069295
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
RX Signal dBm: -4400
Frame: len 230
Frame Type: 0x0040
Type: Management (0)
Subtype: Probe request (4)
40 00 00 00 ff ff ff ff ff ff dc a6 32 22 5f ac @...........2"_.
ff ff ff ff ff ff a0 ca 00 00 01 04 02 04 0b 16 ................
32 08 0c 12 18 24 30 48 60 6c 03 01 06 2d 1a 63 2....$0H`l...-.c
10 17 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 7f 08 01 00 08 00 00 ................
00 00 40 dd 69 00 50 f2 04 10 4a 00 01 10 10 3a ..@.i.P...J....:
00 01 00 10 08 00 02 31 48 10 47 00 10 7c f5 00 .......1H.G..|..
36 ce 40 50 4d 9d fe 2b a3 39 04 32 2b 10 54 00 6.@PM..+.9.2+.T.
08 00 00 00 00 00 00 00 00 10 3c 00 01 03 10 02 ..........<.....
00 02 00 00 10 09 00 02 00 00 10 12 00 02 00 00 ................
10 21 00 01 20 10 23 00 01 20 10 24 00 01 20 10 .!.. .#.. .$.. .
11 00 01 20 10 49 00 06 00 37 2a 00 01 20 dd 11 ... .I...7*.. ..
50 6f 9a 09 02 02 00 25 00 06 05 00 44 45 04 51 Po.....%....DE.Q
06 dd 08 00 50 f2 08 00 11 00 ce dd 09 00 10 18 ....P...........
02 00 00 10 00 00 ......
RX Management Flags: 1 (0x00000001)
< Request: Frame (0x3b) len 224 [ack] 237.069801
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
Offchannel TX OK: true
Frame: len 193
Frame Type: 0x0050
Type: Management (0)
Subtype: Probe response (5)
50 00 00 00 dc a6 32 22 5f ac 84 25 3f 9f c2 54 P.....2"_..%?..T
84 25 3f 9f c2 54 00 00 00 00 00 00 00 00 00 00 .%?..T..........
64 00 11 00 00 10 4c 65 69 63 61 4d 31 30 2d 35 d.....LeicaM10-5
35 38 37 31 31 31 01 03 82 0b 16 03 01 06 30 14 587111........0.
01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ................
ac 02 00 00 dd 6b 00 50 f2 04 10 4a 00 01 10 10 .....k.P...J....
44 00 01 02 10 3b 00 01 03 10 47 00 10 ff 91 f1 D....;....G.....
a0 64 ad 53 9b a2 a2 49 bf 3e 5d 89 ce 10 21 00 .d.S...I.>]...!.
01 20 10 23 00 01 20 10 24 00 01 20 10 42 00 01 . .#.. .$.. .B..
20 10 54 00 08 00 01 00 37 2a 04 00 01 10 11 00 .T.....7*......
10 4c 65 69 63 61 4d 31 30 2d 35 35 38 37 31 31 .LeicaM10-558711
31 10 08 00 02 00 80 10 49 00 06 00 37 2a 00 01 1.......I...7*..
20
> Event: Frame TX Status (0x3c) len 240 237.069889
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Frame: len 193
Frame Type: 0x0050
Type: Management (0)
Subtype: Probe response (5)
50 00 00 00 dc a6 32 22 5f ac 84 25 3f 9f c2 54 P.....2"_..%?..T
84 25 3f 9f c2 54 00 00 00 00 00 00 00 00 00 00 .%?..T..........
64 00 11 00 00 10 4c 65 69 63 61 4d 31 30 2d 35 d.....LeicaM10-5
35 38 37 31 31 31 01 03 82 0b 16 03 01 06 30 14 587111........0.
01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ................
ac 02 00 00 dd 6b 00 50 f2 04 10 4a 00 01 10 10 .....k.P...J....
44 00 01 02 10 3b 00 01 03 10 47 00 10 ff 91 f1 D....;....G.....
a0 64 ad 53 9b a2 a2 49 bf 3e 5d 89 ce 10 21 00 .d.S...I.>]...!.
01 20 10 23 00 01 20 10 24 00 01 20 10 42 00 01 . .#.. .$.. .B..
20 10 54 00 08 00 01 00 37 2a 04 00 01 10 11 00 .T.....7*......
10 4c 65 69 63 61 4d 31 30 2d 35 35 38 37 31 31 .LeicaM10-558711
31 10 08 00 02 00 80 10 49 00 06 00 37 2a 00 01 1.......I...7*..
20
Cookie: 2267659240 (0x000000008729bbe8)
> Result: Frame (0x3b) len 12 237.069911
Cookie: 2267659240 (0x000000008729bbe8)
> Response: Frame (0x3b) len 4 237.069929
Status: Success (0)
< Request: Frame Wait Cancel (0x43) len 24 [ack] 237.070247
Wireless Device: 3 (0x0000000000000003)
Cookie: 2267659240 (0x000000008729bbe8)
> Response: Frame Wait Cancel (0x43) len 4 237.070289
Status: Success (0)
> Event: Frame (0x3b) len 288 237.089704
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
RX Signal dBm: -4400
Frame: len 230
Frame Type: 0x0040
Type: Management (0)
Subtype: Probe request (4)
40 00 00 00 ff ff ff ff ff ff dc a6 32 22 5f ac @...........2"_.
ff ff ff ff ff ff b0 ca 00 00 01 04 02 04 0b 16 ................
32 08 0c 12 18 24 30 48 60 6c 03 01 06 2d 1a 63 2....$0H`l...-.c
10 17 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 7f 08 01 00 08 00 00 ................
00 00 40 dd 69 00 50 f2 04 10 4a 00 01 10 10 3a ..@.i.P...J....:
00 01 00 10 08 00 02 31 48 10 47 00 10 7c f5 00 .......1H.G..|..
36 ce 40 50 4d 9d fe 2b a3 39 04 32 2b 10 54 00 6.@PM..+.9.2+.T.
08 00 00 00 00 00 00 00 00 10 3c 00 01 03 10 02 ..........<.....
00 02 00 00 10 09 00 02 00 00 10 12 00 02 00 00 ................
10 21 00 01 20 10 23 00 01 20 10 24 00 01 20 10 .!.. .#.. .$.. .
11 00 01 20 10 49 00 06 00 37 2a 00 01 20 dd 11 ... .I...7*.. ..
50 6f 9a 09 02 02 00 25 00 06 05 00 44 45 04 51 Po.....%....DE.Q
06 dd 08 00 50 f2 08 00 11 00 ce dd 09 00 10 18 ....P...........
02 00 00 10 00 00 ......
RX Management Flags: 1 (0x00000001)
< Request: Frame (0x3b) len 224 [ack] 237.090179
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
Offchannel TX OK: true
Frame: len 193
Frame Type: 0x0050
Type: Management (0)
Subtype: Probe response (5)
50 00 00 00 dc a6 32 22 5f ac 84 25 3f 9f c2 54 P.....2"_..%?..T
84 25 3f 9f c2 54 00 00 00 00 00 00 00 00 00 00 .%?..T..........
64 00 11 00 00 10 4c 65 69 63 61 4d 31 30 2d 35 d.....LeicaM10-5
35 38 37 31 31 31 01 03 82 0b 16 03 01 06 30 14 587111........0.
01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ................
ac 02 00 00 dd 6b 00 50 f2 04 10 4a 00 01 10 10 .....k.P...J....
44 00 01 02 10 3b 00 01 03 10 47 00 10 ff 91 f1 D....;....G.....
a0 64 ad 53 9b a2 a2 49 bf 3e 5d 89 ce 10 21 00 .d.S...I.>]...!.
01 20 10 23 00 01 20 10 24 00 01 20 10 42 00 01 . .#.. .$.. .B..
20 10 54 00 08 00 01 00 37 2a 04 00 01 10 11 00 .T.....7*......
10 4c 65 69 63 61 4d 31 30 2d 35 35 38 37 31 31 .LeicaM10-558711
31 10 08 00 02 00 80 10 49 00 06 00 37 2a 00 01 1.......I...7*..
20
> Event: Frame TX Status (0x3c) len 240 237.090241
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Frame: len 193
Frame Type: 0x0050
Type: Management (0)
Subtype: Probe response (5)
50 00 00 00 dc a6 32 22 5f ac 84 25 3f 9f c2 54 P.....2"_..%?..T
84 25 3f 9f c2 54 00 00 00 00 00 00 00 00 00 00 .%?..T..........
64 00 11 00 00 10 4c 65 69 63 61 4d 31 30 2d 35 d.....LeicaM10-5
35 38 37 31 31 31 01 03 82 0b 16 03 01 06 30 14 587111........0.
01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ................
ac 02 00 00 dd 6b 00 50 f2 04 10 4a 00 01 10 10 .....k.P...J....
44 00 01 02 10 3b 00 01 03 10 47 00 10 ff 91 f1 D....;....G.....
a0 64 ad 53 9b a2 a2 49 bf 3e 5d 89 ce 10 21 00 .d.S...I.>]...!.
01 20 10 23 00 01 20 10 24 00 01 20 10 42 00 01 . .#.. .$.. .B..
20 10 54 00 08 00 01 00 37 2a 04 00 01 10 11 00 .T.....7*......
10 4c 65 69 63 61 4d 31 30 2d 35 35 38 37 31 31 .LeicaM10-558711
31 10 08 00 02 00 80 10 49 00 06 00 37 2a 00 01 1.......I...7*..
20
Cookie: 2267659240 (0x000000008729bbe8)
> Result: Frame (0x3b) len 12 237.090263
Cookie: 2267659240 (0x000000008729bbe8)
> Response: Frame (0x3b) len 4 237.090281
Status: Success (0)
< Request: Frame Wait Cancel (0x43) len 24 [ack] 237.090531
Wireless Device: 3 (0x0000000000000003)
Cookie: 2267659240 (0x000000008729bbe8)
> Response: Frame Wait Cancel (0x43) len 4 237.090569
Status: Success (0)
> Event: Frame (0x3b) len 288 237.111619
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
RX Signal dBm: -4600
Frame: len 230
Frame Type: 0x0040
Type: Management (0)
Subtype: Probe request (4)
40 00 00 00 ff ff ff ff ff ff dc a6 32 22 5f ac @...........2"_.
ff ff ff ff ff ff c0 ca 00 00 01 04 02 04 0b 16 ................
32 08 0c 12 18 24 30 48 60 6c 03 01 07 2d 1a 63 2....$0H`l...-.c
10 17 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 7f 08 01 00 08 00 00 ................
00 00 40 dd 69 00 50 f2 04 10 4a 00 01 10 10 3a ..@.i.P...J....:
00 01 00 10 08 00 02 31 48 10 47 00 10 7c f5 00 .......1H.G..|..
36 ce 40 50 4d 9d fe 2b a3 39 04 32 2b 10 54 00 6.@PM..+.9.2+.T.
08 00 00 00 00 00 00 00 00 10 3c 00 01 03 10 02 ..........<.....
00 02 00 00 10 09 00 02 00 00 10 12 00 02 00 00 ................
10 21 00 01 20 10 23 00 01 20 10 24 00 01 20 10 .!.. .#.. .$.. .
11 00 01 20 10 49 00 06 00 37 2a 00 01 20 dd 11 ... .I...7*.. ..
50 6f 9a 09 02 02 00 25 00 06 05 00 44 45 04 51 Po.....%....DE.Q
06 dd 08 00 50 f2 08 00 11 00 ce dd 09 00 10 18 ....P...........
02 00 00 10 00 00 ......
RX Management Flags: 1 (0x00000001)
> Event: Frame (0x3b) len 288 237.133041
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
RX Signal dBm: -4500
Frame: len 230
Frame Type: 0x0040
Type: Management (0)
Subtype: Probe request (4)
40 00 00 00 ff ff ff ff ff ff dc a6 32 22 5f ac @...........2"_.
ff ff ff ff ff ff d0 ca 00 00 01 04 02 04 0b 16 ................
32 08 0c 12 18 24 30 48 60 6c 03 01 07 2d 1a 63 2....$0H`l...-.c
10 17 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 7f 08 01 00 08 00 00 ................
00 00 40 dd 69 00 50 f2 04 10 4a 00 01 10 10 3a ..@.i.P...J....:
00 01 00 10 08 00 02 31 48 10 47 00 10 7c f5 00 .......1H.G..|..
36 ce 40 50 4d 9d fe 2b a3 39 04 32 2b 10 54 00 6.@PM..+.9.2+.T.
08 00 00 00 00 00 00 00 00 10 3c 00 01 03 10 02 ..........<.....
00 02 00 00 10 09 00 02 00 00 10 12 00 02 00 00 ................
10 21 00 01 20 10 23 00 01 20 10 24 00 01 20 10 .!.. .#.. .$.. .
11 00 01 20 10 49 00 06 00 37 2a 00 01 20 dd 11 ... .I...7*.. ..
50 6f 9a 09 02 02 00 25 00 06 05 00 44 45 04 51 Po.....%....DE.Q
06 dd 08 00 50 f2 08 00 11 00 ce dd 09 00 10 18 ....P...........
02 00 00 10 00 00 ......
RX Management Flags: 1 (0x00000001)
> Event: Frame (0x3b) len 288 237.203777
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
RX Signal dBm: -5000
Frame: len 230
Frame Type: 0x0040
Type: Management (0)
Subtype: Probe request (4)
40 00 00 00 ff ff ff ff ff ff dc a6 32 22 5f ac @...........2"_.
ff ff ff ff ff ff 00 cb 00 00 01 04 02 04 0b 16 ................
32 08 0c 12 18 24 30 48 60 6c 03 01 08 2d 1a 63 2....$0H`l...-.c
10 17 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 7f 08 01 00 08 00 00 ................
00 00 40 dd 69 00 50 f2 04 10 4a 00 01 10 10 3a ..@.i.P...J....:
00 01 00 10 08 00 02 31 48 10 47 00 10 7c f5 00 .......1H.G..|..
36 ce 40 50 4d 9d fe 2b a3 39 04 32 2b 10 54 00 6.@PM..+.9.2+.T.
08 00 00 00 00 00 00 00 00 10 3c 00 01 03 10 02 ..........<.....
00 02 00 00 10 09 00 02 00 00 10 12 00 02 00 00 ................
10 21 00 01 20 10 23 00 01 20 10 24 00 01 20 10 .!.. .#.. .$.. .
11 00 01 20 10 49 00 06 00 37 2a 00 01 20 dd 11 ... .I...7*.. ..
50 6f 9a 09 02 02 00 25 00 06 05 00 44 45 04 51 Po.....%....DE.Q
06 dd 08 00 50 f2 08 00 11 00 ce dd 09 00 10 18 ....P...........
02 00 00 10 00 00 ......
RX Management Flags: 1 (0x00000001)
> Event: Frame (0x3b) len 288 237.222566
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
RX Signal dBm: -4900
Frame: len 230
Frame Type: 0x0040
Type: Management (0)
Subtype: Probe request (4)
40 00 00 00 ff ff ff ff ff ff dc a6 32 22 5f ac @...........2"_.
ff ff ff ff ff ff 10 cb 00 00 01 04 02 04 0b 16 ................
32 08 0c 12 18 24 30 48 60 6c 03 01 08 2d 1a 63 2....$0H`l...-.c
10 17 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 7f 08 01 00 08 00 00 ................
00 00 40 dd 69 00 50 f2 04 10 4a 00 01 10 10 3a ..@.i.P...J....:
00 01 00 10 08 00 02 31 48 10 47 00 10 7c f5 00 .......1H.G..|..
36 ce 40 50 4d 9d fe 2b a3 39 04 32 2b 10 54 00 6.@PM..+.9.2+.T.
08 00 00 00 00 00 00 00 00 10 3c 00 01 03 10 02 ..........<.....
00 02 00 00 10 09 00 02 00 00 10 12 00 02 00 00 ................
10 21 00 01 20 10 23 00 01 20 10 24 00 01 20 10 .!.. .#.. .$.. .
11 00 01 20 10 49 00 06 00 37 2a 00 01 20 dd 11 ... .I...7*.. ..
50 6f 9a 09 02 02 00 25 00 06 05 00 44 45 04 51 Po.....%....DE.Q
06 dd 08 00 50 f2 08 00 11 00 ce dd 09 00 10 18 ....P...........
02 00 00 10 00 00 ......
RX Management Flags: 1 (0x00000001)
> Event: Frame (0x3b) len 288 237.244269
Wiphy: 0 (0x00000000)
Interface Index: 4 (0x00000004)
Wireless Device: 3 (0x0000000000000003)
Wiphy Frequency: 2437 (0x00000985)
RX Signal dBm: -7000
Frame: len 230
Frame Type: 0x0040
Type: Management (0)
Subtype: Probe request (4)
40 00 00 00 ff ff ff ff ff ff dc a6 32 22 5f ac @...........2"_.
ff ff ff ff ff ff 20 cb 00 00 01 04 02 04 0b 16 ...... .........
32 08 0c 12 18 24 30 48 60 6c 03 01 09 2d 1a 63 2....$0H`l...-.c
10 17 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 7f 08 01 00 08 00 00 ................
00 00 40 dd 69 00 50 f2 04 10 4a 00 01 10 10 3a ..@.i.P...J....:
00 01 00 10 08 00 02 31 48 10 47 00 10 7c f5 00 .......1H.G..|..
36 ce 40 50 4d 9d fe 2b a3 39 04 32 2b 10 54 00 6.@PM..+.9.2+.T.
08 00 00 00 00 00 00 00 00 10 3c 00 01 03 10 02 ..........<.....
00 02 00 00 10 09 00 02 00 00 10 12 00 02 00 00 ................
10 21 00 01 20 10 23 00 01 20 10 24 00 01 20 10 .!.. .#.. .$.. .
11 00 01 20 10 49 00 06 00 37 2a 00 01 20 dd 11 ... .I...7*.. ..
50 6f 9a 09 02 02 00 25 00 06 05 00 44 45 04 51 Po.....%....DE.Q
06 dd 08 00 50 f2 08 00 11 00 ce dd 09 00 10 18 ....P...........
02 00 00 10 00 00 ......
RX Management Flags: 1 (0x00000001)
^A^C^C^Croot@leica:~#
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-10 17:38 ` Altous, Salahaldeen
@ 2021-08-10 18:24 ` James Prestwood
2021-08-11 21:28 ` salahaldeen.altous
0 siblings, 1 reply; 13+ messages in thread
From: James Prestwood @ 2021-08-10 18:24 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
Hi,
> >
> < Request: Get Station (0x11) len 8
> [ack,0x300]
>
> 58.821834
> Interface Index: 4 (0x00000004)
> > Result: New Station (0x13) len 32
> [multi]
>
> 58.821939
> Interface Index: 4 (0x00000004)
> MAC Address 84:25:3F:9F:C2:54
> Generation: 0 (0x00000000)
> Station Info: len 0
> > Complete: Get Station (0x11) len 4
> [multi]
>
> 58.822000
> Status: 0
>
>
> At this time 2 clients were connected to this AP (2x Event: New
> Station)
> attached you can find the whole log before connecting the 2 clients
Any way I could just get the whole log? I don't see the GET_STATION in
the attached file, nor the response... Just the Event: New Station at
the very beginning which appears to be due to a recent connection not
IWD issuing GET_STATION.
Thanks,
James
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-10 18:24 ` James Prestwood
@ 2021-08-11 21:28 ` salahaldeen.altous
2021-08-11 21:32 ` James Prestwood
0 siblings, 1 reply; 13+ messages in thread
From: salahaldeen.altous @ 2021-08-11 21:28 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
Hi James,
> Hi,
>
>
> Any way I could just get the whole log? I don't see the GET_STATION in
> the attached file, nor the response... Just the Event: New Station at
> the very beginning which appears to be due to a recent connection not
> IWD issuing GET_STATION.
>
> Thanks,
> James
Thanks again for your reply, I will try to connect and external USB-WiFi adapter to double check,
can you advice a reference adapter?
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: how to get info about connected clients when iwd runs in AP mode?
2021-08-11 21:28 ` salahaldeen.altous
@ 2021-08-11 21:32 ` James Prestwood
0 siblings, 0 replies; 13+ messages in thread
From: James Prestwood @ 2021-08-11 21:32 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
On Wed, 2021-08-11 at 21:28 +0000, salahaldeen.altous(a)leica-camera.com
wrote:
> Hi James,
> > Hi,
> >
> >
> > Any way I could just get the whole log? I don't see the GET_STATION
> > in
> > the attached file, nor the response... Just the Event: New Station
> > at
> > the very beginning which appears to be due to a recent connection
> > not
> > IWD issuing GET_STATION.
> >
> > Thanks,
> > James
> Thanks again for your reply, I will try to connect and external USB-
> WiFi adapter to double check,
> can you advice a reference adapter?
IWD should work on anything really. I've personally used some cheap
Ralink/Realtek adapters without any problem. I've found many USB
adpaters are from these two vendors unless you're specifically looking
for others.
> _______________________________________________
> iwd mailing list -- iwd(a)lists.01.org
> To unsubscribe send an email to iwd-leave(a)lists.01.org
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2021-08-11 21:32 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-06 6:30 how to get info about connected clients when iwd runs in AP mode? salahaldeen.altous
2021-08-06 16:32 ` James Prestwood
2021-08-09 7:22 ` Altous, Salahaldeen
2021-08-09 15:58 ` James Prestwood
2021-08-10 5:34 ` Altous, Salahaldeen
2021-08-10 8:22 ` salahaldeen.altous
2021-08-10 15:55 ` James Prestwood
2021-08-10 17:38 ` Altous, Salahaldeen
2021-08-10 18:24 ` James Prestwood
2021-08-11 21:28 ` salahaldeen.altous
2021-08-11 21:32 ` James Prestwood
2021-08-06 18:32 ` Denis Kenzior
2021-08-09 7:26 ` Altous, Salahaldeen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.