On Sat, 10 Apr 2021 at 23:51, kaye n <guikaye@gmail.com> wrote:
> On Sat, Apr 10, 2021 at 6:34 AM David <bouncingcats@gmail.com> wrote:
>> On Mon, 5 Apr 2021 at 23:39, kaye n <guikaye@gmail.com> wrote:
>> > On Mon, Mar 29, 2021 at 10:45 PM IL Ka <kazakevichilya@gmail.com> wrote:
>>
>> >>> Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter
>>
>> >> ok, this is your card.
>>
>> >> Lets see output of
>> >> $ iw dev [your_dev_name]
>>
>> > Pardon me, but what should I type for [your_dev_name] ?
>>
>> On Sat, 10 Apr 2021 at 00:15, kaye n <guikaye@gmail.com> wrote:
>> > On Mon, Apr 5, 2021 at 10:18 PM David Wright <deblis@lionunicorn.co.uk> wrote:
>>
>> >> inxi -Fdflmnopuv7 (my own incantation) should say something like:
>>
>> >> Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: 4000 bus ID: 02:00.0
>> >> chip ID: 8086:08b2
>> >> IF: wlp2s0 state: up mac: 01:23:45:67:89:ab
>>
>> >> ↑↑↑↑↑↑ is the name you need.
>>
>> >> BTW, iw may need root or sudo to perform some functions.
>>
>> > Are you referring to this?
>>
>> > Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter
>> > vendor: Wistron NeWeb driver: bcma-pci-bridge v: N/A port: 2000
>> > bus ID: 03:00.0 chip ID: 14e4:4727
>> > Device-2: Marvell 88E8040 PCI-E Fast Ethernet vendor: Samsung Co
>> > driver: sky2 v: 1.30 port: 5000 bus ID: 07:00.0 chip ID: 11ab:4354
>> > IF: enp7s0 state: down mac: e8:11:32:22:69:43
>> > IF-ID-1: wlp3s0b1 state: up mac: 00:1b:b1:aa:c1:8c
>>
>> Hi kaye,
>>
>> so the answer to your first question above is
>>
>> (as root)
>> # iw dev wlp3s0b1
>>
>> or
>>
>> $ sudo iw dev wlp3s0b1
>>
>> Because wlp3s0b1 is the name given by your kernel to
>> your Broadcom Wireless Network Adapter. And this iw command
>> should be run with superuser privileges as David stated
>> above.
>>
>> Similarly, enp7s0 is the name given by your kernel to your
>> Samsung PCIE Ethernet card.
>>
>> Also, when showing command output to people trying to assist
>> you, don't ever omit the actual command that generated the
>> output. Because it is a crucial aspect of the information sharing
>> process.
>
> This command,
> sudo iw dev wlp3s0b1
>
> resulted in a really long output that looks like a manual and started with this line:
Yeah, sorry, I just jumped into the thread half way and I didn't check
what you were advised to do previously (above), it is incomplete.
I think the output that they wanted to see would be given by these
three commands:
sudo iw dev wlp3s0b1 info
sudo iw dev wlp3s0b1 link
sudo iw dev wlp3s0b1 station dump
Here it is:
kaye@laptop:~$ sudo iw dev wlp3s0b1 info
[sudo] password for kaye:
Interface wlp3s0b1
ifindex 3
wdev 0x1
addr 00:1b:b1:aa:c1:8c
ssid hrmny9108
type managed
wiphy 0
channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz
txpower 30.00 dBm
kaye@laptop:~$ sudo iw dev wlp3s0b1 link
Connected to fc:a6:cd:d0:06:20 (on wlp3s0b1)
SSID: hrmny9108
freq: 2437
RX: 14558652 bytes (39650 packets)
TX: 70458521 bytes (56263 packets)
signal: -19 dBm
rx bitrate: 36.0 MBit/s
tx bitrate: 65.0 MBit/s MCS 7
bss flags: short-slot-time
dtim period: 1
beacon int: 100
kaye@laptop:~$ sudo iw dev wlp3s0b1 station dump
Station fc:a6:cd:d0:06:20 (on wlp3s0b1)
inactive time: 24 ms
rx bytes: 14794829
rx packets: 41066
tx bytes: 70548168
tx packets: 56527
tx retries: 17470
tx failed: 1072
beacon loss: 0
beacon rx: 9583
rx drop misc: 860
signal: -20 dBm
signal avg: -24 dBm
beacon signal avg: -21 dBm
tx bitrate: 72.2 MBit/s MCS 7 short GI
rx bitrate: 36.0 MBit/s
last ack signal:0 dBm
expected throughput: 33.507Mbps
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 1
beacon interval:100
short slot time:yes
connected time: 1026 seconds
Thank you.
kaye