Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #233652 > unrolled thread

different internet speed in debian and smart phone

Back to article view | Back to linux.debian.user

Contents

  different internet speed in debian and smart phone kaye n <guikaye@gmail.com> - 2021-03-29 16:10 +0200
    Re: different internet speed in debian and smart phone IL Ka <kazakevichilya@gmail.com> - 2021-03-29 16:10 +0200
      Re: different internet speed in debian and smart phone kaye n <guikaye@gmail.com> - 2021-03-29 16:30 +0200
        Re: different internet speed in debian and smart phone IL Ka <kazakevichilya@gmail.com> - 2021-03-29 16:50 +0200
          Re: different internet speed in debian and smart phone kaye n <guikaye@gmail.com> - 2021-04-05 15:40 +0200
            Re: different internet speed in debian and smart phone David Wright <deblis@lionunicorn.co.uk> - 2021-04-05 16:20 +0200
              Re: different internet speed in debian and smart phone kaye n <guikaye@gmail.com> - 2021-04-09 16:20 +0200
                Re: different internet speed in debian and smart phone David Wright <deblis@lionunicorn.co.uk> - 2021-04-11 16:30 +0200
                  Re: different internet speed in debian and smart phone kaye n <guikaye@gmail.com> - 2021-07-19 10:50 +0200
                    Re: different internet speed in debian and smart phone Nicholas Geovanis <nickgeovanis@gmail.com> - 2021-07-19 14:10 +0200
                      Re: different internet speed in debian and smart phone Reco <recoverym4n@enotuniq.net> - 2021-07-19 15:10 +0200
                        Re: different internet speed in debian and smart phone Nicholas Geovanis <nickgeovanis@gmail.com> - 2021-07-19 21:40 +0200
                          Re: different internet speed in debian and smart phone Joe <joe@jretrading.com> - 2021-07-19 22:00 +0200
                    Re: different internet speed in debian and smart phone kaye n <guikaye@gmail.com> - 2021-07-24 12:50 +0200
            Re: different internet speed in debian and smart phone David <bouncingcats@gmail.com> - 2021-04-10 00:40 +0200
              Re: different internet speed in debian and smart phone kaye n <guikaye@gmail.com> - 2021-04-10 16:00 +0200
                Re: different internet speed in debian and smart phone David <bouncingcats@gmail.com> - 2021-04-10 16:30 +0200
                  Re: different internet speed in debian and smart phone kaye n <guikaye@gmail.com> - 2021-04-10 16:40 +0200

#233652 — different internet speed in debian and smart phone

[Multipart message — attachments visible in raw view] — view raw

Hello Friends!

My laptop, if it matters:
Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.4
Distro: Debian GNU/Linux 10 (buster)

This is a familiar scenario:

Firefox browser in Debian.
Internet speed checker is fast.com
Speed is 670kbps

Built-in browser of Samsung phone
Internet speed checker is fast.com
Speed is 14mbps

I am quite sure I don't get this much disparity with another Linux distro,
as well as in Windows 7.

Thank you for your time!
Kaye

[toc] | [next] | [standalone]

#233653

[Multipart message — attachments visible in raw view] — view raw

>
>
> Firefox browser in Debian.
> Internet speed checker is fast.com
> Speed is 670kbps
>
>  How do you connect your laptop to the internet? Is it a cable or wifi?
What NIC are you using?

[toc] | [prev] | [next] | [standalone]

#233654

[Multipart message — attachments visible in raw view] — view raw

On Mon, Mar 29, 2021 at 10:05 PM IL Ka <kazakevichilya@gmail.com> wrote:

>
>> Firefox browser in Debian.
>> Internet speed checker is fast.com
>> Speed is 670kbps
>>
>>  How do you connect your laptop to the internet? Is it a cable or wifi?
> What NIC are you using?
>

Laptop connects to the internet using wifi.

NIC - are you referring to this?

result of inxi -b :
  Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter
  driver: bcma-pci-bridge
  Device-2: Marvell 88E8040 PCI-E Fast Ethernet driver: sky2

[toc] | [prev] | [next] | [standalone]

#233655

[Multipart message — attachments visible in raw view] — view raw

>
>   Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter
>
ok, this is your card.

Lets see  output of
$ iw dev [your_dev_name]
it should be
 $ iw dev wlan0
I believe

Also, try to ping your wifi router ip address and some Internet address like
$ ping 8.8.8.8

Then, check https://www.speedtest.net/ : it gives a little bit more
information than "fast.com"

[toc] | [prev] | [next] | [standalone]

#233842

[Multipart message — attachments visible in raw view] — view raw

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]
> it should be
>  $ iw dev wlan0
> I believe
>
> Also, try to ping your wifi router ip address and some Internet
> address like
> $ ping 8.8.8.8
>
> Then, check https://www.speedtest.net/ : it gives a little bit more
> information than "fast.com"
>

Pardon me, but what should I type for [your_dev_name] ?

[toc] | [prev] | [next] | [standalone]

#233856

On Mon 05 Apr 2021 at 21:39:16 (+0800), kaye n 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]
> > it should be
> >  $ iw dev wlan0
> > I believe
> >
> > Also, try to ping your wifi router ip address and some Internet
> > address like
> > $ ping 8.8.8.8
> >
> > Then, check https://www.speedtest.net/ : it gives a little bit more
> > information than "fast.com"
> 
> Pardon me, but what should I type for [your_dev_name] ?

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.
Note that the URL on the man page should be:
https://wireless.wiki.kernel.org/en/users/documentation/iw

On Mon 29 Mar 2021 at 21:59:48 (+0800), kaye n wrote:
> I am quite sure I don't get this much disparity with another Linux distro,
> as well as in Windows 7.

Actual numbers for all these cases would be more useful than
reminiscence, so that we can make the comparison.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#234037

[Multipart message — attachments visible in raw view] — view raw

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.
> Note that the URL on the man page should be:
> https://wireless.wiki.kernel.org/en/users/documentation/iw
>
> On Mon 29 Mar 2021 at 21:59:48 (+0800), kaye n wrote:
> > I am quite sure I don't get this much disparity with another Linux
> distro,
> > as well as in Windows 7.
>
> Actual numbers for all these cases would be more useful than
> reminiscence, so that we can make the comparison.
>
> Cheers,
> David.
>

Hi David,
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
  IP v4: 192.168.1.14/24 type: dynamic noprefixroute scope: global
  broadcast: 192.168.1.255
  IP v6: fe80::c19e:a977:3a6:ccec/64 type: noprefixroute scope: link
  WAN IP: 136.158.34.210
Thank you

[toc] | [prev] | [next] | [standalone]

#234100

On Fri 09 Apr 2021 at 22:14:59 (+0800), kaye n wrote:
> Are you referring to this?
>   IF-ID-1: wlp3s0b1 state: up mac: 00:1b:b1:aa:c1:8c

Already answered, I see. BTW …

Generally speaking when people give help of this list,
they often use the traditional names (eth0 and wlan0) as
placeholders for these interfaces because the newer,
persistent names are specific to your computer.

> > On Mon 29 Mar 2021 at 21:59:48 (+0800), kaye n wrote:
> > > I am quite sure I don't get this much disparity with another Linux
> > distro,
> > > as well as in Windows 7.
> >
> > Actual numbers for all these cases would be more useful than
> > reminiscence, so that we can make the comparison.

Here, I meant some sort of table of comparison, like:

Device           connection    down-speed  up-speed    site
                    type
Debian            wifi&ISP         nnn       nnn       fast.com
Windows7          wifi&ISP         nnn       nnn       fast.com
Other linux       wifi&ISP         nnn       nnn       fast.com
Samsung phone        4G            nnn       nnn       fast.com

eg

Debian buster     eth&ISP          83.30    11.38      www.speedtest.net
my mobile            -              0        0         -

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#237520

[Multipart message — attachments visible in raw view] — view raw

On Sun, Apr 11, 2021 at 10:21 PM David Wright <deblis@lionunicorn.co.uk>
wrote:

> On Fri 09 Apr 2021 at 22:14:59 (+0800), kaye n wrote:
> > Are you referring to this?
> >   IF-ID-1: wlp3s0b1 state: up mac: 00:1b:b1:aa:c1:8c
>
> Already answered, I see. BTW …
>
> Generally speaking when people give help of this list,
> they often use the traditional names (eth0 and wlan0) as
> placeholders for these interfaces because the newer,
> persistent names are specific to your computer.
>
> > > On Mon 29 Mar 2021 at 21:59:48 (+0800), kaye n wrote:
> > > > I am quite sure I don't get this much disparity with another Linux
> > > distro,
> > > > as well as in Windows 7.
> > >
> > > Actual numbers for all these cases would be more useful than
> > > reminiscence, so that we can make the comparison.
>
> Here, I meant some sort of table of comparison, like:
>
> Device           connection    down-speed  up-speed    site
>                     type
> Debian            wifi&ISP         nnn       nnn       fast.com
> Windows7          wifi&ISP         nnn       nnn       fast.com
> Other linux       wifi&ISP         nnn       nnn       fast.com
> Samsung phone        4G            nnn       nnn       fast.com
>
> eg
>
> Debian buster     eth&ISP          83.30    11.38      www.speedtest.net
> my mobile            -              0        0         -
>
> Cheers,
> David.
>
> Hello friends,

Just to give an update in case anyone is interested.
One of the solutions provided in the link below seems to be effective for
me.

https://itsfoss.com/speed-up-slow-wifi-connection-ubuntu/

