How is it, with ndiswrapper, networkmanager can do it?  Is it a
limitation in bcm43xx?

On 4/10/07, Hendrik Sattler <[EMAIL PROTECTED]> wrote:
> Am Dienstag 10 April 2007 17:25 schrieb John H.:
> > My school uses the following setup in wpa_supplicant, which I don't
> > even need to use with NetworkManager.  However, this does not work
> > with bcm43xx even with latest patches, but it does work with
> > ndiswrapper.  NetworkManager blatantly says, with bcm43xx driver,
> > "encryption not supported,..." or something.
> >
> > bcm43xx works fine with wpa_supplicant and networkmanager with wpa1...
> >
> > network={
> >         ssid="university"
> >         key_mgmt=WPA-EAP
> >         pairwise=TKIP
> >         group=TKIP
> >         scan_ssid=1
> >         eap=PEAP
> >         identity="myuser"
> >         password="mypass"
> > #       ca_cert="/etc/cert/ca.pem"
> > #       phase1="peaplabel=1"
> >        phase2="auth=MSCHAPV2"
> > }
>
> Interesting because according to networkmanager lists, phase2 is not supported
> by them.
> Did this change lately? If not, you _have_ to use wpa_supplicant manually.
>
> HS
>
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to