Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#2745 - wpa_supplicant watchdog not working on second wifi interface (phy1) #7550

openwrt-bot opened this issue Jan 17, 2020 · 0 comments


Copy link

@openwrt-bot openwrt-bot commented Jan 17, 2020


  • Device problem occurs on
    I'm using a mikrotik rb952 with QCA9531 and QCA9887 16M flash and 64 RAM.
  • Software versions of OpenWrt/LEDE release, packages, etc.
    latest version compiled from source (version is from date january 17 2020)
  • Steps to reproduce
    long way:
    1)remove configuration of wifi client
    2) connect wifi client (eap)
  1. repaet 1)&2) 4 or mor times

short way:

  1. check you have the two wpa_supplicant running with "ps | grep wpa"
  2. kill the wpa_supplciant process for phy1
    this process will no be restarted.
  • Overview
    for some reason after change wifi client configuration more than 4 times (or more) wifi client won't connect any more. the issue is related with wpa_supplicant (wpad symbol link) wich stop running (I could't find the reason) for the phy interface of wifi. I have two phy wifi interfaces (5ghz and 2.4ghz).
    the issue is on phy1. the process "/usr/sbin/wpa_supplicant -s -n phy1 -g /var/run/wpa_supplicant-phy1/global"
    will not be restarted automatically. but if I kill the process for phy0, after 10 seconds it will be running again.

Workarround: I found that if I run manually "hotplug-call ieee80211" the two instances of wpa_supplicant (phy0 and phy1) will be running again.

Where is the watchdog for wpa_supplicant process?
It seams that the watchdog only will monitor the first wpa_supplicant process (for phy0) and not for phy1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant