From: Simon Wunderlich <sw@simonwunderlich.de>
To: Mark Kettner <mkettn@technik-emden.de>
Cc: Nicolas Cavallari <Nicolas.Cavallari@lri.fr>,
linux-wireless@vger.kernel.org
Subject: Re: WPA_Supplicant: no unicast with wpa encryption
Date: Fri, 15 Nov 2013 16:12:50 +0100 [thread overview]
Message-ID: <201311151612.50894.sw@simonwunderlich.de> (raw)
In-Reply-To: <20131115141635.663e48d7@mke-x61t>
Mark,
> On Fri, 15 Nov 2013 10:42:36 +0100 Nicolas Cavallari
>
> <Nicolas.Cavallari@lri.fr> wrote:
> > > […]
> >
> > WPA-NONE is not true WPA. Support for it was broken in wpasupplicant
> > for a long time, and the kernel does not support it anymore. Use IBSS
> > RSN instead :
> >
> > proto=RSN
> > key_mgmt=WPA-PSK
> > pairwise=CCMP
> > group=CCMP
> >
> > > and the /etc/network/interfaces like this:
> > > auto lo
> > >
> > > iface lo inet loopback
> > > iface eth0 inet dhcp
> > >
> > > allow-hotplug wlan0
> > > iface wlan0 inet static
> > >
> > > address 192.168.13.37
> > > netmask 255.255.255.255
> > >
> > > # Load WPA-Supplicant for WPA in Ad-Hoc Mode
> > > wpa-driver wext
> >
> > wext is deprecated, use nl80211 instead.
>
> thanks for your reply.
>
> I am now using the driver nl80211 and everything works again. But if I
> apply the changes to the wpa_supplicant configuration I'm getting these
> errors http://pastebin.com/GYW0mng2 in a endless loop.
you might need a recent version of wpa_supplicant as well - AFAIK v2.0 or
higher. If that is already installed, please let us know your kernel version
and wpa_supplicant version.
Cheers,
Simon
next prev parent reply other threads:[~2013-11-15 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 9:18 WPA_Supplicant: no unicast with wpa encryption mkettn
2013-11-15 9:42 ` Nicolas Cavallari
2013-11-15 13:16 ` Mark Kettner
2013-11-15 15:12 ` Simon Wunderlich [this message]
2013-11-22 9:30 ` Mark Kettner
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=201311151612.50894.sw@simonwunderlich.de \
--to=sw@simonwunderlich.de \
--cc=Nicolas.Cavallari@lri.fr \
--cc=linux-wireless@vger.kernel.org \
--cc=mkettn@technik-emden.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.