El día Sunday, December 21, 2014 a las 08:46:35AM -0800, Adrian Chadd escribió:
> Ok. You should also update iee80211_sta.c and ieee80211_power.c. I
> fixed some issues there too relating to this.
If I do so it gives:
/usr/src/sys/net80211/ieee80211_sta.c:941:2: error: implicit declaration of
Ok. You should also update iee80211_sta.c and ieee80211_power.c. I
fixed some issues there too relating to this.
-adrian
On 21 December 2014 at 08:40, Matthias Apitz wrote:
> El día Sunday, December 21, 2014 a las 08:07:28AM -0800, Adrian Chadd
> escribió:
>
>> Sweet, which version of -HEAD
El día Sunday, December 21, 2014 a las 08:07:28AM -0800, Adrian Chadd escribió:
> Sweet, which version of -HEAD did you end up updating to?
I'm running HEAD r269739 (from August this year) and updated only
src/sys/net80211/ieee80211_scan.c yesterday night to:
r275964 | adrian | 2014-12-20 20:41:
Sweet, which version of -HEAD did you end up updating to?
-adrian
On 21 December 2014 at 02:17, Matthias Apitz wrote:
> El día Saturday, December 20, 2014 a las 11:41:43AM -0800, Adrian Chadd
> escribió:
>
>> It's a race condition in the scan handling. :(
>>
>> When scan is cancelled (eg bec
El día Saturday, December 20, 2014 a las 11:41:43AM -0800, Adrian Chadd
escribió:
> It's a race condition in the scan handling. :(
>
> When scan is cancelled (eg because something cancels it, or the state
> transitions to IDLE or something because the VAP resets) then it
> should be setting a fl
It's a race condition in the scan handling. :(
When scan is cancelled (eg because something cancels it, or the state
transitions to IDLE or something because the VAP resets) then it
should be setting a flag to cancel things and the VAP should come out
of powerstate.
However, there seems to be som
El día Friday, December 19, 2014 a las 08:13:25AM -0800, Adrian Chadd escribió:
> Right, it's going into "stopped" mode, rather than "completed". It's
> expecting there to be something that'll take the VAP out of power save
> state, but nothing ever happens to do so.
>
> ok. I think I have enough
Right, it's going into "stopped" mode, rather than "completed". It's
expecting there to be something that'll take the VAP out of power save
state, but nothing ever happens to do so.
ok. I think I have enough information to track down a fix. Thanks!
-adrian
On 18 December 2014 at 23:53, Matthi
El día Wednesday, December 17, 2014 a las 06:58:09PM -0800, Adrian Chadd
escribió:
> ...
> Would someone please try this again, but run it with scan debugging
> enabled (wlandebug +scan) ? The scan_task() routine has some useful
> debugging just before it may wake up the VAP; I'd like to see what
Hi,
Ok. I think I understand what's going on.
The net80211 stack didn't always call vap->iv_sta_ps(vap, 0) to wake
things up when it saw something in TIM. In fact, this was for the most
part commented out.
ieee80211_sta_tim_notify() now gets called, but I only use that to
transition from IEEE802
El día Monday, November 03, 2014 a las 09:43:14AM -0800, Adrian Chadd escribió:
> Ah, chances are it's being loaded automatically at startup when devd
> loads your USB wifi module.
>
> Just make sure you've commented out the wlan devices (but not
> options!) and rebuilt your kernel to not have wl
El día Monday, November 03, 2014 a las 09:43:14AM -0800, Adrian Chadd escribió:
> Ah, chances are it's being loaded automatically at startup when devd
> loads your USB wifi module.
>
> Just make sure you've commented out the wlan devices (but not
> options!) and rebuilt your kernel to not have wl
Ah, chances are it's being loaded automatically at startup when devd
loads your USB wifi module.
Just make sure you've commented out the wlan devices (but not
options!) and rebuilt your kernel to not have wlan included.
-adrian
On 3 November 2014 01:55, Matthias Apitz wrote:
> El día Monday,
El día Monday, November 03, 2014 a las 06:46:33AM +0100, Matthias Apitz
escribió:
> El día Sunday, November 02, 2014 a las 10:46:13AM -0800, Adrian Chadd
> escribió:
>
> > It's not forcing the adapter itself into ps mode - it's just net80211
> > doing an off-channel scan thing.
> >
> > Someone
El día Sunday, November 02, 2014 a las 10:46:13AM -0800, Adrian Chadd escribió:
> It's not forcing the adapter itself into ps mode - it's just net80211
> doing an off-channel scan thing.
>
> Someone has to debug/fix this scan hang thing, I'm out of energy atm :(
I'm willing to dig into this and
It's not forcing the adapter itself into ps mode - it's just net80211
doing an off-channel scan thing.
Someone has to debug/fix this scan hang thing, I'm out of energy atm :(
-adrian
On 2 November 2014 07:31, Nathan Whitehorn wrote:
>
> On 11/02/14 07:29, Matthias Apitz wrote:
>>
>> El día S
On 11/02/14 07:29, Matthias Apitz wrote:
El día Sunday, November 02, 2014 a las 07:24:02AM -0800, Nathan Whitehorn
escribió:
Are you running wpa_supplicant? If you can connect to a plain network
with ifconfig, these will stop.
-Nathan
I do run wpa_supplicant. But I don't understand what you
El día Sunday, November 02, 2014 a las 07:24:02AM -0800, Nathan Whitehorn
escribió:
> Are you running wpa_supplicant? If you can connect to a plain network
> with ifconfig, these will stop.
> -Nathan
I do run wpa_supplicant. But I don't understand what you mean with "If
you can connect to a pla
Are you running wpa_supplicant? If you can connect to a plain network
with ifconfig, these will stop.
-Nathan
On 11/02/14 01:46, Matthias Apitz wrote:
Hi,
I do not understand why I have these 'powersave on/off' transitions:
Nov 2 09:01:06 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power
Hi,
I do not understand why I have these 'powersave on/off' transitions:
Nov 2 09:01:06 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode
on
Nov 2 09:01:08 unixarea kernel: wlan0: [00:13:f7:0d:08:48] sta power save mode
off
Nov 2 09:06:08 unixarea kernel: wlan0: [00:13:f7:0d:0
El día Sunday, October 26, 2014 a las 08:36:05AM +0100, Matthias Apitz escribió:
> # ifconfig wlan0 list sta
> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG
> 00:13:f7:0d:08:4827 54M 35.50 1219 64016 EPS AE RSN
>
> the kernel is 11-CURRENT (r269739) and I
El día Monday, September 08, 2014 a las 03:17:08PM -0700, Adrian Chadd escribió:
> Please compile your kernel with IEEE80211_DEBUG, then enable debugging
> - wlandebug +state +power
>
> You can disable powersave with 'ifconfig wlan0 -powersave', but it
> shouldn't be enabled by default.
Hi,
I w
On Tue, Sep 9, 2014 at 1:33 AM, Kevin Lo wrote:
> On Mon, Sep 08, 2014 at 12:16:53PM -0300, Thiago Farina wrote:
>>
>> On Sun, Sep 7, 2014 at 11:36 PM, Adrian Chadd wrote:
>> > Which NIC are you seeing this on?
>> >
>> Mine is urtwn0: Realtek RTL8187L from my Gateway laptop.
>
> Typo? urtw(4) su
What the hell is calling sta power save? Can you go put in a stack
trace (maybe use dtrace :) whenever the sta powersave routines get
called?
That's odd.
So you see TIM=1 from the AP, but since powersave isn't enabled, it
doesn't transition the NIC back to normal.
So ieee80211_sta_pwrsave() is s
This is what the debug output looks like when things go wrong:
wlan0: [54:78:1a:a0:91:22] sta power save mode on
wlan0: wlan0: [54:78:1a:a0:91:22] save frame with age 41, 1 now queued
[54:78:1a:a0:91:22] sta power save mode off
wlan0: [54:78:1a:a0:91:22] flush ps queue, 1 packets queued
wlan0: [54
On Mon, Sep 08, 2014 at 12:16:53PM -0300, Thiago Farina wrote:
>
> On Sun, Sep 7, 2014 at 11:36 PM, Adrian Chadd wrote:
> > Hi,
> >
> > On 7 September 2014 19:16, Thiago Farina wrote:
> >> On Sun, Sep 7, 2014 at 12:09 PM, Nathan Whitehorn
> >> wrote:
> >>> I've been having some issues with conn
Please compile your kernel with IEEE80211_DEBUG, then enable debugging
- wlandebug +state +power
You can disable powersave with 'ifconfig wlan0 -powersave', but it
shouldn't be enabled by default.
-a
On 8 September 2014 15:14, Nathan Whitehorn wrote:
> So it's definitely to do with powersave
So it's definitely to do with powersave. Here's a bunch of iterations of
ifconfig list sta on my laptop:
ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG
54:78:1a:a0:91:22 1491 54M 37.00 4385 37104 EPS A
HTCAP RSN WME
ADDR AID CHAN RATE RSSI ID
On Sun, Sep 7, 2014 at 11:36 PM, Adrian Chadd wrote:
> Hi,
>
> On 7 September 2014 19:16, Thiago Farina wrote:
>> On Sun, Sep 7, 2014 at 12:09 PM, Nathan Whitehorn
>> wrote:
>>> I've been having some issues with connection stability in urtwn for several
>>> months. The usual symptom is that afte
> wpa_gui as a next step. In the upstream, wpa_gui is maintained together
> with wpa_supplicant by the same maintainer. Therefor wpa_gui has always
> been working fine with wpa_supplicant and might help you to create a
> consistent configuration.
I too have found wpa_gui useful to detect syntax er
Hi Matthias,
On Mon, 8 Sep 2014 09:32:29 +0200
Matthias Apitz wrote:
> El día Monday, September 08, 2014 a las 08:19:45AM +0200, Vladimir
> Botka escribió:
>
> Hi Vladimir,
>
> > maybe the wpa_passphrase utility could help you to create the
> > config. In this particular case:
> >
> > $ wpa_p
El día Monday, September 08, 2014 a las 08:19:45AM +0200, Vladimir Botka
escribió:
Hi Vladimir,
> maybe the wpa_passphrase utility could help you to create the config.
> In this particular case:
>
> $ wpa_passphrase "Naturhotel Wieserhof" "N@tur%Wieser"
> network={
> ssid="Naturhotel Wi
Hi Matthias,
On Mon, 8 Sep 2014 07:47:34 +0200
Matthias Apitz wrote:
> [...]
> I only encountered one problem while traveling through Italy in a
> hotel: They gave me a piece of paper saying "Password:
> "N@tur%Wieser" and I could not construct a
> good /etc/wpa_supplicant.conf to connect correc
Please file PR entries for each of the problems you're seeing.
I don't use the USB devices and I have my hands full with the atheros and
Intel stuff as it is.
Thanks!
Adriabln
On Sep 7, 2014 10:47 PM, "Matthias Apitz" wrote:
> El día Sunday, September 07, 2014 a las 07:36:27PM -0700, Adrian Ch
El día Sunday, September 07, 2014 a las 07:36:27PM -0700, Adrian Chadd escribió:
> > I think what you are relating here is what I observed recently too.
> > Sorry, I'm new to FreeBSD. Just installed it recently, and I noticed
> > that after I left it idle (I went to do something for some hours) fo
Hi,
On 7 September 2014 19:16, Thiago Farina wrote:
> On Sun, Sep 7, 2014 at 12:09 PM, Nathan Whitehorn
> wrote:
>> I've been having some issues with connection stability in urtwn for several
>> months. The usual symptom is that after some period of time the connection
>> will apparently stall.
On Sun, Sep 7, 2014 at 12:09 PM, Nathan Whitehorn
wrote:
> I've been having some issues with connection stability in urtwn for several
> months. The usual symptom is that after some period of time the connection
> will apparently stall. If I'm running ping continuously, for instance, it
> will at
Hi,
The way it's supposed to work in the legacy 802.11 powersave world is
that you send a/any data frame with the powermgt bit in the 802.11
header set to 0 and the AP goes "oh they're awake!" and sends you your
buffered frames.
By default powersave isn't enabled, so we should never be _telling_
Also does not help. I also tried various other things like forcing 11b
or 11g mode, all of which made no difference.
-Nathan
On 09/07/14 11:51, Adrian Chadd wrote:
Ok. Try disabling bgscan.
ifconfig wlan0 -bgscan
-a
___
freebsd-wireless@freebsd
Ok. Try disabling bgscan.
ifconfig wlan0 -bgscan
-a
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
On 09/07/14 08:28, Adrian Chadd wrote:
On 7 September 2014 08:09, Nathan Whitehorn wrote:
I've been having some issues with connection stability in urtwn for several
months. The usual symptom is that after some period of time the connection
will apparently stall. If I'm running ping continuous
On 7 September 2014 08:09, Nathan Whitehorn wrote:
> I've been having some issues with connection stability in urtwn for several
> months. The usual symptom is that after some period of time the connection
> will apparently stall. If I'm running ping continuously, for instance, it
> will at some p
I've been having some issues with connection stability in urtwn for
several months. The usual symptom is that after some period of time the
connection will apparently stall. If I'm running ping continuously, for
instance, it will at some point stop receiving replies. Then, sometime
later, immed
43 matches
Mail list logo
