nl80211, wext, dhclient

Dan Williams dcbw at
Fri Sep 4 12:26:56 EDT 2015

On Fri, 2015-09-04 at 15:25 +0200, Simon Kitching wrote:
> Hi,
> I've noticed some odd behaviour I hope someone here can explain.
> I can get dhcpcd/dhclient to initialise an interface with wpa_supplicant 
> using "-Dwext" but not "-Dnl80211" (ie the default). Is that expected 
> behaviour?
> System: Lenovo thinkpad with intel 7265 wireless. OS: debian8 or 
> linux-from-scratch (both show the same behaviour), systemd-based but all 
> network-related daemons disabled.
> If I run
>    wpa_supplicant -c.. -iwlp3s0
> then the interface does not reach RUNNING state (according to ifconfig).

Posting the debug logging from wpa_supplicant (pass '-dddt' to it to
enable debug logging) and the config file network block would be
necessary to figure out what's going on.  Also, what kernel version?


> Running "dhcpcd wlp3s0" afterwards reports "link not up" and eventually 
> exits. Running "dhclient wlp3s0" just hangs.
> If I add "-Dwext" to the wpa_supplicant options, then the interface 
> reaches state RUNNING, and dhcpcd/dhclient allocate an address for it. 
> That is obviously a problem, as the default systemd service file for 
> wpa_supplicant starts it without any -D parameter, ie defaulting to nl80211.
> The debian install connects fine if run normally (ie all regular daemons 
> enabled, NetworkManager managing networking).
> Any advice appreciated
> Regards,
> Simon
> _______________________________________________
> HostAP mailing list
> HostAP at

More information about the HostAP mailing list