gmane.linux.drivers.hostap

Re: [PATCH] hostapd: Remove redundant freeing of STA list entries

Mohammed Shafi Shajakhan — 2013-05-21T05:16:55

no Jouni, its a cleanup, haven't found any issue that this fixes.

Re: [PATCH] P2P: Add IFNAME=iface command option for interfaceredirection

Dmitry Shmidt — 2013-05-21T00:59:33

I like idea to have global interface to control everything. However,
it looks like it doesn't understand
"usual" interface commands like:

root< at >manta:/ # wpa_cli -g < at >android:wpa_wlan0
Interactive mode
UNKNOWN COMMAND
Unknown command 'IFNAME=wlan0'
OK
...

I understand that it was not your original design direction, but it
will be easier for wifi manager to
have one socket control and one socket monitor.

Re: Hostapd and wpa_supplicant frequency range

Holger Schurig — 2013-05-20T19:58:22

It's the kernel driver and the optional CRDA that tell the kernel
which channels/frequency are allowed and with what parameters. Do "iw
wlan0" to see what frequencies your card (with your current driver)
supports.

2013/5/20 Sotaro Watanabe <sotarowatanabe< at >gmail.com>:

Re: Not reassociating after a 4-way Handshake 'Retry limit 4 reached'

Douglas Diniz — 2013-05-20T14:56:00

Noone?


On Tue, May 14, 2013 at 2:08 PM, Douglas Diniz <dgdiniz< at >gmail.com> wrote:

Hostapd and wpa_supplicant frequency range

Sotaro Watanabe — 2013-05-20T14:21:49

Good afternoon, I'm Watanabe,Sotaro,

Currently am I working with some experimental wifi cards, which support
6GHz bands. In that sense, I would like to know whether or not hostapd and
wpa supplicant might work in that range.

Looking into the code, I have found some files where such a frequency range
are defined, but I don't know if those files are all of the them or just a
few of a whole set, might be possible to know what are all the files which
contain the frequency working range of hostapd and wpa supplicant?

On the other hand, I would wish to know whether I might extend these ranges
will lead to a proper work of hostapd and wpa supplicant.

Thank you so much,


Watanabe.
_______________________________________________
HostAP mailing list
HostAP< at >lists.shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap

RE: [PATCH 03/20] driver: nl80211: hold wdev identification for P2Pdevice

Peer, Ilan — 2013-05-20T07:05:12



I meant put both attributes :) I think that even older kernel versions can handle this.

Re: [PATCH 06/20] wpa_s: p2p: create P2P Device interface if supported

Arend van Spriel — 2013-05-19T21:16:46

wpas_p2p_add_p2pdev_interface() does a wpa_supplicant_add_iface() with 
iface->p2p_mgmt set to 1. So wpas_p2p_init() is only called for the P2P 
Device wpa_s or for the first interface specified on the command line in 
case driver does not support P2P_DEVICE.

Re: [PATCH 03/20] driver: nl80211: hold wdev identification forP2P device

Arend van Spriel — 2013-05-19T21:13:48

That was my initial take as well, but Johannes pointed out to keep 
wpa_supplicant usable for kernel version with wdev_id.

Re: [PATCH 00/20] wpa_s: p2p: support nl80211 P2P_DEVICE interface

Arend van Spriel — 2013-05-19T21:09:06

Thanks, Jouni

I will have a look at the devel branch. Will not be until tuesday though 
due to holiday. What would be needed to run your hwsim tests if I want 
to look into that.


Ok. I put p2p_mgmt flag in wpa_supplicant struct, which could be used to 
skip creating a control interface for it if it is preferred to keep the 
behaviour the same. I forgot to mention, but there may be more stuff 
that is not really needed for this type of interface (eg. eapol related 
stuff) that I left as is.

Gr. AvS

Re: [PATCH] hostapd: Remove redundant freeing of STA list entries

Jouni Malinen — 2013-05-19T19:28:24

Probably not for most use cases, but it could potentially be used for
RSN pre-authentication testing where a STA entry may be created.

Does this patch fix something or is it just cleanup?

Re: [PATCH] wpa_s: p2p: rework creation order of P2P Device interface

Jouni Malinen — 2013-05-19T19:26:26


Thanks. I merged this into the pending commits in the devel branch.

Re: [PATCH 00/20] wpa_s: p2p: support nl80211 P2P_DEVICE interface

Jouni Malinen — 2013-05-19T19:08:15

Thanks. I started applying commits, but had to stop with that pretty
quickly since this broke number of things in my tests (including hostapd
build and wpa_supplicant start).. I think I managed to fix most of the
issues, but this still does not work in my hwsim tests.

I did quite a bit of cleanup and re-ordering of commits etc. to avoid
breaking things in the middle of series. It is possible that I may have
broken something here, but I didn't find what it could be. As such, I
did not push any of this into the master branch yet, but you can find
the latest version I tested with in the devel branch. It would be
helpful if you could verify whether it still works for you. It should be
noted that I did not get the unmodified versions working either (after
fixing the TDLS startup issue with a one-liner), so I'm not completely
sure what to expect from these changes with mac80211_hwsim.

