• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 40 subscribers
  • Views 269 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

WL127x Linux kernel 4.12 wireless AP problem connecting Windows 10 client with Intel AC-9260 Wi-Fi module.

Kim Weller
Prodigy 20 points
Other Parts Discussed in Thread: AM3352

Linux TiWi-BLE/WL1271L AP problem connecting from Windows 10 Wi-Fi client with Intel AC-9260 Wi-Fi module. Problem is related to wl127x single-role firmware. Switch to multi-role wl127x firmware resolved this problem.

Target

  • HW: TiWi-BLE/WL1271L connected to AM3352 processor using SDIO communications.
  • SW: Wind River Linux based on Linux kernel 4.12

Application

  • Linux/AM335x running wireless AP, hostapd, using TiWi-BLE/WL1271L
  • Windows 10 wireless client connecting to AP using AC-9260 Wi-Fi module

Wireshark 802.11 showing multiple re-associations during failed wireless connection attempt

Beacon packets

No.     Time           Source                Destination           Protocol Length Info
    172 12.147548047   TexasIns_52:be:99     Broadcast             802.11   240    Beacon frame, SN=2861, FN=0, Flags=........C, BI=100, SSID=Map-52BE99
    176 12.202886274   TexasIns_52:be:99     2a:9e:bd:62:75:9e     802.11   234    Probe Response, SN=890, FN=0, Flags=........C, BI=100, SSID=Map-52BE99
    181 12.212566587   TexasIns_52:be:99     2a:9e:bd:62:75:9e     802.11   234    Probe Response, SN=891, FN=0, Flags=........C, BI=100, SSID=Map-52BE99
    183 12.249945466   TexasIns_52:be:99     Broadcast             802.11   240    Beacon frame, SN=2862, FN=0, Flags=........C, BI=100, SSID=Map-52BE99

First Association packet

No.     Time           Source                Destination           Protocol Length Info
    260 15.654755760   82:5a:65:0a:e4:8d     TexasIns_52:be:99     802.11   52     Authentication, SN=352, FN=0, Flags=........C
    262 15.664360216   TexasIns_52:be:99     82:5a:65:0a:e4:8d     802.11   52     Authentication, SN=892, FN=0, Flags=........C
    264 15.666177615   82:5a:65:0a:e4:8d     TexasIns_52:be:99     802.11   164    Association Request, SN=353, FN=0, Flags=........C, SSID=Map-52BE99
    266 15.693355602   TexasIns_52:be:99     82:5a:65:0a:e4:8d     802.11   156    Association Response, SN=2931, FN=0, Flags=........C
    268 15.709056668   TexasIns_52:be:99     82:5a:65:0a:e4:8d     EAPOL    155    Key (Message 1 of 4)
    270 15.710997692   82:5a:65:0a:e4:8d     TexasIns_52:be:99     EAPOL    179    Key (Message 2 of 4)
    272 15.715620982   TexasIns_52:be:99     82:5a:65:0a:e4:8d     EAPOL    259    Key (Message 3 of 4)
    274 15.717480302   82:5a:65:0a:e4:8d     TexasIns_52:be:99     EAPOL    155    Key (Message 4 of 4)
    276 15.737669196   82:5a:65:0a:e4:8d     Broadcast             802.11   400    QoS Data, SN=2, FN=0, Flags=.p.....TC

First Re-association packats

No.     Time           Source                Destination           Protocol Length Info
    346 16.857820466   TexasIns_52:be:99     Broadcast             802.11   240    Beacon frame, SN=2898, FN=0, Flags=........C, BI=100, SSID=Map-52BE99
    348 16.926019428   82:5a:65:0a:e4:8d     Broadcast             802.11   123    Probe Request, SN=288, FN=0, Flags=........C, SSID=Map-52BE99
    349 16.928135083   TexasIns_52:be:99     82:5a:65:0a:e4:8d     802.11   234    Probe Response, SN=893, FN=0, Flags=........C, BI=100, SSID=Map-52BE99
    352 16.960266478   TexasIns_52:be:99     Broadcast             802.11   240    Beacon frame, SN=2899, FN=0, Flags=........C, BI=100, SSID=Map-52BE99
    353 16.984395518   82:5a:65:0a:e4:8d     Broadcast             802.11   123    Probe Request, SN=289, FN=0, Flags=........C, SSID=Map-52BE99
    354 16.986422327   TexasIns_52:be:99     82:5a:65:0a:e4:8d     802.11   234    Probe Response, SN=894, FN=0, Flags=........C, BI=100, SSID=Map-52BE99
    357 17.035324913   82:5a:65:0a:e4:8d     TexasIns_52:be:99     802.11   52     Authentication, SN=355, FN=0, Flags=........C
    359 17.044653013   TexasIns_52:be:99     82:5a:65:0a:e4:8d     802.11   52     Authentication, SN=2935, FN=0, Flags=........C
    361 17.046614489   82:5a:65:0a:e4:8d     TexasIns_52:be:99     802.11   170    Reassociation Request, SN=356, FN=0, Flags=........C, SSID=Map-52BE99
    363 17.053319794   TexasIns_52:be:99     82:5a:65:0a:e4:8d     802.11   156    Reassociation Response, SN=1544, FN=0, Flags=........C
    365 17.060736260   TexasIns_52:be:99     82:5a:65:0a:e4:8d     EAPOL    155    Key (Message 1 of 4)
    367 17.062707799   82:5a:65:0a:e4:8d     TexasIns_52:be:99     EAPOL    179    Key (Message 2 of 4)
    369 17.067748204   TexasIns_52:be:99     82:5a:65:0a:e4:8d     EAPOL    259    Key (Message 3 of 4)
    371 17.069512343   82:5a:65:0a:e4:8d     TexasIns_52:be:99     EAPOL    155    Key (Message 4 of 4)
    373 17.074148928   82:5a:65:0a:e4:8d     Broadcast             802.11   400    QoS Data, SN=2, FN=0, Flags=.p.....TC
    375 17.079062341   82:5a:65:0a:e4:8d     Broadcast             802.11   402    Data, SN=1420, FN=0, Flags=.p....F.C
    376 17.094929794   TexasIns_52:be:99     Broadcast             802.11   402    Data, SN=1421, FN=0, Flags=.p....F.C
    377 17.113301131   82:5a:65:0a:e4:8d     IPv4mcast_16          802.11   112    QoS Data, SN=3, FN=0, Flags=.p.....TC

