Re: [PATCH] LEAP support in NetworkManager

[Jason Martens <me jasonmartens com>]

Thiago Bauermann wrote:
> 2006/10/13, Jason Martens <me jasonmartens com 
> <mailto:me jasonmartens com>>:
>
>     Alright, I tried it without the group and pairwise options, and it
>     works
>     using wpa_supplicant, so I re-installed my pre-Thiago patch NM, and
>     tried to connect to the AP using the existing LEAP support, which
>     failed.  So, I have still yet to successfully connect to this AP
>     using
>     NM.  Below is the (most recent) working wpa_supplicant config, and the
>     syslog of NM trying to connect to the same AP (without the extra LEAP
>     options).
>
>
> Ok, so NM is timing out when trying to connect to the AP. When you 
> connect
> using wpa_supplicant, does it take a long time to associate? Maybe NM 
> is quitting too soon.
>
> What is the driver wpa_supplicant is using (wext, madwifi, etc.)? And 
> does it use the eth2_rename interface? That is a strange name for an 
> interface, maybe it has something to do with your problem, who knows...
> --
> []'s
> Thiago Jung Bauermann
No, wpa_supplicant pretty much connects right away.  And I believe that 
the eth2_rename is because of n-m stuff, but I could be wrong about 
that.  At any rate, it's the same one I'm using with wpa_supplicant.  
I'm using the wext drivers for wpa_supplicant.

Jason