"Solution 5: Ditch default network manager and embrace Wicd (possibly
obsolete)"

Thank you everyone.
Stay safe.
Kaye

[toc] | [prev] | [next] | [standalone]

#237523

[Multipart message — attachments visible in raw view] — view raw

Reading this thread, remembering my annoyance with NetworkManager, I ran
across this article by RedHat's NetManager developer Thomas Haller. From
last year. Yes I suppose it's promotional, but he sorts thru some of the
high-level issues that software like it has to address.
https://blogs.gnome.org/thaller/2020/04/10/why-networkmanager/

On Mon, Jul 19, 2021, 3:41 AM kaye n <guikaye@gmail.com> wrote:

> On Sun, Apr 11, 2021 at 10:21 PM David Wright <deblis@lionunicorn.co.uk>
> wrote:
>
>> On Fri 09 Apr 2021 at 22:14:59 (+0800), kaye n wrote:
>> > Are you referring to this?
>> >   IF-ID-1: wlp3s0b1 state: up mac: 00:1b:b1:aa:c1:8c
>>
>> Already answered, I see. BTW …
>>
>> Generally speaking when people give help of this list,
>> they often use the traditional names (eth0 and wlan0) as
>> placeholders for these interfaces because the newer,
>> persistent names are specific to your computer.
>>
>> > > On Mon 29 Mar 2021 at 21:59:48 (+0800), kaye n wrote:
>> > > > I am quite sure I don't get this much disparity with another Linux
>> > > distro,
>> > > > as well as in Windows 7.
>> > >
>> > > Actual numbers for all these cases would be more useful than
>> > > reminiscence, so that we can make the comparison.
>>
>> Here, I meant some sort of table of comparison, like:
>>
>> Device           connection    down-speed  up-speed    site
>>                     type
>> Debian            wifi&ISP         nnn       nnn       fast.com
>> Windows7          wifi&ISP         nnn       nnn       fast.com
>> Other linux       wifi&ISP         nnn       nnn       fast.com
>> Samsung phone        4G            nnn       nnn       fast.com
>>
>> eg
>>
>> Debian buster     eth&ISP          83.30    11.38      www.speedtest.net
>> my mobile            -              0        0         -
>>
>> Cheers,
>> David.
>>
>> Hello friends,
>
> Just to give an update in case anyone is interested.
> One of the solutions provided in the link below seems to be effective for
> me.
>
> https://itsfoss.com/speed-up-slow-wifi-connection-ubuntu/
>
> "Solution 5: Ditch default network manager and embrace Wicd (possibly
> obsolete)"
>
> Thank you everyone.
> Stay safe.
> Kaye
>
>

[toc] | [prev] | [next] | [standalone]

#237526

	Hi.

Please do not top-post.

On Mon, Jul 19, 2021 at 07:07:30AM -0500, Nicholas Geovanis wrote:
> Reading this thread, remembering my annoyance with NetworkManager, I ran
> across this article by RedHat's NetManager developer Thomas Haller. From
> last year. Yes I suppose it's promotional, but he sorts thru some of the
> high-level issues that software like it has to address.
> https://blogs.gnome.org/thaller/2020/04/10/why-networkmanager/

Whoever wrote this definitely likes to omit some details, and twist some
others. Few examples:

> We have NetworkManager, which is a freedesktop.org project. There is
> also ConnMan, netctl (on ArchLinux), systemd-networkd, wicd
> (unmaintained), wicked (on SUSE).

Note the absence of ifupdown, which is still shipped to paying Red Hat
customers.
Note the absence of ifupdown (same name, different implementation),
which is still considered the primary way of configuring network in
Debian.
And last, but not least, note the absence of netplan, which is the
primary way of configuring network in Ubuntu.

And the brilliant lumping of systemd-networkd along with the others,
while systemd-networkd was supposed to be One Standard Way Of Doing It
On Linux. Priceless.


> NetworkManager works well on the phone,

Sorry, what?

> the server,

Man's entitled to his option. Using a "stateful process" for a typical
"static IP, one default gateway" server is an overkill, but the link
contains "gnome.org", so this is expected.

> in a container,

On the contrary, in a well-designed container any means of configuring
the network from the inside are redundant at best. A good container
starts with the network that's configured already, and cannot change a
single bit of it while it's running.

> on a notebook and on a workstation.

Note the absence of "on a router" in that list.


> Wherever you have NetworkManager, it works and behaves the same.

