linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Venturini <lucventurini@gmail.com>
To: 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, 02 Apr 2008 17:30:03 +0200	[thread overview]
Message-ID: <47F3A67B.1040909@gmail.com> (raw)
In-Reply-To: <47F38267.2040301@fenrir.org.uk>

(I hope I am not making again something rude posting here, and if this 
is the case, I apologize; I am sorry, but this is the first time ever I 
write directly to Linux developers, and I am unsure of how to behave.)

I thank everybody for your help and understanding. I will try to contact 
Ubuntu developers and ask about current situation for this issue. In the 
meantime, Filippo Zangheri of the Linux team was so kind as to give me 
detailed instructions on how to install the latest modules for intel 
wireless cards, so hopefully I will patch the problem well enough so to 
actually update my box...and see if developers have indeed addressed the 
problem in the meantime.

Thank you again, and keep up the awesome work!

Luca Venturini

Brian Morrison ha scritto:
> Luca Venturini wrote:
>> I hope, then, that Linux 2.6.25.x stable will be out sooner than 24th 
>> april (Hardy release date) otherwise I (and I guess also many other 
>> people) will be in a very bad spot until the kernel is updated...(I 
>> am not proficient enough so to compile a whole Linux kernel for my 
>> distro).
>
> I don't know about the Ubuntu situation, but in Fedora the current 
> 2.6.24.x series kernels work just fine with the iwlwifi driver and 
> 3945 and 4965 chipset firmware. Much of the 2.6.25 wireless changes 
> are already in the Fedora kernels (that's where a lot of testing 
> happens) and there is no reason that the Ubuntu maintainers cannot do 
> the same thing. Testing of these changes and discussion of same occurs 
> on the linux-wireless list, if you're seeing problems this is a good 
> place to ask for help. I don't use PEAP with MSCHAPV2 myself, but I 
> did see something on the NetworkManager mailing list from Bill Moss at 
> Clemson University who has got some sort of certificate authentication 
> working under Fedora (might be PEAP), you can probably find his post 
> with help from Google.
>
> I'd suggest asking the Ubuntu team what the status is for this issue 
> and if they have any test kernels to try. The kernel ML is not a good 
> place since they are concerned with the vanilla release and not with 
> any distro specific changes. Linux wireless is under heavy development 
> and 2.6.25 vanilla is the first release where anything like working 
> code will appear from Linus, but the same code has been in the distros 
> fro some time as they need to provide people with a working environment.
>
> HTH :)
>


       reply	other threads:[~2008-04-02 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <adKlV-3WV-5@gated-at.bofh.it>
     [not found] ` <adS9O-4u9-1@gated-at.bofh.it>
     [not found]   ` <adUY2-379-7@gated-at.bofh.it>
     [not found]     ` <adVUj-5bx-81@gated-at.bofh.it>
     [not found]       ` <47F38267.2040301@fenrir.org.uk>
2008-04-02 15:30         ` Luca Venturini [this message]
2008-04-02 15:57           ` New IWL4935 driver for Intel Wireless Cards does not support WPA2 wireless network with PEAP - MSCHAPV2 Filippo Zangheri
     [not found] <47F1F4F4.2080502@gmail.com>
2008-04-01 16:44 ` John W. Linville
2008-04-01 20:06   ` BuraphaLinux Server
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=47F3A67B.1040909@gmail.com \
    --to=lucventurini@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).