From: Nicolas Cavallari <Nicolas.Cavallari@lri.fr>
To: mkettn@technik-emden.de
Cc: linux-wireless@vger.kernel.org
Subject: Re: WPA_Supplicant: no unicast with wpa encryption
Date: Fri, 15 Nov 2013 10:42:36 +0100 [thread overview]
Message-ID: <5285EC8C.3050708@lri.fr> (raw)
In-Reply-To: <20131115101803.66967a4e@mke-x61t>
On 15/11/2013 10:18, mkettn@technik-emden.de wrote:
> Hello,
>
> I want to use wpa_supplicant to encrypt a ad-hoc network with WPA.
> Each device is also a router (using babeld).
> With encryption the support for unicast packages drops. I've used
> tshark to monitor the traffic of two devices (A and B):
>
> when A wants to ping B it broadcasts a ask for the MAC-address of B.
> B sends the MAC-address successfully but A doesn't care.
>
> I see the reply of B in tshark (running on B), but the ARP-package
> doesn't show up on tshark on A.
>
> this only happens with wpa_supplicant enabled.
>
> The wpa_supplicant.conf looks like this:
> ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
> update_config=1
>
> # use 'ap_scan=2' on all devices connected to the network
> ap_scan=2
>
> network={
> ssid="mesh-wpa"
> mode=1
> frequency=2432
> proto=WPA
> key_mgmt=WPA-NONE
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.
next prev parent reply other threads:[~2013-11-15 9:42 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 [this message]
2013-11-15 13:16 ` Mark Kettner
2013-11-15 15:12 ` Simon Wunderlich
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=5285EC8C.3050708@lri.fr \
--to=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.