* broadcom fmac ap mode testing - how to set iwd as dhcp server?
@ 2021-01-29 1:23 KeithG
2021-01-29 1:37 ` James Prestwood
0 siblings, 1 reply; 7+ messages in thread
From: KeithG @ 2021-01-29 1:23 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 20007 bytes --]
Group,
I noticed that the latest patches posted for iwd appeared to addres the
broadcom fmac in ap mode. I compiled the latest from git and tried it out.
It will make a connection. Big improvement from before. This is a log of
the connection on my RPi running iwctl in ap mode. I am connecting from a
dell laptop.
# iwmon
Wireless monitor ver 1.11
Created interface nlmon
> Event: New Station (0x13) len 168
1611882622.696232
Interface Index: 3 (0x00000003)
MAC Address 60:F2:62:AE:70:FE
Generation: 9 (0x00000009)
Station Info: len 0
Information Elements: len 129
SSID: RuneAudioAP1
52 75 6e 65 41 75 64 69 6f 41 50 31 RuneAudioAP1
Supported rates:
1.0(B) 2.0(B) 5.5(B) 11.0(B) 6.0 9.0 12.0 18.0 Mbit/s
82 84 8b 96 0c 12 18 24 .......$
Tag 33: len 2
00 0f ..
Tag 36: len 50
24 01 28 01 2c 01 30 01 34 01 38 01 3c 01 40 01
$.(.,.0.4.8.<.(a).
64 01 68 01 6c 01 70 01 74 01 78 01 7c 01 80 01
d.h.l.p.t.x.|...
84 01 88 01 8c 01 90 01 95 01 99 01 9d 01 a1 01
................
a5 01 ..
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
01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f
................
ac 02 00 00 00 00 ......
Extended supported rates:
24.0 36.0 48.0 54.0 Mbit/s
30 48 60 6c 0H`l
RM Enabled Capabilities: len 5
Enabled: bit 1: Neighbor Report
Enabled: bit 4: Beacon Passive Measurement
Enabled: bit 5: Beacon Active Measurement
Enabled: bit 6: Beacon Table Measurement
Operating Channel Max Measurement Duration: 0
Non-Operating Channel Max Measurement Duration: 0
Measurement Pilot Capability: 0
72 00 00 00 00 r....
Extended yCapabilities: len 10
Capability: bit 2: Extended channel switching
Capability: bit 19: BSS transition
Capability: bit 22: Multiple BSSID
Capability: bit 23: Timing measurement
Capability: bit 31: Interworking
Capability: bit 32: QoS Map
Capability: bit 46: WNM- Notification
04 00 c8 80 01 40 00 00 00 00 .....@....
< Request: Set Station (0x12) len 32 [ack]
1611882622.696372
Interface Index: 3 (0x00000003)
MAC Address 60:F2:62:AE:70:FE
Station Flags 2: len 8
Mask: 0x00000002
Authorized
Set: 0x00000000
> Response: Set Station (0x12) len 4 [root]
1611882622.697255
Status: Success (0)
< Request: New Key (0x0b) len 48 [ack]
1611882622.697359
Interface Index: 3 (0x00000003)
Key: len 36
14 00 01 00 c4 79 49 79 56 8f 90 f3 d7 9a be 73 .....yIyV......s
8a ba 6e 6f 08 00 03 00 04 ac 0f 00 05 00 02 00 ..no............
01 00 00 00 ....
> Response: New Key (0x0b) len 4 [0x100]
1611882622.698943
Status: Success (0)
< Request: Set Key (0x0a) len 32 [ack]
1611882622.699011
Interface Index: 3 (0x00000003)
Key: len 20
05 00 02 00 01 00 00 00 04 00 05 00 08 00 08 80 ................
04 00 02 00 ....
> Response: Set Key (0x0a) len 4 [0x100]
1611882622.699725
Status: Success (0)
< Request: Get Key (0x09) len 16 [ack]
1611882622.699782
Interface Index: 3 (0x00000003)
Key Index: 1 (0x01)
> Result: New Key (0x0b) len 44
1611882622.700248
Interface Index: 3 (0x00000003)
Key Index: 1 (0x01)
Key Cipher: BIP (00:0f:ac) suite 06
Key: len 16
08 00 03 00 06 ac 0f 00 05 00 02 00 01 00 00 00 ................
< PAE: len 121
0.700570
Interface Index: 3
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
47 6e 2d 93 73 84 22 f1 1c 6a 5d 3d 95 e4 9b 74
Gn-.s."..j]=...t
5d f8 d5 48 06 7a e8 49 2e 44 98 98 59 c7 92 00
]..H.z.I.D..Y...
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 54 72 65 62 5c 4b e4 40 60 01 9c e8
....Treb\K.@`...
5f 33 0f 78 _3.x
02 03 00 75 02 00 8a 00 10 00 00 00 00 00 00 00 ...u............
01 47 6e 2d 93 73 84 22 f1 1c 6a 5d 3d 95 e4 9b .Gn-.s."..j]=...
74 5d f8 d5 48 06 7a e8 49 2e 44 98 98 59 c7 92 t]..H.z.I.D..Y..
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 16 dd 14 00 0f ac 04 54 72 65 62 5c 4b e4 .........Treb\K.
40 60 01 9c e8 5f 33 0f 78 @`..._3.x
> Response: Get Key (0x09) len 4 [0x100]
0.700267
Status: Success (0)
> PAE: len 123
0.707588
Interface Index: 3
EAPoL: len 123
Protocol Version: 1 (802.1X-2001)
Type: 3 (Key)
Length: 119
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: 1
Key NONCE
29 7a a9 c3 84 c6 ed 06 c0 00 75 68 57 3d 16 78
)z........uhW=.x
d4 3e 1e 62 1d 48 5d c6 01 da a0 8f 7f 16 b3 cd
.>.b.H].........
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
cf aa 34 82 65 28 93 a7 62 c2 0a b4 e0 d9 dd 59
..4.e(..b......Y
Key Data: len 24
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
01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f
................
ac 02 00 00 00 00 ......
01 03 00 77 02 01 0a 00 00 00 00 00 00 00 00 00 ...w............
01 29 7a a9 c3 84 c6 ed 06 c0 00 75 68 57 3d 16 .)z........uhW=.
78 d4 3e 1e 62 1d 48 5d c6 01 da a0 8f 7f 16 b3 x.>.b.H]........
cd 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 cf aa 34 82 65 28 93 a7 62 c2 0a b4 e0 d9 dd ...4.e(..b......
59 00 18 30 16 01 00 00 0f ac 04 01 00 00 0f ac Y..0............
04 01 00 00 0f ac 02 00 00 00 00 ...........
< PAE: len 155
0.708697
Interface Index: 3
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: 2
Key NONCE
47 6e 2d 93 73 84 22 f1 1c 6a 5d 3d 95 e4 9b 74
Gn-.s."..j]=...t
5d f8 d5 48 06 7a e8 49 2e 44 98 98 59 c7 92 00
]..H.z.I.D..Y...
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
6e b0 eb f8 83 f8 20 31 ad b8 96 df bf 7f 8f 75 n.....
1.......u
Key Data: len 56
cd d7 94 40 e2 7d 9e 63 dc f3 fa b1 3e f4 c7 3a
...@.}.c....>..:
ec 81 46 6a a9 ea 6e b3 ed 22 d7 81 f7 cf 60 fc
..Fj..n.."....`.
64 31 d2 9e 1b 44 da 7a 50 ff 05 aa 25 51 2f 8e
d1...D.zP...%Q/.
f5 d2 d4 96 b4 65 d3 41 .....e.A
02 03 00 97 02 13 ca 00 10 00 00 00 00 00 00 00 ................
02 47 6e 2d 93 73 84 22 f1 1c 6a 5d 3d 95 e4 9b .Gn-.s."..j]=...
74 5d f8 d5 48 06 7a e8 49 2e 44 98 98 59 c7 92 t]..H.z.I.D..Y..
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 6e b0 eb f8 83 f8 20 31 ad b8 96 df bf 7f 8f .n..... 1.......
75 00 38 cd d7 94 40 e2 7d 9e 63 dc f3 fa b1 3e u.8...(a).}.c....>
f4 c7 3a ec 81 46 6a a9 ea 6e b3 ed 22 d7 81 f7 ..:..Fj..n.."...
cf 60 fc 64 31 d2 9e 1b 44 da 7a 50 ff 05 aa 25 .`.d1...D.zP...%
51 2f 8e f5 d2 d4 96 b4 65 d3 41 Q/......e.A
> PAE: len 99
0.717237
Interface Index: 3
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: 2
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
58 61 8f 4a fb 79 4e a5 58 36 31 0e b7 71 c3 4f
Xa.J.yN.X61..q.O
Key Data: len 0
01 03 00 5f 02 03 0a 00 00 00 00 00 00 00 00 00 ..._............
02 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 58 61 8f 4a fb 79 4e a5 58 36 31 0e b7 71 c3 .Xa.J.yN.X61..q.
4f 00 00 O..
< Request: New Key (0x0b) len 56 [ack]
0.717527
Key Data: len 16
ab aa cd 37 2e ef 97 7f 15 f8 72 a5 90 2c c0 20 ...7......r..,.
Key Cipher: CCMP (00:0f:ac) suite 04
MAC Address 60:F2:62:AE:70:FE
Key Index: 0 (0x00)
Interface Index: 3 (0x00000003)
> Response: New Key (0x0b) len 4 [0x100]
0.718200
Status: Success (0)
< Request: Set Station (0x12) len 32 [ack]
0.718256
Interface Index: 3 (0x00000003)
MAC Address 60:F2:62:AE:70:FE
Station Flags 2: len 8
Mask: 0x00000002
Authorized
Set: 0x00000002
Authorized
> Response: Set Station (0x12) len 4 [root]
0.718608
Status: Success (0)
< RTNL: Set Link (0x13) len 32 [request,ack]
0.718663
Flags: 5 (0x005)
Sequence number: 8 (0x00000008)
Port ID: 81225
> RTNL: New Link (0x10) len 1308
0.718871
Flags: 0 (0x000)
Sequence number: 0 (0x00000000)
Port ID: 0
IFLA Family: Unknown
IFLA Type: 1
IFLA Index: 3
IFLA ChangeMask: 0
IFLA Flags: (0x1043) [up,broadcast,running,multicast]
IfName (len:6): wlan0
Txqlen: 1000 (0x000003e8)
OperState: up (6)
LinkMode: userspace controlled (1)
MTU: 1500 (0x000005dc)
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 1
Qdisc (len:9): fq_codel
Reserved: len 4
Reserved: len 1
Reserved: len 4
Reserved: len 4
Map: len 32
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
................
Interface Address: b8:27:eb:52:cc:d0
Broadcast Address: ff:ff:ff:ff:ff:ff
Reserved: len 192
Stats: len 96
7c 10 22 00 f1 7f 03 00 5a a1 b5 16 db b9 57 03
|.".....Z.....W.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
45 f2 1e 00 00 00 00 00 00 00 00 00 00 00 00 00
E...............
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
................
Reserved: len 8
Reserved: len 756
> RTNL: New Link (0x10) len 1308
0.718888
Flags: 0 (0x000)
Sequence number: 0 (0x00000000)
Port ID: 0
IFLA Family: Unknown
IFLA Type: 1
IFLA Index: 3
IFLA ChangeMask: 0
IFLA Flags: (0x1043) [up,broadcast,running,multicast]
IfName (len:6): wlan0
Txqlen: 1000 (0x000003e8)
OperState: up (6)
LinkMode: userspace controlled (1)
MTU: 1500 (0x000005dc)
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 1
Qdisc (len:9): fq_codel
Reserved: len 4
Reserved: len 1
Reserved: len 4
Reserved: len 4
Map: len 32
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
................
Interface Address: b8:27:eb:52:cc:d0
Broadcast Address: ff:ff:ff:ff:ff:ff
Reserved: len 192
Stats: len 96
7c 10 22 00 f1 7f 03 00 5a a1 b5 16 db b9 57 03
|.".....Z.....W.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
45 f2 1e 00 00 00 00 00 00 00 00 00 00 00 00 00
E...............
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
................
Reserved: len 8
Reserved: len 756
> RTNL: New Link (0x10) len 1308
0.718896
Flags: 0 (0x000)
Sequence number: 0 (0x00000000)
Port ID: 0
IFLA Family: Unknown
IFLA Type: 1
IFLA Index: 3
IFLA ChangeMask: 0
IFLA Flags: (0x1043) [up,broadcast,running,multicast]
IfName (len:6): wlan0
Txqlen: 1000 (0x000003e8)
OperState: up (6)
LinkMode: userspace controlled (1)
MTU: 1500 (0x000005dc)
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 4
Reserved: len 1
Qdisc (len:9): fq_codel
Reserved: len 4
Reserved: len 1
Reserved: len 4
Reserved: len 4
Map: len 32
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
................
Interface Address: b8:27:eb:52:cc:d0
Broadcast Address: ff:ff:ff:ff:ff:ff
Reserved: len 192
Stats: len 96
7c 10 22 00 f1 7f 03 00 5a a1 b5 16 db b9 57 03
|.".....Z.....W.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
45 f2 1e 00 00 00 00 00 00 00 00 00 00 00 00 00
E...............
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
................
Reserved: len 8
Reserved: len 756
> RTNL: Error (0x02) len 20 [0x100]
0.718926
Flags: 256 (0x100)
Sequence number: 8 (0x00000008)
Port ID: 81225
ACK: 0
Still gives an RTNL error but I do not kow what that means. And once
connected, I could not disconnect and reconnect without restarting the ap.
I would get an immediate dsiconnect and iwmon shows:
> Event: Del Station (0x14) len 32
474.439927
Interface Index: 3 (0x00000003)
MAC Address 60:F2:62:AE:70:FE
Generation: 0 (0x00000000)
Station Info: len 0
When I restart the AP from iwct, I can connect again.
What I do not yet know how to do, though, is assign an ip address to the ap
and then have it be a dhcp server to serve out a dhcp address to the
connecting computer. I found this online and took a stab, but it did not
assign an address, though the computer did 'attach'.
How do you set it up for iwd to be a dhcp server? If iwd cannot do it, can
I use dhcpd? dnsmasq? I have found very little info in my searches.
Thanks for this! It will help with adoption of iwd in the RPi community.
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 25189 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: broadcom fmac ap mode testing - how to set iwd as dhcp server?
2021-01-29 1:23 broadcom fmac ap mode testing - how to set iwd as dhcp server? KeithG
@ 2021-01-29 1:37 ` James Prestwood
2021-01-30 11:47 ` Paul Menzel
0 siblings, 1 reply; 7+ messages in thread
From: James Prestwood @ 2021-01-29 1:37 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]
Hi Keith,
<snip>
> When I restart the AP from iwct, I can connect again.
> What I do not yet know how to do, though, is assign an ip address to
> the ap and then have it be a dhcp server to serve out a dhcp address
> to the connecting computer. I found this online and took a stab, but
> it did not assign an address, though the computer did 'attach'.
Yes this is exactly the behavior we are seeing as well. I do have a
patch which fixes the disconnect issue and allows the same client to
connect again but we've actually got more problems than this. My recent
patches 'fixing' AP mode is somewhat of a hack in all honesty. It
allows the 4-way handshake to happen but not the GTK handshake. This
means no group traffic which breaks DHCP.
I won't bore you with details but it boils down to brcmfmac being (as
far as we can tell) broken when used this way. We are going to
investigate handshake offloading which might fix it, but we just don't
know yet. I am expecting offloading to work but if not we need to talk
with linux-wireless/broadcom about why its broken or how it supposed to
work. Anyways, we hope to have this sorted soon.
FYI even hostapd exibits this exact same behavior with brcmfmac cards,
does the 4-way but no GTK handshake. At least on my brcmfmac cards. I
would be curious if it does the same for you.
> How do you set it up for iwd to be a dhcp server? If iwd cannot do
> it, can I use dhcpd? dnsmasq? I have found very little info in my
> searches.
You're likely setting it up correctly (EnableNetworkConfiguration=true)
but we've got this GTK problem.
Thanks,
James
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 2179 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: broadcom fmac ap mode testing - how to set iwd as dhcp server?
2021-01-29 1:37 ` James Prestwood
@ 2021-01-30 11:47 ` Paul Menzel
2021-01-30 20:25 ` KeithG
0 siblings, 1 reply; 7+ messages in thread
From: Paul Menzel @ 2021-01-30 11:47 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
Dear James, Dear Keith,
Am 29.01.21 um 02:37 schrieb James Prestwood:
> <snip>
>> When I restart the AP from iwctl, I can connect again.
>> What I do not yet know how to do, though, is assign an ip address to
>> the ap and then have it be a dhcp server to serve out a dhcp address
>> to the connecting computer. I found this online and took a stab, but
>> it did not assign an address, though the computer did 'attach'.
>
> Yes this is exactly the behavior we are seeing as well. I do have a
> patch which fixes the disconnect issue and allows the same client to
> connect again but we've actually got more problems than this. My recent
> patches 'fixing' AP mode is somewhat of a hack in all honesty. It
> allows the 4-way handshake to happen but not the GTK handshake. This
> means no group traffic which breaks DHCP.
>
> I won't bore you with details but it boils down to brcmfmac being (as
> far as we can tell) broken when used this way.
Are the Linux kernel subsystem maintainers (BROADCOM BRCM80211
IEEE802.11n WIRELESS DRIVER) aware of this issue?
> We are going to investigate handshake offloading which might fix it,
> but we just don't know yet. I am expecting offloading to work but if
> not we need to talk with linux-wireless/broadcom about why its broken
> or how it supposed to work. Anyways, we hope to have this sorted
> soon.
[…]
Kind regards,
Paul
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: broadcom fmac ap mode testing - how to set iwd as dhcp server?
2021-01-30 11:47 ` Paul Menzel
@ 2021-01-30 20:25 ` KeithG
2021-01-31 15:44 ` KeithG
0 siblings, 1 reply; 7+ messages in thread
From: KeithG @ 2021-01-30 20:25 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]
it lives! This is the latest git built as
iwd-git-r5142.065f19b-1-aarch64.pkg.tar.xz on Arch running on a RPiB3+
I have not tried using the iwd network management, but when I use connman,
I can create a 'tether' interface and connect to it.
This starts it on 192.168.0.1
connmanctl tether wifi on myssid password
this stops it.
connmanctl tether wlan0 off
I'll try iwd alone next, but this is a great development for the
RaspberryPi community, IMO.
Thanks!
On Sat, Jan 30, 2021 at 5:47 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>
> Dear James, Dear Keith,
>
>
> Am 29.01.21 um 02:37 schrieb James Prestwood:
>
> > <snip>
> >> When I restart the AP from iwctl, I can connect again.
> >> What I do not yet know how to do, though, is assign an ip address to
> >> the ap and then have it be a dhcp server to serve out a dhcp address
> >> to the connecting computer. I found this online and took a stab, but
> >> it did not assign an address, though the computer did 'attach'.
> >
> > Yes this is exactly the behavior we are seeing as well. I do have a
> > patch which fixes the disconnect issue and allows the same client to
> > connect again but we've actually got more problems than this. My recent
> > patches 'fixing' AP mode is somewhat of a hack in all honesty. It
> > allows the 4-way handshake to happen but not the GTK handshake. This
> > means no group traffic which breaks DHCP.
> >
> > I won't bore you with details but it boils down to brcmfmac being (as
> > far as we can tell) broken when used this way.
>
> Are the Linux kernel subsystem maintainers (BROADCOM BRCM80211
> IEEE802.11n WIRELESS DRIVER) aware of this issue?
>
> > We are going to investigate handshake offloading which might fix it,
> > but we just don't know yet. I am expecting offloading to work but if
> > not we need to talk with linux-wireless/broadcom about why its broken
> > or how it supposed to work. Anyways, we hope to have this sorted
> > soon.
> […]
>
>
> Kind regards,
>
> Paul
>
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 2615 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: broadcom fmac ap mode testing - how to set iwd as dhcp server?
2021-01-30 20:25 ` KeithG
@ 2021-01-31 15:44 ` KeithG
2021-02-01 12:42 ` Andrew Zaborowski
0 siblings, 1 reply; 7+ messages in thread
From: KeithG @ 2021-01-31 15:44 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 3483 bytes --]
On Sat, Jan 30, 2021 at 2:25 PM KeithG <ys3al35l@gmail.com> wrote:
> it lives! This is the latest git built as
> iwd-git-r5142.065f19b-1-aarch64.pkg.tar.xz on Arch running on a RPiB3+
>
> I have not tried using the iwd network management, but when I use connman,
> I can create a 'tether' interface and connect to it.
> This starts it on 192.168.0.1
> connmanctl tether wifi on myssid password
> this stops it.
> connmanctl tether wlan0 off
>
> I'll try iwd alone next, but this is a great development for the
> RaspberryPi community, IMO.
>
> Thanks!
>
> On Sat, Jan 30, 2021 at 5:47 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>
>>
>> Dear James, Dear Keith,
>>
>>
>> Am 29.01.21 um 02:37 schrieb James Prestwood:
>>
>> > <snip>
>> >> When I restart the AP from iwctl, I can connect again.
>> >> What I do not yet know how to do, though, is assign an ip address to
>> >> the ap and then have it be a dhcp server to serve out a dhcp address
>> >> to the connecting computer. I found this online and took a stab, but
>> >> it did not assign an address, though the computer did 'attach'.
>> >
>> > Yes this is exactly the behavior we are seeing as well. I do have a
>> > patch which fixes the disconnect issue and allows the same client to
>> > connect again but we've actually got more problems than this. My recent
>> > patches 'fixing' AP mode is somewhat of a hack in all honesty. It
>> > allows the 4-way handshake to happen but not the GTK handshake. This
>> > means no group traffic which breaks DHCP.
>> >
>> > I won't bore you with details but it boils down to brcmfmac being (as
>> > far as we can tell) broken when used this way.
>>
>> Are the Linux kernel subsystem maintainers (BROADCOM BRCM80211
>> IEEE802.11n WIRELESS DRIVER) aware of this issue?
>>
>> > We are going to investigate handshake offloading which might fix it,
>> > but we just don't know yet. I am expecting offloading to work but if
>> > not we need to talk with linux-wireless/broadcom about why its broken
>> > or how it supposed to work. Anyways, we hope to have this sorted
>> > soon.
>> […]
>>
>>
>> Kind regards,
>>
>> Paul
>>
>
So, I finally tried running iwd in 'standalone' ap mode (no connman). It
still connects but even though I have this for my main.conf:
[General]
UseDefaultInterface=true
EnableNetworkConfiguration=true
It connects, but does not set up an IP address. the log shows this:
iwd[32171]: KEY_SEQ not returned in GET_KEY reply
the windows computer I have connected shows this:
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wireless-AC 9560 160MHz
Physical Address. . . . . . . . . : 60-F2-62-AE-70-FE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::dc8d:27f1:52c2:5b0f%10(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.91.15(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 90239586
DHCPv6 Client DUID. . . . . . . . :
00-01-00-01-25-7E-CD-22-34-48-ED-06-F5-9A
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Is there any more I can do to help?
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 4781 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: broadcom fmac ap mode testing - how to set iwd as dhcp server?
2021-01-31 15:44 ` KeithG
@ 2021-02-01 12:42 ` Andrew Zaborowski
2021-02-01 17:27 ` KeithG
0 siblings, 1 reply; 7+ messages in thread
From: Andrew Zaborowski @ 2021-02-01 12:42 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 388 bytes --]
Hi Keith,
On Sun, 31 Jan 2021 at 16:44, KeithG <ys3al35l@gmail.com> wrote:
> So, I finally tried running iwd in 'standalone' ap mode (no connman). It still connects but even though I have this for my main.conf:
> [General]
> UseDefaultInterface=true
> EnableNetworkConfiguration=true
If I'm not mistaken you're missing the APRanges= setting for server-side DHCP.
Best regards
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: broadcom fmac ap mode testing - how to set iwd as dhcp server?
2021-02-01 12:42 ` Andrew Zaborowski
@ 2021-02-01 17:27 ` KeithG
0 siblings, 0 replies; 7+ messages in thread
From: KeithG @ 2021-02-01 17:27 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]
On Mon, Feb 1, 2021 at 6:42 AM Andrew Zaborowski <
andrew.zaborowski@intel.com> wrote:
> Hi Keith,
>
> On Sun, 31 Jan 2021 at 16:44, KeithG <ys3al35l@gmail.com> wrote:
> > So, I finally tried running iwd in 'standalone' ap mode (no connman). It
> still connects but even though I have this for my main.conf:
> > [General]
> > UseDefaultInterface=true
> > EnableNetworkConfiguration=true
>
> If I'm not mistaken you're missing the APRanges= setting for server-side
> DHCP.
>
> Best regards
>
Andrew,
I got a pointer from James and posed this to him as well. He asked that I
pose this to the greater group.
If I change my /etc/iwd/main.conf to
[General]
UseDefaultInterface=true
EnableNetworkConfiguration=true
APRanges=192.168.5.0/24
I now get an IP address and can connect. Is there a way to make iwd scan
for SSIDs when connected this way? We are trying to set up an RPi so that
when powered, if it gets no IP address, it turns into an AP and allows a
connection to select an SSID to connect to. Currently, we are using connman
and dnsmasq/hostapd and that works. I have tried connman with its 'tether'
mode and though it creates a 'tether' interface, it does connect and
appears to scan at startup before it turns over the tether mode, but I have
no control over the IP address it advertised on and our current
instructions specify 192.168.5.1. I'd like to not change that. If I used
hostapd and dnsmasq, it does scan and I can see SSIDs as they appear.
Looking for a transparent way to move to iwd and/or connman from
hostapd/dnsmasq yet not change the instructions.
Thanks for the help!
Keith
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 2387 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2021-02-01 17:27 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-29 1:23 broadcom fmac ap mode testing - how to set iwd as dhcp server? KeithG
2021-01-29 1:37 ` James Prestwood
2021-01-30 11:47 ` Paul Menzel
2021-01-30 20:25 ` KeithG
2021-01-31 15:44 ` KeithG
2021-02-01 12:42 ` Andrew Zaborowski
2021-02-01 17:27 ` KeithG
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.