pd) (and experimentation to
verify it does 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 int
Association ID for the station and the exact value
depends on what other stations are currently associated. The only area
where this would have an effect during the association is in power
saving (buffered frames on the AP are indicated for a specific AID).
--
Jouni Malinen
the log so it is not something that is enabled by default, but it
sounds like 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 M
e, so there was no DHCP 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
d the logs to avoid future passwords for any other
network getting 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
or
ifconfig mon0 up
dumpcap -i mon0 -w /tmp/capture.pkt
And then run the success/failure case.
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
, it would be quite helpful since it
could make it easier to try to reproduce this if there is indeed
something 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
connect to the network with wpa_supplicant and after
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 Malinen
me of those were because 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/mailma
er
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 MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
unfortunately ugly
and I'd assume almost no station implements this in a way that would
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
__
On Mon, Feb 23, 2015 at 12:06:09PM -0800, Linus Torvalds wrote:
> On Mon, Feb 23, 2015 at 9:17 AM, Jouni Malinen 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, bu
rate, so this
specific item is mainly applicable 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
_
On Mon, Feb 23, 2015 at 03:00:39PM -0800, Linus Torvalds wrote:
> On Mon, Feb 23, 2015 at 2:43 PM, Jouni Malinen 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
&g
here could be defined as 6 Mbps OFDM for 5 GHz
band and either that or maybe even 2 Mbps or 5.5 Mbps on 2.4 GHz (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
that for IEEE80211_TX_CTL_RATE_CTRL_PROBE which seemed to
get set for the initial EAPOL frames. 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 r
stablished in more cases and this can result in relatively
functional network connection 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
ifferent rates indicated in the first
three values and nothing else. With RC probing (which happens to occur
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 previo
EAPOL-Key msg 4/4 retries without 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
On Tue, 2010-12-28 at 22:32 -0800, Mohammed Shafi wrote:
> On Wed, Dec 29, 2010 at 11:40 AM, Robert Chan
> 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 IBSS + N + mesh)?
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 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 differenc
pied by skb_copy?
> If we do see performance differences on different platforms, this could
> 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
On Sun, Jan 09, 2011 at 09:14:53PM +0100, Christian Lamparter wrote:
> On Sunday 09 January 2011 19:13:04 Jouni Malinen wrote:
> > For the order-1 allocation issues, it would be interesting to see if
> > someone could take a look at using paged skbs or multiple RX descriptors
> &
;ve been thinking of adding 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
__
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
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 wit
On Wed, 2011-02-16 at 02:01 -0800, Timothy Smith wrote:
> I'm not sure if this specific to the ath9k drivers, or a general problem
> across many, but I have seen it here so I'll report it here first. It's
> actually been the case for quite a while and IIRC the ath5k does this too,
> but
> I hav
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 sho
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 d
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 Wed, 2011-02-23 at 10:40 -0800, Adrian Chadd wrote:
> The trouble is, I don't know if this macbook pro NIC (some broadcom
> 11n thing) is handing over garbage frames or not. I know it sometimes
> shows frames from ath9k with incorrect FCS, but that could be in-air
> garbage. So it's entirely po
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) wa
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 lo
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, i
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;
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 Thu, 2011-02-24 at 03:52 -0800, Peter Stuge wrote:
> Quick grep rfkill -r /lib/rc* /etc/init.d comes up empty.
It is done with iwconfig. iwconfig_post_stop and failure in
iwconfig_pre_start results in "iwconfig wlan# txpower off" getting
executed. This results in soft blocking the interface.
i
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 Andrews wrote:
> >> Is DELAYED-BA implemented?
> >
> > need to check it out. Can you please explain what are you trying to do ?
>
> I am using ath9k
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
do
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
dition, if this is really needed, 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
l is concerned, it
would much better 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
e
allowed, HT could be disabled. Though, a cleaner mechanism would likely
be to just provide an explicit attribute 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_suppl
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 MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
justification for the
improvement (and anything with WEP in it is unlikely to be considered
good justification in 2011 ;-).
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
ith the channel obviously set to the one that the AP is using)
Then try to connect the AR9285-based station and once that fails, kill
tcpdump and send 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 wi
iffer? It would be interesting to see
sniffer capture both for a successful and failed connection attempts.
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
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
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
ly the most secure design out
there, the proper way of addressing this would be to use CCMP instead of
frequent rekeying with TKIP..
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
s is not
> the case. The PTK just happens to come from the
> configuration.
Well, this is a valid configuration in theory, but not really something
that is normally used and I would recommend using WPA2 with CCMP and
leaving out the PTK rekeying
of user space upgrades with kernel changes without a very good
reason.
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
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
>
nt and that can be used with ath9k. The main missing
functionality in ath9k is the new power saving mechanisms defined in the
P2P specification.
--
Jouni MalinenPGP id EFC895FA
___
ath9k-devel mailin
On Aug 15, 2008, at 3:37 AM, Kevin Mitchell wrote:
> I get the slighlty disturbing message "wireless event too big"
> whenever I associate with my router at home (Dlink DIR-655) with my
> ar5418 chip that's sitting in one of the PCIe slots of my T60. It does
> not appear to cause any immediately
On Aug 20, 2008, at 9:57 AM, Alexandros C. Couloumbis wrote:
> ath5k with hostapd is working fine with the patch Juri Slaby provided:
> https://lists.ath5k.org/pipermail/ath5k-devel/2008-August/001224.html
>
> was wondering is something similar is possible for the ath9k driver.
I've already sent
On Aug 20, 2008, at 7:46 PM, Alexandros C. Couloumbis wrote:
> it works! I posted some benchmarks on the openwrt forum:
> http://forum.openwrt.org/viewtopic.php?pid=72503#p72503
>
> I am unable though to set hostapd for 802.11a
Nice to hear that the AP mode worked for you. I haven't tested
80
On Aug 29, 2008, at 9:32 AM, Mats Johannesson wrote:
> Plain kernel 2.6.27-rc5 (as well as -rc4 and -rc3) works very well,
> but
> applying the http://w1.fi/wireless-testing/ patches dated 28-Aug-2008
> 05:09 as per the "series" file (only those marked as "Submitted for
> inclusion; no known op
On Aug 29, 2008, at 3:54 PM, Mats Johannesson wrote:
> Built wireless-testing and applied w1.fi patches
> (mac80211_iwassocreqie.patch and mac80211_fix_debugfs_netdev.patch
> were
> in Linville's tree...)
> As with the -rc5+w1.fi combo the wireless-testing+w1.fi show less
> sensitivity than a
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
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 wpa
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 t
Fix a memory leak where AP mode did not free transmitted Beacon frame
skbs.
Signed-off-by: Jouni Malinen <[EMAIL PROTECTED]>
Index: wireless-testing/drivers/net/wireless/ath9k/beacon.c
===
--- wireless-testing.orig/drive
offset is to disable
staggered Beacon frames for now. We need to redesign beacon.c anyway
when adding multi-BSS support with mac80211 since the existing code
depends on different mechanism for Beacon frame transmission.
Signed-off-by: Jouni Malinen <[EMAIL PROTECTED]>
Index: wireless-testing/d
d in more detail to make it easier to understand how the
padding length is calculated.
Signed-off-by: Jouni Malinen <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/recv.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
--- wireless-testing.orig/drivers/net/wireless/at
On Thu, 2008-12-11 at 11:49 -0800, Bob Copeland wrote:
> On Thu, Dec 11, 2008 at 11:22 AM, Jouni Malinen
> wrote:
> > The 802.11 header is only padded to 32-bit boundary when the frame has
> > a non-zero length payload.
> Thanks Jouni, that clears up the question of t
On Tue, 2008-12-30 at 03:06 -0800, Adam Tistler wrote:
> I would like to get a wireless N pci card and use the ath9k drivers.
> I would like for it to serve as an AP as in my previous setup.
> I read that there are a few patches available for ath9k/AP mode. What
> is the current state of developm
On Tue, 2008-12-30 at 10:50 -0800, Jens Ott - Opteamax wrote:
> but when I try to set device to master (ap) mode I only get:
>
> acapulco ~ # iwconfig wlan0 mode master
> Error for wireless request "Set Mode" (8B06) :
> SET failed on device wlan0 ; Invalid argument.
mac80211 does not support
invalid configuration.
Signed-off-by: Jouni Malinen
---
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/wireless/ath9k/Kconfig 2009
On Wed, 2009-01-14 at 05:24 -0800, Paul Koan wrote:
> I am using a Linksys WMP300N (AR5146 + AR2133, 168c:0023) with a WRT610N
> access point. The access point is set to N only, using WPA2-Personal.
It would be interesting to understand how exactly the AP is enforcing
the "N only" part taken in
On Fri, 2009-01-16 at 06:23 -0800, Mark Schloesser wrote:
> Now... If i understand this correctly the atheros cards (old madwifi
> driver and also ath5k/ath9k) are able to bring up multiple interfaces so
> you can serve as AP and be a client station in parallel - or even could
> serve two access p
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.
>
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 sugg
On Wed, 2009-02-04 at 01:51 -0800, Amit Sood wrote:
> was unable to find libnl2.0 anywhere. I saw makefile under iw has a check
> for this library. Any idea how I can get this library?
libnl 2.0 has not been released yet. Why would you like to find it?
- Jouni
On Wed, 2009-02-04 at 21:17 -0800, takuan wrote:
> Sorry for the simple question but I have looked all over and could not
> find much information about how to get WPA working with ath9k.
> wpa_supplicant.conf:
> ap_scan=2
Change that to ap_scan=1
- Jouni
___
parameters are passed into PHY through the PHY-SAP 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 Malinen
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
On Thu, 2009-02-05 at 17:33 -0800, takuan wrote:
> Thanks for the reply, however I have tried ap_scan=1 and ap_scan=0
> with no luck.
> When I set it to 1 it just goes in an infinite loop scanning for APs
> although the SSID of my AP is not being broadcast so it probably will
> not find it.
You wi
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
suppo
On Tue, 2009-02-17 at 09:28 -0800, Stephen Gutknecht (hilltx) wrote:
> Any and all walkthroughs of constructing ht_capab appreciated ;)
>
> With 0.6.7 we had default which gave us G-only. Or we could revise
> hostapd config with:
>
> ieee80211n=1
> ht_capab=[SHORT-GI-20][TX-STBC][RX-STBC12][DEL
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: disasso
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-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
_
probably work yet, so 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@list
On Mon, 2009-03-16 at 05:35 -0700, Valmantas Palikša wrote:
> When i set ht_capab=[HT40+][SHORT-GI-40][DSSS_CCK-40] in hostapd, client
> connects fine, but datarates are quite bad, about ~1-2MB/s. In contrast
> when i set htcapab= , I get about 5-9MB/s when transferring AP->client.
>
> PS. The int
On Tue, 2009-03-24 at 08:58 -0700, ming li wrote:
> I asked this some time back but did not get any reply. I am just
> wondering if there is any easy way to implement adhoc-demo mode in
> ath9k.
This should not be in any way specific to ath9k, i.e., this type of
functionality can be implemented in
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 ha
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:
> https://lists.ath9k.org/pipermail/ath9k-devel/2009-January/00
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
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=4
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 th
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 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. Th
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
usin
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, th
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 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'
> val
On Tue, 2009-05-19 at 03:45 -0700, Gabor Juhos wrote:
> Ok, I will wait for the patches then.
I just submitted the patches and they are also available from
http://w1.fi/p/ps/
After implementing additional debugging functionality, I did find number
of issues with ath9k touching the hardware when
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 a
1 - 100 of 132 matches
Mail list logo
