? And if so, what are those use cases? Or is this only for some
public safety cases? And if so, for which regulatory domains?
To be frank, I really don't see how this would be even close to a state
that should be accepted into the upstream tree.
--
Jouni Mal
generate the explicit rules to enable the licensed bands and
only distribute the regdb with these changes to properly licensed users)
was one of the approaches discussed in the past for this type of use
cases.
--
Jouni Malinen
are somewhat in conflict with the
needs of regulatory rule enforcement for most other use cases.. :)
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
ld configuration parameter. We must prevent accidental use of
these channels regardless of what config options a user might pick.
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
encryption patch
is concerned, I think I have enough concern on the couple of corner
cases that I know it does not address (and may break), so it may take
some more time before I'm ready to suggest it (or a bit modified version
of it) to be applied, though.
--
Jouni Malinen
and rate control can handle the less
critical data frames through whatever means to get optimal throughput
from the network. As such, I do think we do need to paper over this
for EAPOL frames.
--
Jouni MalinenPGP id EFC895FA
for the initial EAPOL frames, this results in only one attempt at
MCS(0) and two + two attempts at MCS0. No non-MCS rates are tried. As
pointed out previously, this is likely fine for normal data frames, but
not for EAPOL.
--
Jouni MalinenPGP id EFC895FA
(if
included by the AP in basic rate set).
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
. I guess this could be done more
generically for all EAPOL frames.
- change their mrr setup to be more conservative
That mrr[3]:= basic_rate is the part I was really asking for as far as
EAPOL frames are concerned.
--
Jouni MalinenPGP id EFC895FA
frame with the new pairwise key.
This is somewhat ugly, but doable. (Though, this would be yet another
justification for finally trying to come up with an alternative
mechanism for handling EAPOL frame TX/RX that is really a special case
for IEEE 802.1X.)
--
Jouni Malinen
handle all cases cleanly (i.e., just hope for msg 4/4 to go through and
reassociate as a backup plan if things fail..).
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
On Mon, Feb 23, 2015 at 12:06:09PM -0800, Linus Torvalds wrote:
On Mon, Feb 23, 2015 at 9:17 AM, Jouni Malinen j...@w1.fi wrote:
mac80211: Do not encrypt EAPOL frames before peer has used the key
Hmm. This patch does not seem to make a difference. I thought it did
at first, but then removed
only to driver that use minstrel from
mac80211 (e.g., ath9k). Though, that IEEE80211_TX_CTL_USE_MINRATE would
likely affect most mac80211 drivers.
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k
On Mon, Feb 23, 2015 at 03:00:39PM -0800, Linus Torvalds wrote:
On Mon, Feb 23, 2015 at 2:43 PM, Jouni Malinen j...@w1.fi wrote:
This did not get exactly supportive response when this was proposed last
time (Sep 2013). Anyway, for a quick test, this can be done with the
following one
couple of reconnections, stop wpa_supplicant and dumpcap. That
/tmp/wlan.pcap should have most of the frames exchanged between the
devices.
You can then remove the monitor interface with:
sudo iw mon0 del
--
Jouni MalinenPGP id EFC895FA
of the sniffer not seeing them rather than
them not being transmitted.
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k
/failure case.
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
special about that AP behavior that allows the issue to show
up but does not show up in the wpa_supplicant debug log.
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https
an effect during the association is in power
saving (buffered frames on the AP are indicated for a specific AID).
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https
this is fine here and it will include the details that would
be needed to check what exactly are the differences in the 4-way
handshake between NM and manual wpa_supplicant configuration cases.
--
Jouni MalinenPGP id EFC895FA
issues
here (didn't get that far).
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
written into a log file..)
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
not break deployed stations badly).
To prevent 802.11b stations from associating: add one of the OFDM rates
(say, 6 Mbps) into basic_rates parameter into hostapd.conf.
To allow only HT stations, add require_ht=1 into hostapd.conf.
--
Jouni MalinenPGP
version were you using in the failure case? Based on your
follow up message, the current hostap.git snapshot does not have this
issue which is good in itself, but still, we should not be forcing this
type of user space upgrades with kernel changes without a very good
reason.
--
Jouni Malinen
On Mon, Jan 02, 2012 at 11:00:11AM +0100, Thomas Hilber wrote:
On Mon, Jan 02, 2012 at 11:28:30AM +0200, Jouni Malinen wrote:
Which hostapd version were you using in the failure case? Based on your
it's debian 6.0 stock version of hostapd installed via
'apt-get install hostapd'. According
and I would recommend using WPA2 with CCMP and
leaving out the PTK rekeying (which is really just a workaround for not
so secure TKIP).
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel
this is related to rekeying?
May I ask why you have configured the station to force PTK rekeying
every 10 minutes? While TKIP is not really the most secure design out
there, the proper way of addressing this would be to use CCMP instead of
frequent rekeying with TKIP..
--
Jouni Malinen
On Fri, Oct 28, 2011 at 06:26:53AM +0200, Julien Valroff wrote:
Le jeudi 27 oct. 2011 à 22:27:58 (+0200 CEST), Jouni Malinen a écrit :
Which drivers did you use in these tests?
brcmsmac and b43
brcmsmac does not support monitor mode. b43 is claimed to support that,
but I've never tried
On Thu, Oct 27, 2011 at 09:13:53PM +0200, Julien Valroff wrote:
Le jeudi 27 oct. 2011 à 20:36:06 (+0200 CEST), Julien Valroff a écrit :
Le lundi 24 oct. 2011 à 21:55:01 (+0200 CEST), Jouni Malinen a écrit :
ifconfig wlan0 down
iw wlan0 set type monitor
iw wlan0 set channel 6 HT20
the capture log. If you can easily run this twice,
i.e., first with the success case where the station connects as the
first device and then with the failure case, this would be even more
valuable since it would make it easier to compare the message sequences.
--
Jouni Malinen
dynamic WEP functionality
does not sound like a good direction.
If the goal here was to improve station mode functionality in the case
where a single WEP network is being used, it should be done more
carefully to avoid causing problems to other cases.
--
Jouni Malinen
;-).
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
to do that as a parameter for the connection (e.g.,
new nl80211 attribute for NL80211_CMD_ASSOCIATE) rather than a module
parameter. This workaround seems to be needed with some APs and global
disabling of 802.11n does not sound like the ideal mechanism for that.
--
Jouni Malinen
to disable 802.11n. If that is
done outside the scope of a single connection, that would be available
as a manual workaround even without modifications to
wpa_supplicant/NM/ConnMan.
--
Jouni MalinenPGP id EFC895FA
, why would this be a driver
specific hack rather than providing a shared mechanism in mac80211 to
disable 802.11n support? It would sound strange if there would need to
be a new module parameter in every 802.11n driver to handle something
like this.
--
Jouni Malinen
On Wed, 2011-03-23 at 06:46 -0700, Duccio Mangiavacchi wrote:
Hi, i add lines ieee80211n=1
ht_capab=[HT40-][SHORT-GI-40][DSSS_CCK-40] in hostapd.conf to enabled
N , i have Linksys 300WP300N, with Ar5008 in AP mode master, but my
laptop would use Wep now, Why? And if i use wep in AP mode n,
On Tue, 2011-03-22 at 16:35 -0700, Duccio Mangiavacchi wrote:
Hi, i have an idea if in hostapd.conf it's possible to configure
hw_mode=n, or automatic b,g,n?
In practice, hw_mode is used to select between 2.4 GHz and 5 GHz. IEEE
802.11n is enabled with a separate parameter (ieee80211n=1) as
On Fri, 2011-02-25 at 09:08 -0800, Thomas Andrews wrote:
On 02/25/2011 06:15 PM, Mohammed Shafi wrote:
On Fri, Feb 25, 2011 at 2:32 PM, Thomas Andrewstandr...@grok.co.za wrote:
Is DELAYED-BA implemented?
need to check it out. Can you please explain what are you trying to do ?
I am
On Thu, 2011-02-24 at 01:15 -0800, Cedric Sodhi wrote:
PS, if that matters: When I observe the ERFKILL status with rfkill I get
a
idx 0 type 1 op 2 soft 0 hard 0
idx 0 type 1 op 2 soft 0 hard 0
every time I restart /etc/init.d/net.wlan1.
Those lines are saying that WLAN (type 1) was
On Thu, 2011-02-24 at 01:39 -0800, Cedric Sodhi wrote:
Oh I'm a fool, I made a typo, the two lines that I get with rfkill event
are
idx 0 type 1 op 2 soft 1 hard 0
idx 0 type 1 op 2 soft 0 hard 0
The interesting part about that is the block being soft, not hard.. In
other words, this looks
On Thu, 2011-02-24 at 01:58 -0800, Cedric Sodhi wrote:
I hope I understood you correctly. If you want me to run rfkill list
at the very moment between those two 132 errors, that could be difficult
as they appear very quickly after eachother
Yes, I think you understood correctly. However, it
On Thu, 2011-02-24 at 01:55 -0800, Cedric Sodhi wrote:
You mean capture log as in a log with wireshark? I'm really
unexperienced in that field. If you could tell me what program I need I
can do my best.
I meant running another wireless LAN card in monitor mode (e.g.,:
ifconfig wlan0 down; iw
On Thu, 2011-02-24 at 03:21 -0800, Cedric Sodhi wrote:
Why would it do that? To be frank I doubt your diagnosis at this point,
how did you come to conclude that?
I have no idea why it would do that; you would need to ask Gentoo
developers that. I concluded this by checking what my test laptop
On Wed, 2011-02-23 at 10:20 -0800, Adrian Chadd wrote:
in fact, I lie - it's ath9k seemingly sending two ACKs for the same
frame.
I don't remember having seen that and cannot really think of any reason
that would cause this type of behavior. Would you happen to have a
wireless capture file
On Wed, 2011-02-23 at 12:46 -0800, Cedric Sodhi wrote:
in dmesg. When I restart /etc/init.d/net.wlan1 I get, after
wpa_supplicant is said to start
SIOCSIFFLAGS: Unknown error 132
SIOCSIFFLAGS: Unknown error 132
Error 132 is ERFKILL, i.e., something in the system disabled the
wireless
On Wed, 2011-02-23 at 13:49 -0800, Peter Stuge wrote:
In my case no. I have gotten both minipci ath9k card and cardbus
ath5k stuck in reporting 132 on ip l s dev .. up IIRC both after
using wpa_supplicant and only using iw manually.
I'm not sure what could trigger this apart from the most
On Mon, 2011-01-24 at 14:33 -0800, Ben Greear wrote:
So, I am hoping for some guidance from the core ath9k folks. Should
I attempt to fix my copybreak patch for non pci busses and re-post
it?
My preference would be to use multiple RX buffers to receive long frames
(chain RX descriptors with
On Thu, 2011-01-20 at 10:27 -0800, Ben Greear wrote:
Seems I saw a note a long time ago about virtual wiphy being
removed sometime soon. Should we go ahead and remove it?
It doesn't seem useful to me (virtual interfaces appear to
work much better), and it would likely simplify the code
a
some
kind of mechanism for the driver to override Beacon interval in such
cases (which would need to go back all the way to user space to hostapd
in case of AP mode).
--
Jouni MalinenPGP id EFC895FA
___
ath9k
perhaps be
something we could tune at run-time.
I guess that could be looked at, but as long as that is not the case,
the test setup you used is not exactly the most common case for ath9k in
the upstream kernel and should not be used to figure out default
behavior.
--
Jouni Malinen
On Wed, 2011-01-05 at 14:59 -0800, Lara Deek wrote:
I would please like to ask what are the relevant places for code
change in ath9k for beacon reception and transmission? Also, which
struct can I change to control the contents of a beacon packet?
What are you trying to do? This sounds like
On Fri, 2011-01-07 at 13:55 -0800, Peter Stuge wrote:
I normally never use wpa_supplicant. I don't accept that it would be
required for a working connection and so far noone has really
explained why that would be the case. Only ath9k (ie. neither ipw2200
nor ath5k) has ever made a difference
On Tue, 2010-12-28 at 23:21 -0800, Robert Chan wrote:
As I am implementing a project that requires a 802.11N mesh network at low
(or zero actually, for a poor area deployment) budget. May I ask what is
the progress in that end (mesh over 11N)? Or if I want to jump in, which
part of the
On Tue, 2010-12-28 at 22:32 -0800, Mohammed Shafi wrote:
On Wed, Dec 29, 2010 at 11:40 AM, Robert Chan
robert.chan.l...@gmail.com wrote:
So should I assume that the details here are too updated or are the modes
above are only independently supported (but not able to work together such
as
On Tue, 2010-11-09 at 09:16 -0800, João Maurício wrote:
Thanks for the advices Lorna. The thing is that when I'm associated
with an AP with wlan0, when I issue echo add .../wiphy I get
dissassociated after +- 10 secs. It happens even if the newly created
wlan1 stays down, i.e., if I just
On Wed, 2010-10-27 at 04:11 -0700, Lorna González wrote:
I am trying to build a virtual interface (not wiphy) operating in master mode
using hostapd. Using wiphys (echo add ...wiphy) I am able to configurate a
wiphy as station and another one as AP. It works perfectly but by setting the
AP
On Tue, 2010-07-06 at 09:42 -0700, Javier Cardona wrote:
We have a dedicated target for this, so we can quickly test patches or
diffent kernel versions.
May I ask what are you trying to achieve with virtual wiphys? Are you
trying to do multi-channel operations? If not, some other option may be
On Wed, 2010-05-05 at 02:28 -0700, Lorna González wrote:
according to the nl80211_commands it is possible to add, get, set and delete
wiphy using iw command like using debugfs ath9k/phy#/wiphy am I right? But I
can´t use and don´t have this options in my supported commands (iw phy name
On Wed, 2010-05-05 at 07:27 -0700, Rodolphe Marques wrote:
That means that from the OS perspective we would see only one interface
and that the mac80211 would that care of multiple associations in order
to improve overall throughput?
No, this would not change how the actual network devices
On Fri, 2010-04-16 at 03:52 -0700, Johan Hovold wrote:
Frames tagged by hardware with ATH9K_RXKEYIX_INVALID should not
incorrectly be marked decrypted (even if key index in frame is valid).
Have you tested this with static WEP configuration? Or broadcast RX with
WPA? There must be a reason for
On Tue, 2010-03-30 at 10:10 -0700, Curtis Larsen wrote:
freq_list=5180,5200,5220,5240,5260,5280,5300,5320,5745,5765,5785,5805,5825
That list is space, not comma, separated (freq_list=5180 5200 5220 ...).
I would assume that this particular example ends up getting interpreted
as a single
On Sun, 2010-03-28 at 13:57 -0700, Ben Gamari wrote:
Hostapd output with e.g. ht_capab=[HT40+][SHORT-GI-20][SHORT-GI-40]
HT40: control channel: 8 secondary channel: 12
HT40 secondary channel 12 not allowed
Could not select hw_mode and channel. (-1)
wlan0: Unable to setup interface.
I
On Fri, 2010-03-26 at 16:16 -0700, Pavel Roskin wrote:
I confirm that scan_freq is accepted by the current wpa_supplicant but
has no reliable effect. Both ath5k and ath9k connected to an AP on the
channel 6 when scan_freq=2412 was in the configuration file.
scan_freq is not supposed to limit
On Mon, 2010-03-22 at 08:40 -0700, Rodolphe Marques wrote:
When an interface is scanning I notice that it goes through the 5GHz
channels. Is there any way to disable this, so that it only scans in the
11 channels of 11g?
When using nl80211, you can specify the list of channels you want to
On Sat, 2010-03-20 at 14:19 -0700, Curtis Larsen wrote:
At my work the singleSSID supports 802.11n in the 2.4ghz and 5ghz
bands. Even though 2.4 ghz is slower - my laptop chooses 2.4 every
time. Is there a way to force connection to 5ghz or disable 2.4ghz?
I don't think there is currently
On Sun, 2010-03-21 at 09:22 -0700, Curtis Larsen wrote:
Yes, I do run wpa_supplicant. I would love to see a sample config for
this -even though it sounds like it would not work in all areas across
the campus. Still, better than what I have right now.
All you need to do is to add scan_freq
On Tue, 2010-02-02 at 16:08 -0800, Luis Rodriguez wrote:
We have reviewed this. The 64 value came from interoperability
tests against another 802.11n device which had increased delayed BlockAcks
when CTS-to-self was enabled. Although this is a higher value than
what the standard says to use we
currently traveling and cannot
easily try to reproduce this before returning home.
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo
correctly (for other than
Beacon frames).
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
On Sun, 2009-10-18 at 21:08 -0700, Paul Koan wrote:
But the arp doesn't make it out to the rest of the network.
The ath9k card is connected to a Linksys WRT610N, flashed
with dd-wrt, so I can run tcpdump on it.
I don't see the arp requests coming from the media PC arrive
at the wrt610N.
On Sun, 2009-09-27 at 07:49 -0700, Philippe Fontannaz wrote:
I'm trying to set up 2 AP interfaces with my AR9160/AR9106 based card
in order to get both 2/5 Ghz bands available.
I can see then both ssid's but the connection on either one keeps
disconnecting, thus rendering this set up useless.
On Thu, 2009-06-04 at 23:28 -0700, Johannes Berg wrote:
On Fri, 2009-06-05 at 01:41 -0400, Luis R. Rodriguez wrote:
All rate control algorithms agree to send management and no-ack
frames at the lowest rate. They also agree to do this when sta
and the private rate control data is NULL. We
On Tue, 2009-05-26 at 10:46 -0700, Luis Rodriguez wrote:
On Mon, May 25, 2009 at 06:52:41PM -0700, Jeff Hansen wrote:
I found that upgrading from compat-wireless-2009-04-28 to
compat-wireless-2009-05-11 caused a huge degradation in performance in AP
mode. Before (with 04-28), I was able to
On Mon, 2009-05-18 at 13:35 -0700, Gabor Juhos wrote:
I have discovered some weird crashes on various embedded (MIPS, ARM) boards
with
2.6.30-rc5+compat-wireless-2009-05-15. I'm not sure that is the same error
but seems similar at least. The strange thing, that i saw a '0xdeadbeef'
value
On Tue, 2009-05-12 at 01:35 -0700, Davide Pesavento wrote:
I've already reported ath9k's issues with PS multiple times [1] [2]
[3], but the driver hasn't been fixed yet. You can find a verbose
debugging output at [4], I hope that helps in fixing the problem (I
can provide even more info if
On Fri, 2009-04-24 at 07:40 -0700, Nymerion wrote:
Assuming to create multiple VSTAs on different channels, i wonder what
happens to the packets that the APs they are associated with send to
them when they are temporarily paused.
If the frames are actually transmitted on another channel, they
On Mon, 2009-04-06 at 02:35 -0700, Karl Hiramoto wrote:
All of these cases seem to be working
now. What other cases is software encryption needed?
I do not have a full list, but most cases are in combinations of station
and AP mode interfaces being used at the same time. If you are only
using
On Fri, 2009-04-03 at 01:20 -0700, Giorgio Mazzucchelli wrote:
Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=17 dBm
Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=17 dBm
Allowed channel: mode=2 chan=44 freq=5220 MHz max_tx_power=17 dBm
Allowed channel: mode=2 chan=48
On Fri, 2009-04-03 at 01:44 -0700, Karl Hiramoto wrote:
2. essid1=WPA esid2 = open. Everything works in essid1. Windows
XP SP2 client can connect to essid2 but no traffic, only sends EAPOL
packet.
The secondary BSSes that were using open or static WEP did not work
properly since the
On Fri, 2009-04-03 at 04:37 -0700, Karl Hiramoto wrote:
Another case. two WEP APs essid 1 works but essid2 does not (no
traffic flow). an iwlist dev wlan0 on another machine shows the two
AP's with WEP. Windows shows the WEP APs.
Static WEP keys were not configured for secondary BSSes.
On Thu, 2009-04-02 at 07:34 -0700, Karl Hiramoto wrote:
Thanks for the info. I got it to work with an open AP. WPA is not
working though. There is a hostapd error Invalid pairwise cipher (0)
for a very simple config that worked for me before with one AP, and
hostapd 0.6.8
Looks like you
On Wed, 2009-04-01 at 10:46 -0700, Karl Hiramoto wrote:
Hi,
Thanks for all the work. I've got one AP working with kernel 2.6.29 and
ath9k
I was wondering if there has been any change to the multiple ssid
support I see:
On Tue, 2009-03-24 at 09:30 -0700, ming li wrote:
I just want to avoid the control pkts/mechanisms(association, probe,
etc.) in adhoc-mode. Is there any easy way to disable these functions
in ath9k?
No, like I mentioned, this type of change is not in scope for ath9k and
such changes would
it will
be useful to know if these show up in a configuration that someone would
like to use.
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org
On Fri, 2009-03-06 at 00:57 -0800, Gabor Juhos wrote:
This set will correct two compilation errors in master-2009-03-04
of wireless-testing.
Thanks for fixing these and the no-RFKILL build issue! Looks like I
should try to get a build setup for testing ahb.c build myself..
- Jouni
On Tue, 2009-03-03 at 03:58 -0800, Yura wrote:
However, it still doesn't not work right. Connection is almost bad in N mode.
Ping shows 50-90% packet loss, every 2nd or 3rd packet is lost.
Transfer speed is usually only some kBps. Sometimes it improves and seems to
work well and I have ~2
On Fri, 2009-02-27 at 03:38 -0800, Sebastian S wrote:
then I try to associate with my Asus RT-N15 with WPA2-PSK with the
following command:
' wpa_supplicant -Dwext -iwlan1 -c/etc/wpa_workn.conf'
dmesg reports the following:
[ 4297.083963] wlan1: associated
[ 4297.318287] wlan1:
On Tue, 2009-02-17 at 08:48 -0800, Stephen Gutknecht (hilltx) wrote:
A new hostapd was just released as stable, version 0.6.8, and I'm
fighting some issues with it rejecting ht_capab that worked in 0.6.7
at the moment.
hostapd is now rejecting ht_capab options that the driver does not
interface in TXVECTOR
(e.g., DATARATE and MCS). How the MAC sublayer decides how to set these
parameters or even things like how to control the decision process are
very much out of scope.
--
Jouni MalinenPGP id EFC895FA
On Thu, 2009-02-05 at 03:38 -0800, Amit Sood wrote:
Actually I reffred this site to compile and install AP mode and here only I
found about
CONFIG_LIBNL20=y setting in hostapd compilation and I'm unable to compile
with this settings.
I've not got any response from hostapd mailing list yet.
On Thu, 2009-01-22 at 17:25 -0800, Chris Kennedy wrote:
Here's what I've got for the ht_capab= setting in hostapd.conf, which
I'm not fully sure what
it should be for the DWA-552 (AR5416 chip)...
ht_capab=[HT40+][SHORT-GI-40][TX-STBC][RX-STBC12][DELAYED-BA]
[DSSS_CCK-40]
I would suggest
On Wed, 2009-01-21 at 02:11 -0800, W. van den Akker wrote:
I have tested with 1 CPU disabled. Running now for about 2 hours without
hangups (I have several connection drops, but it will reconnect).
I have also tested with 2 CPU's and HT-disabled (noht parameter) but that
had no effect.
So
this invalid configuration.
Signed-off-by: Jouni Malinen jouni.mali...@atheros.com
---
drivers/net/wireless/ath9k/Kconfig |1 +
1 file changed, 1 insertion(+)
--- wireless-testing.orig/drivers/net/wireless/ath9k/Kconfig2009-01-05
13:27:01.0 +0200
+++ wireless-testing/drivers/net
On Wed, 2008-12-03 at 01:27 -0800, David Shwatrz wrote:
I think that I heard that it does support Access Point mode (AP), so
my question is: what is the status of master mode (AP) in ath9k ? Is it
known to work ? (I am willing to use also the driver for the wireless-testing
or ath9k git
On Wed, 2008-11-19 at 09:41 -0800, Tyler W. Mills wrote:
wlan0: associated
wlan0: disassociating by local choice (reason=3)
I get this every few minutes while associated with my AP.
WPA2/TKIP encryption, this has only started happening with the latest
kernel in F10.
Are you using
On Oct 3, 2008, at 2:53 PM, Kevin Mitchell wrote:
So about a month ago, I got a mail from my router (Dlink DIR-655
HW:A2) telling me that firmware 1.20 was available for download. I
believe I had 1.11 before. Hoping to boost my new 11n capability
(thanks so much by the way), I went ahead
96 matches
Mail list logo
