wpa_supplicant and no Internet connection

Dan Williams dcbw at redhat.com
Sat Oct 12 16:02:48 EDT 2013

On Sat, 2013-10-12 at 10:08 +0200, Arend van Spriel wrote:
> On 10/11/2013 11:46 PM, John V. Smith wrote:
> > wpa_supplicant -Dnl80211 -iwlp5s0 -c
> > /etc/wpa_supplicant/wpa_supplicant.conf says
> > *Code:*	
> > wpa_supplicant -Dnl80211 -iwlp5s0 -c
> > /etc/wpa_supplicant/wpa_supplicant.conf
> > Successfully initialized wpa_supplicant
> > wlp5s0: SME: Trying to authenticate with 98:42:46:01:f0:0c (SSID='@:-D'
> > freq=2462 MHz)
> > wlp5s0: Trying to associate with 98:42:46:01:f0:0c (SSID='@:-D'
> > freq=2462 MHz)
> > wlp5s0: Associated with 98:42:46:01:f0:0c
> > wlp5s0: WPA: Key negotiation completed with 98:42:46:01:f0:0c [PTK=TKIP
> > wlp5s0: CTRL-EVENT-CONNECTED - Connection to 98:42:46:01:f0:0c completed
> > [id=0 id_str=]
> > wlp5s0: CTRL-EVENT-DISCONNECTED bssid=98:42:46:01:f0:0c reason=3
> > locally_generated=1	
> >
> > *BUT NO Internet Connection EVEN no ping*
> Which totally makes sense given the last *DISCONNECT* event in the log 
> above, but without timestamps it is hard to tell whether this is your 
> problem.
> Is there some sort of connection manager like NetworkManager running 
> while attempting to run wpa_supplicant from the command line. You should 
> disable that service. After establishing connection you have to run a 
> dhcp client to establish IP connectivity, eg. dhclient -v wlp5s0

When running NetworkManager, NM will communicate with an already-running
wpa_supplicant, or it will ask D-Bus to spawn a supplicant for it.  And
then if you run a supplicant yourself, they will fight over the
interface and you may well see the "reason=3 locally_generated=1"
responses.  The solution here is to either manage the interface with
NetworkManager, or make NM ignore it and do it all yourself.


More information about the HostAP mailing list