I must me missing something, but NetworkManager on Debian does not
generate those wonderful /etc/sysconfig/network-scripts/* files like it
does in RHEL.


To sum it up - if NetworkManager works for you - more power to you.
If it does not - the thing was designed to be an over-engineered behemoth
(and the article admits it to a certain extent), you've got exactly what
was advertised to you.

Personally, I'll take "other solutions" designed with the "focus on
configuring the network" over the "configuration daemon that serves the
needs of applications". Because, while it may sound strange, I like my
network to be configured if I happen to do it.

Reco

[toc] | [prev] | [next] | [standalone]

#237528

[Multipart message — attachments visible in raw view] — view raw

On Mon, Jul 19, 2021, 8:02 AM Reco <recoverym4n@enotuniq.net> wrote:

>         Hi.
>
> Please do not top-post.
>
> On Mon, Jul 19, 2021 at 07:07:30AM -0500, Nicholas Geovanis wrote:
> > Reading this thread, remembering my annoyance with NetworkManager, I ran
> > across this article by RedHat's NetManager developer Thomas Haller. From
> > last year. Yes I suppose it's promotional, but he sorts thru some of the
> > high-level issues that software like it has to address.
> > https://blogs.gnome.org/thaller/2020/04/10/why-networkmanager/
>
> ......
>

> NetworkManager works well on the phone,
>
> Sorry, what?
>
> > the server,
>
> Man's entitled to his option. Using a "stateful process" for a typical
> "static IP, one default gateway" server is an overkill, but the link
> contains "gnome.org", so this is expected.
>

It seems clear that NetworkManager like systemd was a response to
non-dedicated, transient network configuration of a portable device or
hands-off networking environment  (including physical layer). Naturally, we
needed to build an all-encompassing software world-view on top of that :-)
cause that's what we do :-)


> in a container,
>
> On the contrary, in a well-designed container any means of configuring
> the network from the inside are redundant at best. A good container
> starts with the network that's configured already, and cannot change a
> single bit of it while it's running.
>
> > on a notebook and on a workstation.
>
> Note the absence of "on a router" in that list.
>

Deities defend us.
My problem is the complete absence of thought shown by that list "server
notebook workstation".
I want to ask him: What is a use-case?

Also to point out that containers too have different use-cases, and he
seems to have done a mash-up again. You point-out one such case. I see at
least three: what you might call cloud-temp, on-prem-in-broadest-terms, and
human-at-workstation.

>
>
> Reco
>
>

[toc] | [prev] | [next] | [standalone]

#237531

On Mon, 19 Jul 2021 14:35:44 -0500
Nicholas Geovanis <nickgeovanis@gmail.com> wrote:

>
> 
> Deities defend us.
> My problem is the complete absence of thought shown by that list
> "server notebook workstation".
> I want to ask him: What is a use-case?
> 
> Also to point out that containers too have different use-cases, and he
> seems to have done a mash-up again. You point-out one such case. I
> see at least three: what you might call cloud-temp,
> on-prem-in-broadest-terms, and human-at-workstation.
> 

I have NM installed on my netbook and would have it on my Laptop if it
ran Linux. I wouldn't allow it anywhere near my workstation or server,
where it would have no function. And my workstation doesn't have a
static address, it has a DHCP reservation, like most other network
devices here. Only my netbook uses wireless and VPN, where I find NM
(now) Just Working (tm). Agreed, it wasn't always so.

On the subject of VPN, I'm having terrible trouble with the official
OpenVPN client for mobiles, it works on my Android phone but not my
wife's Android phone or our iPad. Possibly something to do with the
client on the latter two not having any manual configuration mode. NM
on the netbook is far easier to configure, which I believe Google and
Apple see as a drawback. It appears that nobody configures VPNs any
more, people just take a subscription with a commercial one and are sent
fully debugged configuration files.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#237674

[Multipart message — attachments visible in raw view] — view raw

> Hello friends,
>
> Just to give an update in case anyone is interested.
> One of the solutions provided in the link below seems to be effective for
> me.
>
> https://itsfoss.com/speed-up-slow-wifi-connection-ubuntu/
>
> "Solution 5: Ditch default network manager and embrace Wicd (possibly
> obsolete)"
>
> Thank you everyone.
> Stay safe.
> Kaye
>

Hello Friends
Update again for anyone who's interested.
Wicd worked for a few days. Now it's as slow as the default Network Manager.
Really strange.
I give up.
Thank you for your time.

[toc] | [prev] | [next] | [standalone]

#234064

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.

[toc] | [prev] | [next] | [standalone]

#234070

[Multipart message — attachments visible in raw view] — view raw

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.
>

Hello.

 This command,
sudo iw dev wlp3s0b1

resulted in a really long output that looks like a manual and started with
this line:
Usage: iw [options] command

Really sorry, I'm not very knowledgeable with this.

Thank you for your time
kaye

[toc] | [prev] | [next] | [standalone]

#234073

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

[toc] | [prev] | [next] | [standalone]

#234074

[Multipart message — attachments visible in raw view] — view raw

On Sat, Apr 10, 2021 at 10:23 PM David <bouncingcats@gmail.com> wrote:

> 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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web