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.

WL1837MOD: Very High ping on WL1837MOD

Part Number: WL1837MOD


Hi Support,

my customer is testing WL1837MOD kit in bundle with NXP Processor and with Linux 4.1.

They have two systems, one is working as client and the other as access point.

They see ping in the range of 100msec, with peaks of 140msec. Testing the same environment with competitor Wi-Fi they see 2msec.

Is it possible to work at driver level in order to solve this issue?

Do you have other suggestion / tests that customer can try?

Thanks and regards,

Alberto

  • Hi Alberto,
    There, could be several reasons - a) Please, try with disabling the low power states on the host processor. b) Are they using COM8 module? If not, ensure that the Antenna performance is good with their board. c) You can also try with the following kernel configurations :

    CONFIG_TCP_CONG_ADVANCED=y
    CONFIG_DEFAULT_RENO=y
    CONFIG_DEFAULT_TCP_CONG="reno"

    Thanks
  • Thanks Hari,

    can you also kindly help me providing the feedback on other antennas questions, like:

    1) Is the module certified using 1 or 2 antennas?
    2) Can we provide the antenna model used in certification?
    3) Can the module work fine with one antenna, even if it's set in MIMO mode?

    Thanks and regards,
    Alberto
  • Hi Alberto,

    You are seeing 100msec with ping because power save is enabled by default and the system is able to enter power save between pings as there is no traffic for a long period.
    It wakes up on every ping request (in next beacon from the AP) and this is the 100msec you see.
    Try disabling power save:

    iw wlan0 set power_save off

    And you should see the lower numbers with ping.

    Best Regards,
    Eyal
  • Hari,

    1) They don't have Low Power states at Host PRocessor
    2) Confirmed they are using COM8
    3) Suggested parameters did not change the situation, so OING is still high.

    They will now try to remove (if present) Power Save.
    Come back to you with feedback soon.

    Alberto
  • Hi
    Alberto told me to put my feedback here.
    I have removed power save but the ping behaviour hasn't changed.
    Anyway if I transmit UDP messages every 10 ms on both sides the ping time goes down to 3/4 ms
    This ping time is ok for me.

    I have some other questions about g WL1837MOD.
    Until now I have used infrastructure mode (Access Point + client), but I'd like to use point to point communication: ad hoc or WiFi Direct.
    Ad hoc mode isn't available, is it?

    If I try to use WiFi Direct I get this error:

    root@exorNS01kit:/usr/share/wl18xx# ./p2p_start.sh
    Successfully initialized wpa_supplicant
    nl80211: Failed to open /proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast: No such file or directory
    nl80211: Failed to set IPv4 unicast in multicast filter

    Do you have any idea of the reason of this error?

    Thanks
    Marco Raiteri
  • Hi Marco,

    Ad-Hoc is deprecated an is not supported.
    I am not sure that the error you posted above is fatal. Can you try the full sequence as in the examples below:

    processors.wiki.ti.com/.../WiLink8_WLAN_Demo:_Linux

    BR,
    Eyal
  • Hi Eyal,

    I have tried to do what you suggested but when I run p2p_cli.sh it doesn't give me the prompt:

    root@exorNS01kit:~# cd /usr/share/wl18xx

    root@exorNS01kit:/usr/share/wl18xx# ./p2p_start.sh
    Successfully initialized wpa_supplicant
    wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
    nl80211: Failed to open /proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast: No such file or directory
    nl80211: Failed to set IPv4 unicast in multicast filter

    root@exorNS01kit:/usr/share/wl18xx# ./p2p_cli.sh
    wpa_cli v2.6-devel-R8.7_SP3
    Copyright (c) 2004-2016, Jouni Malinen <j@w1.fi> and contributors

    This software may be distributed under the terms of the BSD license.
    See README for more details.



    Interactive mode

    Could not connect to wpa_supplicant: p2p-dev-wlan0 - re-trying

    Thanks
    BR
    Marco
  • Hi Marco,

    What version of the kernel are yo using?
    Are you using the drivers from our R8.7_sp3 as well?

    Next, What is the output of:

    cd /usr/share/wl18xx
    killall wpa_supplicant
    ifconfig wlan0 down
    ./p2p_start.sh
    ./p2p_cli.sh

    BR,
    Eyal
  • Hi Eyal,
    we are using a 4.1 freescale kernel that you can find here:
    github.com/.../4.1-2.0.x-imx-RT
    branch: 4.1-2.0.x-imx-RT

    How can I read the TI drivers version ?
    When I start ./p2p_cli.sh it prints:
    wpa_cli v2.6-devel-R8.7_SP3

    This is the output you requested:

    root@exorNS01kit:~# cd /usr/share/wl18xx
    root@exorNS01kit:/usr/share/wl18xx# killall wpa_supplicant
    root@exorNS01kit:/usr/share/wl18xx# ifconfig wlan0 down
    root@exorNS01kit:/usr/share/wl18xx# ./p2p_start.sh
    Successfully initialized wpa_supplicant
    rfkill: WLAN soft blocked
    nl80211: Failed to open /proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast: No such file or directory
    nl80211: Failed to set IPv4 unicast in multicast filter
    root@exorNS01kit:/usr/share/wl18xx# ./p2p_cli.sh
    wpa_cli v2.6-devel-R8.7_SP3
    Copyright (c) 2004-2016, Jouni Malinen <j@w1.fi> and contributors

    This software may be distributed under the terms of the BSD license.
    See README for more details.


    If I run "rfkill unblock all" at the beginning then the "rfkill: WLAN soft blocked" error disappears:

    root@exorNS01kit:~# rfkill unblock all
    root@exorNS01kit:~# cd /usr/share/wl18xx
    root@exorNS01kit:/usr/share/wl18xx# killall wpa_supplicant
    root@exorNS01kit:/usr/share/wl18xx# ifconfig wlan0 down
    root@exorNS01kit:/usr/share/wl18xx# ./p2p_start.sh
    Successfully initialized wpa_supplicant
    wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
    nl80211: Failed to open /proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast: No such file or directory
    nl80211: Failed to set IPv4 unicast in multicast filter
    root@exorNS01kit:/usr/share/wl18xx# ./p2p_cli.sh
    wpa_cli v2.6-devel-R8.7_SP3
    Copyright (c) 2004-2016, Jouni Malinen <j@w1.fi> and contributors

    This software may be distributed under the terms of the BSD license.
    See README for more details.


    Interactive mode

    Could not connect to wpa_supplicant: p2p-dev-wlan0 - re-trying


    Thanks
    BR
    Marco
  • Hello,
    I don see the error you are getting on a platform that I am using (v4.14 based)

    root@am65xx-evm:/usr/share/wl18xx#
    root@am65xx-evm:/usr/share/wl18xx#
    root@am65xx-evm:/usr/share/wl18xx# ./p2p_start.sh
    Successfully initialized wpa_supplicant
    [ 36.174747] wlcore: down
    root@am65xx-evm:/usr/share/wl18xx# ./p2p_cli.sh
    wpa_cli v2.6-devel-R8.7_SP3
    Copyright (c) 2004-2016, Jouni Malinen <j@w1.fi> and contributors

    This software may be distributed under the terms of the BSD license.
    See README for more details.



    Interactive mode

    ....
    What happens if instead of running p2p_cli.sh, run the following command:
    wpa_cli -i -wlan0 -p /var/run/wpa_supplicant/ $@

    BR,
    Eyal
  • Hi Eyal

    root@exorNS01kit:~# rfkill unblock all
    root@exorNS01kit:~#  cd /usr/share/wl18xx
    root@exorNS01kit:/usr/share/wl18xx# killall wpa_supplicant
    root@exorNS01kit:/usr/share/wl18xx# ifconfig wlan0 down
    root@exorNS01kit:/usr/share/wl18xx# ./p2p_start.sh
    Successfully initialized wpa_supplicant
    wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
    nl80211: Failed to open /proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast: No such file or directory
    nl80211: Failed to set IPv4 unicast in multicast filter
    root@exorNS01kit:/usr/share/wl18xx#
    root@exorNS01kit:/usr/share/wl18xx# wpa_cli -i -wlan0 -p /var/run/wpa_supplicant/ $@
    wpa_cli v2.6-devel-R8.7_SP3
    Copyright (c) 2004-2016, Jouni Malinen <j@w1.fi> and contributors

    This software may be distributed under the terms of the BSD license.
    See README for more details.



    Interactive mode

    Could not connect to wpa_supplicant: -wlan0 - re-trying

    Unfortunately the prompt doesn't appear.

    BR

    Thanks

    Marco

  • Hi,

    Have you built our latest drivers (from R8.7_SP3) using our build script?
    processors.wiki.ti.com/.../WL18xx_System_Build_Scripts

    Or are you using the in-tree modules of your kernel?
    In case the drivers are from your 4.1 kernel, please make sure you build the ones from our R8.7_SP3 using backports as mentioned in the wiki page above.

    BR,
    Eyal
  • Hi,

    we built your latest drivers  R8.7_SP3 using your build script.

    thanks

    BR

    Marco

  • I am not seeing such issue on any of my platforms.
    Can you start wpa_supplicant with extra debugging and send the logs?

    In addition, are yo able to use sta_start.sh instead of p2p_start.sh?

    BR,
    Eyal