dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
10
share rss forum feed


No_Strings
Premium,MVM,Ex-Mod 2008-13
join:2001-11-22
The OC
kudos:6
reply to Snakeoil

Re: How do you improve network speeds?

Connect speed is a function of several things:

• Chipset compatibility between the router and the wireless card
• Router/card settings
• Signal strength
• Noise

You can't control the first. If the two devices can't play nicely, you'll get standard speeds.

You may be able to affect the last two by changing the position of the router or client, finding a "quiet" channel or removing interference sources such as 2.4GHz telephones or leaky microwave ovens.

The router probably has channel width settings - something like 20MHz or 40MHz selection. A quick read of a few sites leads me to think that on the client end, it will either work or it won't depending on the Linux driver. There doesn't seem to be a setting for the channel width.

sudo iwconfig wlan0 should show the connect rate and channel width.


Snakeoil
Ignore Button. The coward's feature.
Premium
join:2000-08-05
Mentor, OH
kudos:1

IEEE 802.11bgn ESSID:removed ID
Mode:Managed Frequency:2.462 GHz Access Point: C8:D7:19:92:86:9E
Bit Rate=52 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=52/70 Signal level=-58 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:439 Invalid misc:958 Missed beacon:0

Here is the result. I just removed my network name.
--
Is a person a failure for doing nothing? Or is he a failure for trying, and not succeeding at what he is attempting to do? What did you fail at today?.


No_Strings
Premium,MVM,Ex-Mod 2008-13
join:2001-11-22
The OC
kudos:6
How about this?

sudo iw dev wlan0 link

Per this documentation on the latest config utility (iw), you should see it there. »wireless.kernel.org/en/users/Doc···ation/iw


Snakeoil
Ignore Button. The coward's feature.
Premium
join:2000-08-05
Mentor, OH
kudos:1
Connected to (on wlan0)
SSID:
freq: 2462
RX: 91557111 bytes (133602 packets)
TX: 6698023 bytes (46088 packets)
signal: -60 dBm
tx bitrate: 52.0 MBit/s MCS 11

bss flags: short-slot-time
dtim period: 0
beacon int: 100
--
Is a person a failure for doing nothing? Or is he a failure for trying, and not succeeding at what he is attempting to do? What did you fail at today?.


No_Strings
Premium,MVM,Ex-Mod 2008-13
join:2001-11-22
The OC
kudos:6
Your client card and/or driver may not be compatible with the router for advanced speeds. sudo lspci -v will show the devices, but you'd do well to ping some of the gurus in the Wireless Networking forum to see what you can expect from the Cisco and whatever card you have in the PC.

I've not stayed current on that aspect of wireless. (I may need to change my nick.)


Snakeoil
Ignore Button. The coward's feature.
Premium
join:2000-08-05
Mentor, OH
kudos:1
00:00.0 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
Subsystem: VIA Technologies, Inc. K8M890CE Host Bridge
Flags: bus master, medium devsel, latency 8
Memory at d0000000 (32-bit, prefetchable) [size=128M]
Capabilities: [80] AGP version 3.0
Capabilities: [50] Power Management version 2
Capabilities: [60] HyperTransport: Slave or Primary Interface
Capabilities: [58] #00 [0000]
Kernel driver in use: agpgart-amd64

00:00.1 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
Flags: bus master, medium devsel, latency 0

00:00.2 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
Flags: bus master, medium devsel, latency 0

00:00.3 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
Flags: bus master, medium devsel, latency 0

00:00.4 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
Flags: bus master, medium devsel, latency 0

00:00.5 PIC: VIA Technologies, Inc. K8M890CE I/O APIC Interrupt Controller (prog-if 20 [IO(X)-APIC])
Flags: bus master, fast devsel, latency 0

00:00.7 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
Flags: bus master, medium devsel, latency 0

