lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 4 Mar 2019 02:34:19 +0000
From:   Tony Chuang <yhchuang@...ltek.com>
To:     Arend Van Spriel <arend.vanspriel@...adcom.com>,
        "David R. Bergstein" <david.r.bergstein@...il.com>,
        Larry Finger <Larry.Finger@...inger.net>
CC:     Pkshih <pkshih@...ltek.com>,
        "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Realtek r8822be kernel module does not negotiate 802.11ac connection



> -----Original Message-----
> From: Arend Van Spriel [mailto:arend.vanspriel@...adcom.com]
> 
> > Larry,
> >
> > Sorry about all these extra replies.  Shortly after I sent my last
> > message my access point started recognizing the connection as 802.11ac
> > with PHY Rate / Modulation Rate of 866.6 Mbps.  What is somewhat
> > misleading is the information reported by iwconfig (see bit rate below).
> 
> My bet would be that it is nitrate at which beacon or probe response is
> received. Regardless I would suggest using iw in this day and age.
> 
> Regards,
> Arend
> 
> > $ iwconfig wlo1
> > wlo1      IEEE 802.11  ESSID:"XXXXXXXXXX-5G"
> >           Mode:Managed  Frequency:5.22 GHz  Access Point:
> > xx:xx:xx:xx:xx:xx
> >           Bit Rate=6.5 Mb/s   Tx-Power=23 dBm
> >           Retry short limit:7   RTS thr:off   Fragment thr:off
> >           Power Management:on
> >           Link Quality=70/70  Signal level=-40 dBm
> >           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >           Tx excessive retries:0  Invalid misc:11   Missed beacon:0
> >
> > Sincerely,
> >
> > David R. Bergstein
> 

It's because the initial version does not collect tx_rate report from the firmware.
So it just print out the initial value. Will be added in the next series. Thanks!

Yan-Hsuan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