The TI E2E™ design support forums will undergo maintenance from Sept. 28 to Oct. 2. If you need design support during this time, contact your TI representative or open a new support request with our customer support center.

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.

WL1801MOD: Questions on WiLink driver capabilities

Part Number: WL1801MOD

My customer has following questions using a WL18xx module (I will add more details once available or ask the customer to add here):

Question 1

There are some macro define in wlcore driver files:

    #define WLCORE_MAX_LINKS 16

    #define WL18XX_MAX_AP_STATIONS 10

    #define WL18XX_MAX_LINKS 16

Are those macro determined by the firmware capabilities?

Question 2

Regarding the firmware fix on FragAttacks for wl18xx family, is it compatible with linux kernel 4.9 wlcore driver? We are on kernel 4.9 using the ti stack driver from the kernel source.

Question 3

How do I enable the debug logging on wlcore.ko?

I notice that there is a debug_level driver parameter can be set as a bit map to enable logging on deferent components in wlcore.

And I also set the printk to the max to display the "info" and "debug" messages. However, I do not see any of those messages in dmesg.

  • Hi Frank,

    For question 1, that is correct this is the device capabilities.

    For question 2, I am reaching out internally and will get back to you shortly. 

    For question 3, to enable logs please see here - https://www.ti.com/lit/ug/swru575/swru575.pdf?ts=1629727301736&ref_url=https%253A%252F%252Fwww.google.com%252F

    BR,

    Vince 

  • Hello Vincent,

    I am Frank's customer who asked those questions. Can you share some more on those questions?

    Question 1, I understand that firmware limits those defines, even though they are defined in the driver, correct?

    Question 3, I have read those documentations before, 

    I load the driver with command insmod wlcore.ko debug_level=0x63c00, and overwrite the printk level "echo 8 > /proc/sys/kernel/printk". It did not work with those "info" and "debug" messages. That is why I am reaching out for help.

    Thank you,

    Hao

  • Hi Hao,

    The driver also needs to know the firmware limits to ensure it doesn't use our device inproperly, thus is why those are defined. For Linux 4.9 kernel, you can't use our wlcore from our wilink drivers but should be able to use the native intree driver that comes with that kernel. 

    Lastly I am trying to bring up a setup and verify the log issue - please give me until friday to complete this. 

  • Hi Vincent,

    thank you for clearing the max number station question up for us.

    Yes we are on kernel4.9 intree driver. Have you heard anything internally regarding if this driver is compatible with the latest firmware yet? We need to move to the latest firmware for security reasons, etc FragAttack fix you guys put in this firmware.

  • Hi Hao,

    I believe our drivers were tested up to Kernel version 4.19. You will need to validate the driver on the latest kernel, and if you have issues, please let us know.

  • Hi Vincent,

    we have experience some problem with maximum number of stations testing. Please take a look at the following log:

    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:6c:05:e2 IEEE 802.11: authenticated
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:6c:05:e2 IEEE 802.11: associated (aid 1)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:a8:89:e2 IEEE 802.11: authenticated
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:a8:89:e2 IEEE 802.11: associated (aid 2)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:f4:30:e2 IEEE 802.11: authenticated
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:f4:30:e2 IEEE 802.11: associated (aid 3)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:f4:30:e2 RADIUS: starting accounting session B8F361D306E34921
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:f4:30:e2 WPA: pairwise key handshake completed (RSN)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:44:d0:e2 IEEE 802.11: authenticated
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:44:d0:e2 IEEE 802.11: associated (aid 4)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:44:d0:e2 RADIUS: starting accounting session 4AAFB9DE020461F7
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:44:d0:e2 WPA: pairwise key handshake completed (RSN)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:2c:45:e2 IEEE 802.11: authenticated
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:2c:45:e2 IEEE 802.11: associated (aid 5)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:aa:99:e2 IEEE 802.11: authenticated
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:aa:99:e2 IEEE 802.11: associated (aid 6)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:83:34:e2 IEEE 802.11: authenticated
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:83:34:e2 IEEE 802.11: associated (aid 7)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:83:34:e2 RADIUS: starting accounting session 55FB03B9E26AD1C8
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:83:34:e2 WPA: pairwise key handshake completed (RSN)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:8d:93:e2 IEEE 802.11: authenticated
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:8d:93:e2 IEEE 802.11: associated (aid 8)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:8d:93:e2 RADIUS: starting accounting session 0D8020C5B04BA237
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:8d:93:e2 WPA: pairwise key handshake completed (RSN)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:f6:4d:e2 IEEE 802.11: authenticated
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:f6:4d:e2 IEEE 802.11: associated (aid 9)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:f6:4d:e2 RADIUS: starting accounting session 2F38C6767F171DC7
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:f6:4d:e2 WPA: pairwise key handshake completed (RSN)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:97:96:e2 IEEE 802.11: authenticated
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:97:96:e2 IEEE 802.11: associated (aid 10)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:97:96:e2 RADIUS: starting accounting session 29EC587625EB18B6
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:97:96:e2 WPA: pairwise key handshake completed (RSN)
    Nov 4 13:55:27 AP1 kernel: [ 169.688739] wlcore: WARNING could not allocate HLID - too much stations
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:f9:81:e2 IEEE 802.11: Could not add STA to kernel driver
    Nov 4 13:55:27 AP1 kernel: [ 169.711841] wlcore: WARNING could not allocate HLID - too much stations
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:0e:8e:25:c3:e2 IEEE 802.11: Could not add STA to kernel driver
    Nov 4 13:55:27 AP1 dhcpd[4861]: DHCPDISCOVER from 00:0e:8e:44:d0:e2 via wlan-ap1
    Nov 4 13:55:27 AP1 dhcpd[4861]: DHCPDISCOVER from 00:0e:8e:f4:30:e2 via wlan-ap1
    Nov 4 13:55:27 AP1 dhcpd[4861]: DHCPDISCOVER from 00:0e:8e:f6:4d:e2 via wlan-ap1
    Nov 4 13:55:27 AP1 dhcpd[4861]: DHCPDISCOVER from 00:0e:8e:8d:93:e2 via wlan-ap1
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:21:6b:c9:bb:da IEEE 802.11: authenticated
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:21:6b:c9:bb:da IEEE 802.11: associated (aid 6)
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:21:6b:c9:bb:da RADIUS: starting accounting session A2985CED12CC81B5
    Nov 4 13:55:27 AP1 hostapd: wlan-ap1: STA 00:21:6b:c9:bb:da WPA: pairwise key handshake completed (RSN)

    After 10 stations has connected, we see that a new station got into the wireless network. This is not expected. Since 10 stations is the max for firmware, why would firmware forwarded new association request to hostapd after 10 stations has connected?

  • Can you verify which Mac address is present for aid 6? Is it the new client or previously associated one? 

  • Vincent,

    This is from a Bug report we have here reported by our QA team. I am working on building a setup and reproduce this. 

    I can share with you more detail next week. This looks very fishy to me. I thought since 10 stations has connected, that firmware has to reject any new incoming association request. However, it seems like new association request gets all the way up to hostapd, and hostapd is trying to add a new station to cfg80211.

  • Thanks Hao, I will loop in another WiLink expert to assist here and provide any additional guidance.

  • Hao,

    We had fixed an issue on kernel 4.9  related to max AP stations.  Pls apply patches 0004-x & 0005-x and re-test :

    https://git.ti.com/cgit/wilink8-wlan/build-utilites/tree/patches/kernel_patches/4.19.38?h=r8.8

    Saurabh