Next Re-association packets (sequence repeated every few seconds for 2 minutes when connection fails)

No.     Time           Source                Destination           Protocol Length Info
    500 18.399771596   82:5a:65:0a:e4:8d     Broadcast             802.11   123    Probe Request, SN=296, FN=0, Flags=........C, SSID=Map-52BE99
    501 18.401870523   TexasIns_52:be:99     82:5a:65:0a:e4:8d     802.11   234    Probe Response, SN=897, FN=0, Flags=........C, BI=100, SSID=Map-52BE99
    503 18.460317053   82:5a:65:0a:e4:8d     Broadcast             802.11   123    Probe Request, SN=297, FN=0, Flags=........C, SSID=Map-52BE99
    504 18.462412578   TexasIns_52:be:99     82:5a:65:0a:e4:8d     802.11   234    Probe Response, SN=898, FN=0, Flags=........C, BI=100, SSID=Map-52BE99
    506 18.496178483   TexasIns_52:be:99     Broadcast             802.11   240    Beacon frame, SN=2905, FN=0, Flags=........C, BI=100, SSID=Map-52BE99
    507 18.503718825   82:5a:65:0a:e4:8d     TexasIns_52:be:99     802.11   52     Authentication, SN=359, FN=0, Flags=........C
    509 18.512332410   TexasIns_52:be:99     82:5a:65:0a:e4:8d     802.11   52     Authentication, SN=1549, FN=0, Flags=........C
    511 18.514253144   82:5a:65:0a:e4:8d     TexasIns_52:be:99     802.11   170    Reassociation Request, SN=360, FN=0, Flags=........C, SSID=Map-52BE99
    513 18.524222162   TexasIns_52:be:99     82:5a:65:0a:e4:8d     802.11   156    Reassociation Response, SN=2995, FN=0, Flags=........C
    515 18.532140180   TexasIns_52:be:99     82:5a:65:0a:e4:8d     EAPOL    155    Key (Message 1 of 4)
    517 18.534016503   82:5a:65:0a:e4:8d     TexasIns_52:be:99     EAPOL    179    Key (Message 2 of 4)
    519 18.538746695   TexasIns_52:be:99     82:5a:65:0a:e4:8d     EAPOL    259    Key (Message 3 of 4)
    521 18.540607127   82:5a:65:0a:e4:8d     TexasIns_52:be:99     EAPOL    155    Key (Message 4 of 4)
    523 18.547179004   82:5a:65:0a:e4:8d     Broadcast             802.11   400    QoS Data, SN=2, FN=0, Flags=.p.....TC
    525 18.552359758   82:5a:65:0a:e4:8d     Broadcast             802.11   402    Data, SN=1433, FN=0, Flags=.p....F.C
    526 18.574961411   TexasIns_52:be:99     Broadcast             802.11   402    Data, SN=1434, FN=0, Flags=.p....F.C
    527 18.590505040   82:5a:65:0a:e4:8d     IPv4mcast_16          802.11   112    QoS Data, SN=3, FN=0, Flags=.p.....TC

Workaround:

  • Switch to wl127x multi-role firmware by adding a 2nd interface, i.e. iw wlan0 interface add wlansta0 type station.

Different single-role wl127x firmware revisions behaved the same.

  • Single-role Rev: 6.3.10.0.142, 6.3.10.0.133, 3.3.10.2.115

  • Multi-role Rev: 6.5.7.2.49

  • 0
    TI__Mastermind 35795 points

    Hi ,

    WL127x was succeeded by WiLink8 ( WL18xx ) yeas ago . We haven't done any software releases or maintenance on WL127x in last few years except updating it for WPA2 KRACK fix I believe .  Seems like you are using latest version of SR fwr :

    Are you able to design in WiLink8 instead on your product ? Is using MR fwr on your product an option  ?

    Thanks

    Saurabh

  • 0 in reply to S
    Prodigy 20 points

    Hi Saurabh,

    Thanks for the quick reply. No, switching out the Wi-Fi hardware module on our deployed product is not an option. We're update the Linux kernel to add enhancements and improve security. Yes, we can use the multi-role firmware as a workaround.

    Kim