Re: Atheros 5418, client drops connection after some time with N

[Adrian Chadd]

woo ok!


-A

On 7 February 2017 at 11:23, clutton  wrote:
> On Sat, 2017-02-04 at 11:12 -0800, Adrian Chadd wrote:
>> thanks! please do update and let me know.
>
> Solved. Updating both endpoints to the latest CURRENT helped.
> Thank you sir!
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 5418, client drops connection after some time with N

[clutton]

On Sat, 2017-02-04 at 11:12 -0800, Adrian Chadd wrote:
> thanks! please do update and let me know.

Solved. Updating both endpoints to the latest CURRENT helped.
Thank you sir!

signature.asc
Description: This is a digitally signed message part

Re: Atheros 5418, client drops connection after some time with N

[Adrian Chadd]

hiya,

thanks! please do update and let me know.



-adrian


On 4 February 2017 at 11:06, clutton  wrote:
> On Sat, 2017-02-04 at 10:57 -0800, Adrian Chadd wrote:
>> ok, so far it indeed looks like a block-ack window issue. Which is
>> weird, because i thought I had fixed all the transmit block-ack
>> window
>> stuff a looong time ago :(
>>
>> Oh, can you please update to the very latest -HEAD? I only recently
>> just fixed some multicast / queue handling issues which may fix your
>> issues. It needs to be done on both the STA and AP side.
>
> HOST: #0 8c2c935f91a(master)-dirty: Sun Jan 29 17:19:08 EET 2017
> AP  : #0 82a993254a9(master): Mon Jan 23 11:46:09 EET 2017
>
> I'll update anyway and give feedback.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 5418, client drops connection after some time with N

[clutton]

On Sat, 2017-02-04 at 10:57 -0800, Adrian Chadd wrote:
> ok, so far it indeed looks like a block-ack window issue. Which is
> weird, because i thought I had fixed all the transmit block-ack
> window
> stuff a looong time ago :(
> 
> Oh, can you please update to the very latest -HEAD? I only recently
> just fixed some multicast / queue handling issues which may fix your
> issues. It needs to be done on both the STA and AP side.

HOST: #0 8c2c935f91a(master)-dirty: Sun Jan 29 17:19:08 EET 2017
AP  : #0 82a993254a9(master): Mon Jan 23 11:46:09 EET 2017

I'll update anyway and give feedback.

signature.asc
Description: This is a digitally signed message part

Re: Atheros 5418, client drops connection after some time with N

[Adrian Chadd]

ok, so far it indeed looks like a block-ack window issue. Which is
weird, because i thought I had fixed all the transmit block-ack window
stuff a looong time ago :(

Oh, can you please update to the very latest -HEAD? I only recently
just fixed some multicast / queue handling issues which may fix your
issues. It needs to be done on both the STA and AP side.



-adrian


On 4 February 2017 at 10:15, clutton  wrote:
> They are too big for hosting now. I'll attach.
>
> falling time around: Sat  4 Feb 2017 20:03:29 EET
>
>
> On Sat, 2017-02-04 at 10:02 -0800, Adrian Chadd wrote:
>> all of em togethe.
>>
>> (I'm going to go look at the element ids that aren't being processed,
>> in case it's something stupid I missed.)
>>
>> On 4 February 2017 at 10:00, clutton  wrote:
>> >
>> > On Sat, 2017-02-04 at 09:48 -0800, Adrian Chadd wrote:
>> > >
>> > > ugh, uhm, redo this on the client and AP side, and include
>> > > "wlandebug
>> > > +crypto +11n" too.
>> > >
>> > > thx,
>> > Just with +crypto+11n or
>> > with
>> > input+scan+assoc+elemid+node+output+inact+roam+rate++crypto+11n
>> >
>> > I'm doing with second now it's still working for now.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 5418, client drops connection after some time with N

[Adrian Chadd]

all of em togethe.

(I'm going to go look at the element ids that aren't being processed,
in case it's something stupid I missed.)

On 4 February 2017 at 10:00, clutton  wrote:
> On Sat, 2017-02-04 at 09:48 -0800, Adrian Chadd wrote:
>> ugh, uhm, redo this on the client and AP side, and include "wlandebug
>> +crypto +11n" too.
>>
>> thx,
>
> Just with +crypto+11n or
> with input+scan+assoc+elemid+node+output+inact+roam+rate++crypto+11n
>
> I'm doing with second now it's still working for now.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 5418, client drops connection after some time with N

[clutton]

On Sat, 2017-02-04 at 09:48 -0800, Adrian Chadd wrote:
> ugh, uhm, redo this on the client and AP side, and include "wlandebug
> +crypto +11n" too.
> 
> thx,

Just with +crypto+11n or
with input+scan+assoc+elemid+node+output+inact+roam+rate++crypto+11n

I'm doing with second now it's still working for now.

signature.asc
Description: This is a digitally signed message part

Re: Atheros 5418, client drops connection after some time with N

[clutton]

AP: http://pasted.co/89e8eb3b

The fall happened around this time: Sat  4 Feb 2017 19:32:04 EET

signature.asc
Description: This is a digitally signed message part

Re: Atheros 5418, client drops connection after some time with N

[clutton]

On Sat, 2017-02-04 at 09:17 -0800, Adrian Chadd wrote:
> hi,
> 
> can you do the AP side at the same time please?
> 
> 
> -a

Sure, give me 10 minutes.

signature.asc
Description: This is a digitally signed message part

Re: Atheros 5418, client drops connection after some time with N

[clutton]

http://pasted.co/3664ad20

There it is.
Nope, it's the log from the client which fails.

On Sat, 2017-02-04 at 08:54 -0800, Adrian Chadd wrote:
> hiya,
> 
> hm! attachments are stripped. can you please put it up somewhere for
> download?
> 
> Is that log from the AP side?
> 
> 
> 
> -adrian
> 
> 
> On 4 February 2017 at 06:34, clutton  wrote:
> > 
> > Hi list.
> > 
> > The hosts are CURRENT both AP and client, after some time of usage
> > client (my laptop) becomes deaf.
> > tcpdump from AP shows that packets are received and transmitted
> > back,
> > but on client tcpdump doesn't show receiving. arping doesn't work
> > too.
> > ifconfig shows "status: associated" anyway.
> > 
> > I don't have any wifi encryption, I use OPEN with IPSEC, but
> > without
> > IPSEC the situation is the same.
> > 
> > What else, ifconfig down/up solves the issue, and with ifconfig -ht
> > everything works well. Need more info - ask.
> > 
> > The log attached is produced with:
> > _ wlandebug input+scan+assoc+elemid+node+output+inact+roam+rate
> > 
> > client's dmesg:
> > ath0:  mem 0xdf3f-0xdf3f irq 17 at device 0.0
> > on
> > pci2
> > ath0: [HT] enabling HT modes
> > ath0: [HT] RTS aggregates limited to 8 KiB
> > ath0: [HT] 2 RX streams; 2 TX streams
> > ath0: AR5418 mac 12.10 RF5133 phy 8.1
> > ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0
> > 
> > P.S. I must be cursed, since I send few emails with debug
> > attachment
> > and none of them passed to list.

signature.asc
Description: This is a digitally signed message part

Re: Atheros 5418, client drops connection after some time with N

[Adrian Chadd]

hiya,

hm! attachments are stripped. can you please put it up somewhere for download?

Is that log from the AP side?



-adrian


On 4 February 2017 at 06:34, clutton  wrote:
> Hi list.
>
> The hosts are CURRENT both AP and client, after some time of usage
> client (my laptop) becomes deaf.
> tcpdump from AP shows that packets are received and transmitted back,
> but on client tcpdump doesn't show receiving. arping doesn't work too.
> ifconfig shows "status: associated" anyway.
>
> I don't have any wifi encryption, I use OPEN with IPSEC, but without
> IPSEC the situation is the same.
>
> What else, ifconfig down/up solves the issue, and with ifconfig -ht
> everything works well. Need more info - ask.
>
> The log attached is produced with:
> _ wlandebug input+scan+assoc+elemid+node+output+inact+roam+rate
>
> client's dmesg:
> ath0:  mem 0xdf3f-0xdf3f irq 17 at device 0.0 on
> pci2
> ath0: [HT] enabling HT modes
> ath0: [HT] RTS aggregates limited to 8 KiB
> ath0: [HT] 2 RX streams; 2 TX streams
> ath0: AR5418 mac 12.10 RF5133 phy 8.1
> ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0
>
> P.S. I must be cursed, since I send few emails with debug attachment
> and none of them passed to list.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Atheros 5418, client drops connection after some time with N

[clutton]

Hi list.

The hosts are CURRENT both AP and client, after some time of usage
client (my laptop) becomes deaf.
tcpdump from AP shows that packets are received and transmitted back,
but on client tcpdump doesn't show receiving. arping doesn't work too.
ifconfig shows "status: associated" anyway.

I don't have any wifi encryption, I use OPEN with IPSEC, but without
IPSEC the situation is the same.

What else, ifconfig down/up solves the issue, and with ifconfig -ht
everything works well. Need more info - ask.

The log attached is produced with:
_ wlandebug input+scan+assoc+elemid+node+output+inact+roam+rate

client's dmesg:
ath0:  mem 0xdf3f-0xdf3f irq 17 at device 0.0 on
pci2
ath0: [HT] enabling HT modes
ath0: [HT] RTS aggregates limited to 8 KiB
ath0: [HT] 2 RX streams; 2 TX streams
ath0: AR5418 mac 12.10 RF5133 phy 8.1
ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0

P.S. I must be cursed, since I send few emails with debug attachment
and none of them passed to list.

signature.asc
Description: This is a digitally signed message part