One thing that came up, though, is that this is likely to break upper
layer expectations since this changes default behavior by

RE: [PATCH 08/20] driver: nl80211: handle creation of P2P deviceinterface

Peer, Ilan — 2013-05-19T18:15:08



Can't we simply have this for all the interfaces types? Is there something wrong we having to keep wdev in all cases?

RE: [PATCH 06/20] wpa_s: p2p: create P2P Device interface if supported

Peer, Ilan — 2013-05-19T18:14:12



I might be missing something here, but in this flow, where is wpas_p2p_init()called?

RE: [PATCH 03/20] driver: nl80211: hold wdev identification for P2Pdevice

Peer, Ilan — 2013-05-19T18:13:18



The title of the patch might be a bit misleading :)


It is possible to always add both attributes (and this can actually be done for all the nl commands ...). The kernel should be able to handle this.


It might be better to get both IFINDEX and WDEV id, and then have only a single iteration and do similar processing as in process_global_event(). Otherwise, you might miss a case where the ifindex is -1 but a bss with a valid wdev_id is not the first in the list

Re: [RFC] nl80211: allow Android P2P functionality

YanBo — 2013-05-19T15:10:16

On Fri, May 17, 2013 at 2:50 AM, Johannes Berg
<johannes< at >sipsolutions.net> wrote:
Yes, it works, after create the combination station/P2P device in the
driver, now the android can success call the patched wpa_s to wake up
the p2p0 and wlan0 interface. (although I still use the manual way to
create the p2p0 ) Thanks a lot.

BR /Yanbo

Re: [PATCH] P2P: Add IFNAME=iface command option for interfaceredirection

Jouni Malinen — 2013-05-18T17:07:21


The part of making control interface commands available through a single
socket sounds reasonable, but I'm not sure whether use of per-interface
socket for this is the best design for it. At least in theory, there
could be different security policies configured for network interfaces
and this design would by-pass such differences. In addition, the concept
of directing commands through another control interface at network
device level does not look correct.

I added a similar mechanism, but using the global control interface
instead of the per-network interface ctrl_iface. In addition to just
handling commands, there is no also support for attaching a monitor
socket on top of the global control interface to get events from all
network interfaces that the wpa_supplicant process controls. There is
also concept of global operations that are not specific to any network
interface, so that it is possible to run P2P Device operations (like
P2P_FIND and P2P_CONNECT) through the control interface without having
to s

Re: Error with Kernel 3.9

Softy — 2013-05-18T16:09:30

Hello again ... sorry to dredge this up, I was wondering if there was any
more ideas on how to get hostapd working with an rtl8187 in a 3.9 kernel?

I've tried 3.10rc1, and will be trying 3.8 in a moment.  Things do work
correctly using kernel 3.2.29 which I would be happy to use, however that
kernel doesn't support the touch screen on the laptop which the newer
kernels do and hence the desire to "have it all" in using the newer kernels.

I've pastebin'd iw dev output and some other data.  Please let me know if
anything else would help.  Any suggestions on possible things to try would
be great.

http://pastebin.com/zHGadqYC

-daniel



On Mon, May 13, 2013 at 7:15 PM, Softy <softservant< at >gmail.com> wrote:

_______________________________________________
HostAP mailing list
HostAP< at >lists.shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap

Re: WPA_supplicant trouble connecting client to AP

Francisco Cuesta — 2013-05-17T05:58:17

2013/5/16 Dan Williams <dcbw< at >redhat.com>:

The output of a complete cycle that I get are the following:

 wlan1: State: DISCONNECTED -> SCANNING
1315503198.069739: Scan SSID - hexdump_ascii(len=18):
     69 72 74 2d 61 68 2d 69 6e 72 69 61 2d 73 69 65   <SSID>
     62 65                                             <SSID>
1315503198.070008: wlan1: Starting AP scan for wildcard SSID
1315503198.070078: nl80211: Scan SSID - hexdump_ascii(len=18):
     69 72 74 2d 61 68 2d 69 6e 72 69 61 2d 73 69 65   <SSID>
     62 65                                             <SSID>
1315503198.070326: nl80211: Scan SSID - hexdump_ascii(len=0): [NULL]
1315503198.070529: Scan requested (ret=0) - scan timeout 30 seconds
1315503198.070632: nl80211: Event message available
1315503198.070693: nl80211: Scan trigger
1315503201.436117: RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
1315503201.436206: netlink: Operstate: linkmode=-1, operstate=6
1315503201.436408: The number of sent bytes  in netlink_send_oper_ifla are 37
1315503201.4

Re: [PATCH] hostapd: Remove redundant freeing of STA list entries

Mohammed Shafi Shajakhan — 2013-05-17T05:19:14

Hi Jouni,

On Thu, May 16, 2013 at 08:55:00PM +0300, Jouni Malinen wrote:

does driver=none maintains a sta list ?

Re: [RFC] hostapd: Fix pointer assignment for new iface alloc

Mohammed Shafi Shajakhan — 2013-05-17T05:15:09

sorry, misread the code. thanks for the review.

shafi