00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/8251 PCI bridge [K8M890/K8T800/K8T890 South] (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: dfc00000-dfcfffff
Prefetchable memory behind bridge: dfb00000-dfbfffff
Capabilities: [70] Power Management version 2
Kernel modules: shpchp

00:02.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: dc000000-deffffff
Prefetchable memory behind bridge: 00000000c0000000-00000000cfffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [68] Power Management version 2
Capabilities: [70] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [dc] HyperTransport: MSI Mapping Enable- Fixed+
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport
Kernel modules: shpchp

00:03.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: dfe00000-dfefffff
Prefetchable memory behind bridge: 00000000dfd00000-00000000dfdfffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [68] Power Management version 2
Capabilities: [70] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [dc] HyperTransport: MSI Mapping Enable- Fixed+
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [180] Root Complex Link
Kernel driver in use: pcieport
Kernel modules: shpchp

00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Micro-Star International Co., Ltd. Device 7253
Flags: bus master, medium devsel, latency 64, IRQ 21
I/O ports at ff00 [size=8]
I/O ports at fe00 [size=4]
I/O ports at fd00 [size=8]
I/O ports at fc00 [size=4]
I/O ports at fb00 [size=16]
I/O ports at f400 [size=256]
Capabilities: [c0] Power Management version 2
Kernel driver in use: sata_via
Kernel modules: sata_via

00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07) (prog-if 8a [Master SecP PriP])
Subsystem: Micro-Star International Co., Ltd. Device 7253
Flags: bus master, medium devsel, latency 64
[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
[virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
I/O ports at fa00 [size=16]
Capabilities: [c0] Power Management version 2
Kernel driver in use: pata_via
Kernel modules: pata_via

00:10.0 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd. Device 7253
Flags: bus master, medium devsel, latency 64, IRQ 20
I/O ports at f900 [size=32]
Capabilities: [80] Power Management version 2
Kernel driver in use: uhci_hcd

00:10.1 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd. Device 7253
Flags: bus master, medium devsel, latency 64, IRQ 22
I/O ports at f800 [size=32]
Capabilities: [80] Power Management version 2
Kernel driver in use: uhci_hcd

00:10.2 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd. Device 7253
Flags: bus master, medium devsel, latency 64, IRQ 21
I/O ports at f700 [size=32]
Capabilities: [80] Power Management version 2
Kernel driver in use: uhci_hcd

00:10.3 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd. Device 7253
Flags: bus master, medium devsel, latency 64, IRQ 23
I/O ports at f600 [size=32]
Capabilities: [80] Power Management version 2
Kernel driver in use: uhci_hcd

00:10.4 USB controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
Subsystem: Micro-Star International Co., Ltd. Device 7253
Flags: bus master, medium devsel, latency 64, IRQ 21
Memory at dffff000 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
Kernel driver in use: ehci_hcd

00:11.0 ISA bridge: VIA Technologies, Inc. VT8237A PCI to ISA Bridge
Subsystem: VIA Technologies, Inc. VT8237A PCI to ISA Bridge
Flags: medium devsel
Capabilities: [c0] Power Management version 2
Kernel modules: i2c-viapro

00:11.7 Host bridge: VIA Technologies, Inc. VT8237/8251 Ultra VLINK Controller
Subsystem: VIA Technologies, Inc. Device 337e
Flags: bus master, medium devsel, latency 64
Capabilities: [58] HyperTransport: Interrupt Discovery and Configuration

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)
Subsystem: Micro-Star International Co., Ltd. Device 7253
Flags: bus master, medium devsel, latency 64, IRQ 23
I/O ports at f200 [size=256]
Memory at dfffe000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2
Kernel driver in use: via-rhine
Kernel modules: via-rhine

00:13.0 Host bridge: VIA Technologies, Inc. VT8237A Host Bridge
Flags: bus master, fast devsel, latency 0

00:13.1 PCI bridge: VIA Technologies, Inc. VT8237A PCI to PCI Bridge (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: dfa00000-dfafffff
Prefetchable memory behind bridge: 00000000df900000-00000000df9fffff
Capabilities: [60] HyperTransport: MSI Mapping Enable- Fixed+
Capabilities: [70] Subsystem: Device 4300:1320

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Flags: fast devsel
Capabilities: [80] HyperTransport: Host or Secondary Interface

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Flags: fast devsel
Capabilities: [f0] Secure device
Kernel driver in use: k8temp
Kernel modules: k8temp

02:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7600 GT] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. Device c550
Physical Slot: 0
Flags: bus master, fast devsel, latency 0, IRQ 24
Memory at dc000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at dd000000 (64-bit, non-prefetchable) [size=16M]
I/O ports at df00 [size=128]
[virtual] Expansion ROM at de000000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting
Kernel driver in use: nvidia
Kernel modules: nvidia_current, nouveau, nvidiafb

04:04.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device
Flags: bus master, stepping, medium devsel, latency 64, IRQ 17
I/O ports at be00 [size=256]
Capabilities: [c0] Power Management version 2
Kernel driver in use: snd_cmipci
Kernel modules: snd-cmipci

04:05.0 Network controller: Ralink corp. RT3062 Wireless 802.11n 2T/2R
Subsystem: Ralink corp. RT3062 Wireless 802.11n 2T/2R
Flags: bus master, slow devsel, latency 64, IRQ 18
Memory at dfaf0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Kernel driver in use: rt2800pci
Kernel modules: rt2800pci

80:01.0 Audio device: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller (rev 10)
Subsystem: Micro-Star International Co., Ltd. Device 7253
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at bfffc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Kernel driver in use: snd_hda_intel
Kernel modules: snd-hda-intel

Thanks for looking anyhow. It is a generic wifi card that I purchased for 20 bucks or so from Amazon. It's replacing a generic "g" wifi card that I purchased from Microcenter 5 years ago for 10 bucks.

At least it works.. lol.
--
Is a person a failure for doing nothing? Or is he a failure for trying, and not succeeding at what he is attempting to do? What did you fail at today?.


No_Strings
Premium,MVM,Ex-Mod 2008-13
join:2001-11-22
The OC
kudos:6
This is the relevant part: Ralink corp. RT3062 Wireless 802.11n 2T/2R

The good news is that it is capable of using two channels. The other news is that some folks have had challenges with the latest driver (I think you're pretty current on Ubuntu) and dropped back to an older one.

ex: »ubuntuforums.org/showthread.php?···0&page=3

The things I've read don't mention specifically channel width capability with Linux.


koitsu
Premium,MVM
join:2002-07-16
Mountain View, CA
kudos:23
Please do not use 40MHz with 802.11n if using 2.4GHz and there are a substantial number of APs around you actively using channels within the frequency range you plan to use. Doing so may induce interference/increase unreliability for people around you. If unsure, please use 20MHz!

Reference material for my opinion/statement is here (read, do not skim): »www.smallnetbuilder.com/wireless···z-part-1

Here's a visual diagram showing exactly what you end up doing with 40MHz: »en.wikipedia.org/wiki/File:NonOv···N-en.svg

If there are no surrounding APs using those frequency ranges, sure, 40MHz would be fine to use. But chances are (in this day and age) that's not the case.

Bottom line: if you care about speed, use a wired connection. No debate or arguments please. 802.11 -- all revisions -- is quite a disgusting mess.
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.


No_Strings
Premium,MVM,Ex-Mod 2008-13
join:2001-11-22
The OC
kudos:6
Your points are valid, but do not address the OP's question. I run wires for everything where practical, but accept that not everyone has that luxury.

40MHz usage may make you a bad neighbor in an apartment, but where the OP lives lot sizes are large. Output power can usually be turned down as well to mitigate interference.

A blanket "do not use" warning is not indicated, I think.