Hi,
Ok, I've updated -HEAD with "better" looking RSSI code> Would you
please update and try again? I'd like to see the full scan list again
(ifconfig -v wlan0 list scan).
Thanks!
-adrian
___
freebsd-wireless@freebsd.org mailing list
https://lists.free
On 2016-09-17 20:24, Larry Rosenman wrote:
On 2016-09-17 20:20, Larry Rosenman wrote:
On 2016-09-17 20:19, Larry Rosenman wrote:
On 2016-09-17 19:54, Andriy Voskoboinyk wrote:
Sun, 18 Sep 2016 03:52:07 +0300 було написано Adrian Chadd
:
The patch was not applied (copy-paste from one of previo
On 2016-09-17 20:20, Larry Rosenman wrote:
On 2016-09-17 20:19, Larry Rosenman wrote:
On 2016-09-17 19:54, Andriy Voskoboinyk wrote:
Sun, 18 Sep 2016 03:52:07 +0300 було написано Adrian Chadd
:
The patch was not applied (copy-paste from one of previous messages):
with the patch applied:
LER
On 2016-09-17 20:19, Larry Rosenman wrote:
On 2016-09-17 19:54, Andriy Voskoboinyk wrote:
Sun, 18 Sep 2016 03:52:07 +0300 було написано Adrian Chadd
:
The patch was not applied (copy-paste from one of previous messages):
with the patch applied:
LER-MAC-2505:Downloads lrosenma$ cat typescript
On 2016-09-17 19:54, Andriy Voskoboinyk wrote:
Sun, 18 Sep 2016 03:52:07 +0300 було написано Adrian Chadd
:
The patch was not applied (copy-paste from one of previous messages):
with the patch applied:
LER-MAC-2505:Downloads lrosenma$ cat typescript
Script started on Sat Sep 17 20:13:40 2016
Sun, 18 Sep 2016 03:52:07 +0300 було написано Adrian Chadd
:
The patch was not applied (copy-paste from one of previous messages):
SSID/MESH IDBSSID CHAN RATES:N INT CAPS
0x0... ac:3a:7a:08:00:971 54M -117:-127 100 EP RSN HTCAP
WME WPS
WIFIE4EBA3
it didn't seem to change much -- I can re-apply it if y'all want
On 2016-09-17 19:54, Andriy Voskoboinyk wrote:
Sun, 18 Sep 2016 03:52:07 +0300 було написано Adrian Chadd
:
The patch was not applied (copy-paste from one of previous messages):
SSID/MESH IDBSSID CHAN RATE
ok, so it may be something about rate selection. rssi isn't making it
any easier to debug.
lemme see if we can fix rssi in -head..
-a
2016-09-17 17:27 GMT-07:00 Larry Rosenman :
> in the same room, it associates, and when I move back to where I was, it
> stays ssiciated:
>
> iwm0: sending txd
in the same room, it associates, and when I move back to where I was, it
stays ssiciated:
iwm0: sending txd 0xfe00011942a8, in 0xfe0008909000
iwm0: sending data: qid=0 idx=20 len=78 nsegs=1 txflags=0x00103018
rate_n_flags=0x400b rateidx=2
iwm0: <-iwm_start
iwm0: iwm_mvm_rx_tx_cmd_s
same as before - dev.iwm.0.debug=0x1
-a
On 17 September 2016 at 17:09, Larry Rosenman wrote:
> On 2016-09-17 19:07, Adrian Chadd wrote:
>>
>> just go in there and try associating. :)
>>
> with what debug(s) set?
>
>
>>
>> -a
>>
>>
>> On 17 September 2016 at 17:02, Larry Rosenman wrote:
>>>
>>
On 2016-09-17 19:07, Adrian Chadd wrote:
just go in there and try associating. :)
with what debug(s) set?
-a
On 17 September 2016 at 17:02, Larry Rosenman wrote:
On 2016-09-17 18:59, Adrian Chadd wrote:
Well, I'd like to see the RSSI values correct first off. That'll make
debugging a l
just go in there and try associating. :)
-a
On 17 September 2016 at 17:02, Larry Rosenman wrote:
> On 2016-09-17 18:59, Adrian Chadd wrote:
>>
>> Well, I'd like to see the RSSI values correct first off. That'll make
>> debugging a lot easier.
>>
>> If you're testing right up against the AP (sa
On 2016-09-17 18:59, Adrian Chadd wrote:
Well, I'd like to see the RSSI values correct first off. That'll make
debugging a lot easier.
If you're testing right up against the AP (say, 3 or 4 feet away) then
that should eliminate "it happens to be too far away" issues.
-adrian
I can take t
Well, I'd like to see the RSSI values correct first off. That'll make
debugging a lot easier.
If you're testing right up against the AP (say, 3 or 4 feet away) then
that should eliminate "it happens to be too far away" issues.
-adrian
On 17 September 2016 at 16:58, Larry Rosenman wrote:
> On
On 2016-09-17 18:55, Adrian Chadd wrote:
I don't know off-hand how to do monitor mode "right" with macosx
anymore. I'm sure it's something you can google. :)
We should try and fix that RSSI thing first because incorrect RSSI
makes everything difficult :(
-a
avos' patch didn't seem(!) to fix i
I don't know off-hand how to do monitor mode "right" with macosx
anymore. I'm sure it's something you can google. :)
We should try and fix that RSSI thing first because incorrect RSSI
makes everything difficult :(
-a
On 17 September 2016 at 16:32, Larry Rosenman wrote:
> On 2016-09-17 18:27,
On 2016-09-17 18:27, Adrian Chadd wrote:
Ok, eg:
LERCTR NETWORK 2.5 e4:8d:8c:ba:14:ea2 54M
-168:-127 100 EPS SSID
RATES DSPARMS<2> ERP<0x0> HTCAP RSN XRATES<48,72,96,108> HTINFO VEN WPA
the "better" one from where I'm sitting is:
LERCTR NETWORK 2.5 bc:ee:7b:6f
Ok, eg:
LERCTR NETWORK 2.5 e4:8d:8c:ba:14:ea2 54M
-168:-127 100 EPS SSID
RATES DSPARMS<2> ERP<0x0> HTCAP RSN XRATES<48,72,96,108> HTINFO VEN WPAhttps://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.o
On 2016-09-17 18:21, Adrian Chadd wrote:
Hi,
So those status=0x83 means it failed the long retry limit:
IWM_TX_STATUS_FAIL_LONG_LIMIT = 0x83
so it's failing to get an ACK.
The TX setup is:
iwm0: sending data: qid=0 idx=2 len=30 nsegs=1 txflags=0x3008
rate_n_flags=0x420a rateidx=0
S
Hi,
So those status=0x83 means it failed the long retry limit:
IWM_TX_STATUS_FAIL_LONG_LIMIT = 0x83
so it's failing to get an ACK.
The TX setup is:
iwm0: sending data: qid=0 idx=2 len=30 nsegs=1 txflags=0x3008
rate_n_flags=0x420a rateidx=0
So, rate_n_flags = 0x420a, which is:
IWM_RA
On 2016-09-17 18:02, Larry Rosenman wrote:
On 2016-09-17 17:58, Larry Rosenman wrote:
On 2016-09-17 17:08, Larry Rosenman wrote:
On 2016-09-17 16:57, Andriy Voskoboinyk wrote:
Sun, 18 Sep 2016 00:56:11 +0300 було написано Andriy Voskoboinyk
:
make buildkernel w/ KERNFAST=yes
reverted the me
On 2016-09-17 17:58, Larry Rosenman wrote:
On 2016-09-17 17:08, Larry Rosenman wrote:
On 2016-09-17 16:57, Andriy Voskoboinyk wrote:
Sun, 18 Sep 2016 00:56:11 +0300 було написано Andriy Voskoboinyk
:
make buildkernel w/ KERNFAST=yes
reverted the merges, built a new kernel, added the sysctl f
On 2016-09-17 17:08, Larry Rosenman wrote:
On 2016-09-17 16:57, Andriy Voskoboinyk wrote:
Sun, 18 Sep 2016 00:56:11 +0300 було написано Andriy Voskoboinyk
:
make buildkernel w/ KERNFAST=yes
reverted the merges, built a new kernel, added the sysctl for Adrian:
wm0: iwm_nic_tx_init: loading rin
On 2016-09-17 16:57, Andriy Voskoboinyk wrote:
Sun, 18 Sep 2016 00:56:11 +0300 було написано Andriy Voskoboinyk
:
make buildkernel w/ KERNFAST=yes
reverted the merges, built a new kernel, added the sysctl for Adrian:
wm0: iwm_nic_tx_init: loading ring 0 descriptors (0xfe045e13c000) at
e33
Sun, 18 Sep 2016 00:56:11 +0300 було написано Andriy Voskoboinyk
:
make buildkernel w/ KERNFAST=yes
Sun, 18 Sep 2016 00:49:33 +0300 було написано Larry Rosenman
:
It's uses newer firmware - svn merge -c -303322 + reinstall iwm firmwares
To check EAPOL timeouts, you can a) revert the firmw
Sun, 18 Sep 2016 00:49:33 +0300 було написано Larry Rosenman
:
It's uses newer firmware - svn merge -c -303322 + reinstall iwm firmwares
To check EAPOL timeouts, you can a) revert the firmware or b) restore the
iwm module (svn revert --depth=infinity sys/dev/iwm; make buildkernel;
cp
/usr/ob
On 2016-09-17 16:48, Adrian Chadd wrote:
Hi,
Try doing
sysctl dev.iwm.0.debug=0x1
and then try connecting.
I'd like to see what the transmit rate control setup is when it's
transmitting. I'm still not entirely convinced the tx rate, flags, etc
setup is "right".
Also we should patch iwm to al
with those reverts, and a full kernel rebuild, I get a panic on trying
to load it.
Unknown section type in the firmware.
Ideas?
On 2016-09-17 16:18, Andriy Voskoboinyk wrote:
Sun, 18 Sep 2016 00:13:49 +0300 було написано Larry Rosenman
:
For HEAD there is one more commit (r305470):
svn re
Hi,
Try doing
sysctl dev.iwm.0.debug=0x1
and then try connecting.
I'd like to see what the transmit rate control setup is when it's
transmitting. I'm still not entirely convinced the tx rate, flags, etc
setup is "right".
Also we should patch iwm to also use the lowest rate when doing EAPOL
fra
Sun, 18 Sep 2016 00:13:49 +0300 було написано Larry Rosenman
:
For HEAD there is one more commit (r305470):
svn revert --depth=infinity sys/dev/iwm # revert previous 'svn merge'
svn merge -c
-305470,-304891,-304880,-303557,-303418,-303416,-303413,-303327
On 2016-09-17 13:29, Andriy Vosko
On 2016-09-17 13:29, Andriy Voskoboinyk wrote:
Sat, 17 Sep 2016 20:12:59 +0300 було написано Larry Rosenman
:
Ok, last try:
try to apply 'Comment out SF_CFG_CMD + revert changes for MAC_CONTEXT'
patch
from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211885 ;
in case, if it will not he
On 2016-09-17 13:29, Andriy Voskoboinyk wrote:
Sat, 17 Sep 2016 20:12:59 +0300 було написано Larry Rosenman
:
Ok, last try:
try to apply 'Comment out SF_CFG_CMD + revert changes for MAC_CONTEXT'
patch
from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211885 ;
in case, if it will not he
Sat, 17 Sep 2016 20:12:59 +0300 було написано Larry Rosenman
:
Ok, last try:
try to apply 'Comment out SF_CFG_CMD + revert changes for MAC_CONTEXT'
patch
from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211885 ;
in case, if it will not help, try to revert all local changes
( svn revert
attached is WiFi info from my Mac which is sitting next to the problem
machine.
On 2016-09-17 12:12, Larry Rosenman wrote:
+freebsd-wireless
On 2016-09-17 12:11, Larry Rosenman wrote:
On 2016-09-17 11:59, Larry Rosenman wrote:
On 2016-09-17 11:55, Andriy Voskoboinyk wrote:
So, it detects
On 2016-09-17 12:17, Larry Rosenman wrote:
attached is WiFi info from my Mac which is sitting next to the problem
machine.
the List didn't like the PNG, so
link:
http://www.lerctr.org/~ler/FreeBSD/SNR-MAC.png
On 2016-09-17 12:12, Larry Rosenman wrote:
+freebsd-wireless
On 2016-09-17 12:
+freebsd-wireless
On 2016-09-17 12:11, Larry Rosenman wrote:
On 2016-09-17 11:59, Larry Rosenman wrote:
On 2016-09-17 11:55, Andriy Voskoboinyk wrote:
So, it detects AP and tries to associate:
+ bc:ee:7b:6f:41:b8 bc:ee:7b:6f:41:b8 10 40 54M ess wep "LERCTR
NETWORK 2.5"
You can disable iwm
So, it detects AP and tries to associate:
+ bc:ee:7b:6f:41:b8 bc:ee:7b:6f:41:b8 10 40 54M ess wep "LERCTR NETWORK
2.5"
You can disable iwm debugging (sysctl dev.iwm.0.debug=0x0);
probably, wlandebug -i wlan0 auth+assoc+state+crypto will say more
about reasons why it's failing
On 2016-09-17
On 2016-09-17 11:42, Andriy Voskoboinyk wrote:
Sat, 17 Sep 2016 19:37:58 +0300 було написано Larry Rosenman
:
wlandebug -i wlan0 scan ?
here's one with more:
wm0: iwm_mvm_rx_rx_mpdu: phy_info: channel=36, flags=0x0020
iwm0: inputall m 0xf80014bf5d00
[a8:a7:95:e4:eb:a8] new beacon on
On Sat, Sep 17, 2016 at 07:42:33PM +0300, Andriy Voskoboinyk wrote:
> Sat, 17 Sep 2016 19:37:58 +0300 було написано Larry Rosenman
> :
>
> wlandebug -i wlan0 scan ?
>
Done, dmesg
Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 19
Sat, 17 Sep 2016 19:37:58 +0300 було написано Larry Rosenman
:
wlandebug -i wlan0 scan ?
On Sat, Sep 17, 2016 at 06:50:17PM +0300, Andriy Voskoboinyk wrote:
Ok; I think, the patch should resolve this issue.
Nope.
ifconfig wlan0 list scan:
SSID/MESH IDBSSID CHAN RATES:
On Sat, Sep 17, 2016 at 06:50:17PM +0300, Andriy Voskoboinyk wrote:
> Ok; I think, the patch should resolve this issue.
Nope.
ifconfig wlan0 list scan:
SSID/MESH IDBSSID CHAN RATES:N INT CAPS
0x0... ac:3a:7a:08:00:971 54M -117:-127 100 EP RSN HTCAP WME
Ok; I think, the patch should resolve this issue.
patch-iwm-rssi.diff
Description: Binary data
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-u
Here ya go:
Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-CURRENT #8 a212210(dr
Can you attach dmesg with 'sysctl dev.iwm.0.debug=0x2' set?
Is there an easy fix?
On Sat, Sep 17, 2016 at 06:19:51PM +0300, Andriy Voskoboinyk wrote:
Sat, 17 Sep 2016 17:59:43 +0300 Larry Rosenman
:
Ok, I see; there are is a bug with RSSI calculation (S:N field).
>
Is there an easy fix?
On Sat, Sep 17, 2016 at 06:19:51PM +0300, Andriy Voskoboinyk wrote:
> Sat, 17 Sep 2016 17:59:43 +0300 Larry Rosenman
> :
>
> Ok, I see; there are is a bug with RSSI calculation (S:N field).
>
> > No hidden SSID.
> > ifconfig list scan:
> >
> > SS
Sat, 17 Sep 2016 17:59:43 +0300 було написано Larry Rosenman
:
Ok, I see; there are is a bug with RSSI calculation (S:N field).
No hidden SSID.
ifconfig list scan:
SSID/MESH IDBSSID CHAN RATES:N INT CAPS
WIFIE4EBA3 a8:a7:95:e4:eb:a71 54M -172:-127 100 EP
No hidden SSID.
ifconfig list scan:
SSID/MESH IDBSSID CHAN RATES:N INT CAPS
WIFIE4EBA3 a8:a7:95:e4:eb:a71 54M -172:-127 100 EP RSN BSSLOAD
HTCAP WPS WME
0x0... 30:52:cb:03:39:291 54M -181:-127 100 EP RSN HTCAP WME
WPS
LERCTR NETW... e4:8d
Sat, 17 Sep 2016 05:45:23 +0300 було написано Larry Rosenman
:
If you are using AP w/ hidden SSID - patch src tree / wait until r305470
will be merged.
Also:
1) check if 'ifconfig wlan0 list chan' contains AP channel.
2) ifconfig wlan0 list scan (your AP should be here).
fixing the tag on th
fixing the tag on the subject line.
On 2016-09-16 21:42, Larry Rosenman wrote:
i Have a 7260 card, and am running TrueOS's top of tree as of today
(from their update)
and it will NOT connect to my network.
I had similar issues with earlier 11/12 FreeBSD code.
What can I supply to help fix?
p
49 matches
Mail list logo
