mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "BuraphaLinux Server" <buraphalinuxserver@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Luca Venturini" <lucventurini@gmail.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: New IWL4935 driver for Intel Wireless Cards does not support WPA2 wireless network with PEAP - MSCHAPV2
Date: Wed, 2 Apr 2008 03:06:07 +0700	[thread overview]
Message-ID: <5d75f4610804011306y55352e73sb5223a294b66f2cf@mail.gmail.com> (raw)
In-Reply-To: <20080401164419.GA3530@tuxdriver.com>

intel wireless just doesn't work on linux 2.6.24.4; wait for 2.6.25.x stable.

On 4/1/08, John W. Linville <linville@tuxdriver.com> wrote:
> You probably want to address this to linux-wireless@vger.kernel.org
> instead...
>
> On Tue, Apr 01, 2008 at 10:40:20AM +0200, Luca Venturini wrote:
> > Using Ubuntu Hardy Beta, Linux kernel 2.6.24, AMD64.
> > I have to connect to a campus (University of Verona, Italy; more
> > information maybe available at https://wifi.univr.it sadly in Italian
> only,
> > and I am not sure it is reachable from outside the university) WPA2
> > wireless network. It uses PEAP authentication, Dynamic WEP encryption,
> > second phase: MSCHAPv2.
> > It also requires user login, password, and a CA certificate (available at
> > the web page I linked above).
> > At the same page a wpasupplicant configuration file is also available, so
> > to allow people to connect from linux also.
> > In Ubuntu Gutsy 32 bit (Linux kernel 2.6.22.14 if I am not mistaken) I was
> > able to connect through NetworkManager and precisely using the GNOME
> > nm-applet.
> > However, since I switched to Linux 2.6.24, I have no more been able to
> > connect, whether through NM-applet or from the command line, using
> > wpasupplicant. The wireless functions perfectly, and there has been no
> > change in its configuration, since I am using it now (Windows Vista,
> > configured months ago).
> > Reported also here on launchpad:
> > https://bugs.launchpad.net/ubuntu/+bug/209602
> > Thank you for your attention.
> > Greetings
> >
> > Luca Venturini
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
>
> --
> John W. Linville
> linville@tuxdriver.com
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2008-04-01 20:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01  8:40 Luca Venturini
2008-04-01 16:44 ` John W. Linville
2008-04-01 20:06   ` BuraphaLinux Server [this message]
2008-04-01 21:02     ` Luca Venturini
2008-04-02  0:54       ` Pavel Roskin
2008-04-02 12:24         ` Lennart Sorensen
2008-04-02 19:48           ` Pavel Roskin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5d75f4610804011306y55352e73sb5223a294b66f2cf@mail.gmail.com \
    --to=buraphalinuxserver@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lucventurini@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome