Não é possível aumentar a potência do cartão wifi usando o iwconfig

2

Por isso, configurei um ponto de acesso usando hostapd , isc-dhcp-server e MASQUERADING . O hotspot funciona e eu posso acessar a Internet.

Problema

A velocidade de conexão é muito lenta .

Quando me conecto ao meu hotspot (via android 4.1, Snapdragon S3 ), vejo uma velocidade de conexão de 65mbps , que cai para 1mbps em segundos.

Eu sei que isso não é um problema de hardware, pois posso obter facilmente 24mbps ( 54mbps link) da minha conexão ethernet em Windows (via connectify ).

Informação

BBes32BesB32 MulherBBBBesBBesBeses MulherBBes iwconfig :
mon.wlan0  IEEE 802.11bgn  Mode:Monitor  Tx-Power=19 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:on

eth0      no wireless extensions.

lo        no wireless extensions.

wlan0     IEEE 802.11bgn  Mode:Master  Tx-Power=19 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
BBes32BesB32 MulherBBBBesBBesBeses MulherBBes iw list :
Wiphy phy0
    Band 1:
        Capabilities: 0x70
            HT20
            Static SM Power Save
            RX Greenfield
            RX HT20 SGI
            RX HT40 SGI
            No RX STBC
            Max AMSDU length: 3839 bytes
            No DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 8 usec (0x06)
        HT TX/RX MCS rate indexes supported: 0-7
        Frequencies:
            * 2412 MHz [1] (19.0 dBm)
            * 2417 MHz [2] (19.0 dBm)
            * 2422 MHz [3] (19.0 dBm)
            * 2427 MHz [4] (19.0 dBm)
            * 2432 MHz [5] (19.0 dBm)
            * 2437 MHz [6] (19.0 dBm)
            * 2442 MHz [7] (19.0 dBm)
            * 2447 MHz [8] (19.0 dBm)
            * 2452 MHz [9] (19.0 dBm)
            * 2457 MHz [10] (19.0 dBm)
            * 2462 MHz [11] (19.0 dBm)
            * 2467 MHz [12] (19.0 dBm) (passive scanning, no IBSS)
            * 2472 MHz [13] (19.0 dBm) (passive scanning, no IBSS)
            * 2484 MHz [14] (disabled)
        Bitrates (non-HT):
            * 1.0 Mbps
            * 2.0 Mbps (short preamble supported)
            * 5.5 Mbps (short preamble supported)
            * 11.0 Mbps (short preamble supported)
            * 6.0 Mbps
            * 9.0 Mbps
            * 12.0 Mbps
            * 18.0 Mbps
            * 24.0 Mbps
            * 36.0 Mbps
            * 48.0 Mbps
            * 54.0 Mbps

lspci -v:

0a:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
    Subsystem: Hewlett-Packard Company Device 1795
    Flags: bus master, fast devsel, latency 0, IRQ 19
    Memory at d4500000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [40] Power Management version 3
    Capabilities: [58] Vendor Specific Information: Len=78 <?>
    Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [d0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [13c] Virtual Channel
    Capabilities: [160] Device Serial Number <removed>
    Capabilities: [16c] Power Budgeting <?>
    Kernel driver in use: bcma-pci-bridge

0b:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)
    Subsystem: Hewlett-Packard Company Device 1818
    Flags: bus master, fast devsel, latency 0, IRQ 43
    I/O ports at 2000 [size=256]
    Memory at d4404000 (64-bit, prefetchable) [size=4K]
    Memory at d4400000 (64-bit, prefetchable) [size=16K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [70] Express Endpoint, MSI 01
    Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
    Capabilities: [d0] Vital Product Data
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Virtual Channel
    Capabilities: [160] Device Serial Number <removed>
    Kernel driver in use: r8169

Ubuntu Release :

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.10
DISTRIB_CODENAME=saucy
DISTRIB_DESCRIPTION="Ubuntu 13.10"
Linux pr3d4tOr 3.11.0-17-generic #31-Ubuntu SMP Mon Feb 3 21:52:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

O que eu tentei:

  • Potência de transmissão:

    prakhar@pr3d4tOr:~$ sudo iwconfig mon.wlan0 txpower 24

  • Taxa de bits:

    prakhar@pr3d4tOr:~$ sudo iwconfig mon.wlan0 rate auto

  • Desativar gerenciamento de energia:

    prakhar@pr3d4tOr:~$ sudo iwconfig mon.wlan0 power off Error for wireless request "Set Power Management" (8B2C) : SET failed on device mon.wlan0 ; Invalid argument.

Eu tentei o acima para wlan0 também. EsBBB MulherB32BBBB MulherB32BBBesBBB Mulhereses Alguém pode orientar o que pode ser o problema?

    
por ps95 26.02.2014 / 09:58

2 respostas

1

Ok, então descobri o problema.

Parece que o driver atual é o uso ( bcma-pci-bridge ) não suporta totalmente o meu cartão sem fio ( Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter ). Se eu deixar meu computador entrar no modo de suspensão e reativá-lo, a placa Wi-Fi permanecerá no modo de baixa energia, por isso, a 1mbps de velocidade.

Na inicialização, os sppeds estão variando corretamente de 1mbps a 54mbps .

A outra alternativa, bcmwl-kernel-source , ao mesmo tempo em que oferece ótimo desempenho sem fio, não suporta o modo AP .

Não consegui encontrar nenhum outro driver.

Espero que isso ajude alguém.

EDITAR : alternar para brcmsmac adiciona o modo AP .

prakhar@aS4v4g3wOrld:~$ iw list

    Supported interface modes:
         * IBSS
         * managed
         * AP
         * AP/VLAN
         * monitor
    software interface modes (can always be added):
         * AP/VLAN
         * monitor

(saída parcial).

Vá para neste artigo para instalar.

    
por ps95 27.02.2014 / 10:17
0

Velocidades 802.11n no BCM4313

Eu criou um ponto de acesso usando a seguinte configuração hostapd :

#####Basic Settings########################
#sets the wifi interface to use, is wlan0 in most cases
interface=wlan0
#driver to use, nl80211 works in most cases
driver=nl80211
#Access Point name
ssid=HEXspot

#####Channel and Mode Settings#############
# Operation mode (a = IEEE 802.11a, b = IEEE 802.11b, g = IEEE 802.11g,
# ad = IEEE 802.11ad (60 GHz); a/g options are used with IEEE 802.11n, too, to
# specify band)
# Default: IEEE 802.11b
hw_mode=g
# WiFi Channel:
channel=11

##### IEEE 802.11n related configuration ##
#WMM needs to be enabled for full HT functionality
wmm_enabled=1
# ieee80211n: Whether IEEE 802.11n (HT) is enabled
# 0 = disabled (default)
# 1 = enabled
# Note: You will also need to enable WMM for full HT functionality.
ieee80211n=1
# ht_capab: HT capabilities (list of flags)
# LDPC coding capability: [LDPC] = supported
# Supported channel width set: [HT40-] = both 20 MHz and 40 MHz with secondary
#   channel below the primary channel; [HT40+] = both 20 MHz and 40 MHz
#   with secondary channel below the primary channel
#   (20 MHz only if neither is set)
#   Note: There are limits on which channels can be used with HT40- and
#   HT40+. Following table shows the channels that may be available for
#   HT40- and HT40+ use per IEEE 802.11n Annex J:
#   freq        HT40-       HT40+
#   2.4 GHz     5-13        1-7 (1-9 in Europe/Japan)
#   5 GHz       40,48,56,64 36,44,52,60
#   (depending on the location, not all of these channels may be available
#   for use)
#   Please note that 40 MHz channels may switch their primary and secondary
#   channels if needed or creation of 40 MHz channel maybe rejected based
#   on overlapping BSSes. These changes are done automatically when hostapd
#   is setting up the 40 MHz channel.
# Spatial Multiplexing (SM) Power Save: [SMPS-STATIC] or [SMPS-DYNAMIC]
#   (SMPS disabled if neither is set)
# HT-greenfield: [GF] (disabled if not set)
# Short GI for 20 MHz: [SHORT-GI-20] (disabled if not set)
# Short GI for 40 MHz: [SHORT-GI-40] (disabled if not set)
# Tx STBC: [TX-STBC] (disabled if not set)
# Rx STBC: [RX-STBC1] (one spatial stream), [RX-STBC12] (one or two spatial
#   streams), or [RX-STBC123] (one, two, or three spatial streams); Rx STBC
#   disabled if none of these set
# HT-delayed Block Ack: [DELAYED-BA] (disabled if not set)
# Maximum A-MSDU length: [MAX-AMSDU-7935] for 7935 octets (3839 octets if not
#   set)
# DSSS/CCK Mode in 40 MHz: [DSSS_CCK-40] = allowed (not allowed if not set)
# PSMP support: [PSMP] (disabled if not set)
# L-SIG TXOP protection support: [LSIG-TXOP-PROT] (disabled if not set)
ht_capab=[HT40][GF][SHORT-GI-40][SHORT-GI-20]
# Require stations to support HT PHY (reject association if they do not)
require_ht=1

#####Security and Authentication###########
#macaddr_acl sets options for mac address filtering. 0 means "accept unless in deny list"
macaddr_acl=0
#Sets authentication algorithm
#1 - only open system authentication
#2 - both open system authentication and shared key authentication
auth_algs=1
#setting ignore_broadcast_ssid to 1 will disable the broadcasting of ssid
ignore_broadcast_ssid=0

#####Sets WPA and WPA2 authentication######
#wpa option sets which wpa implementation to use
#1 - wpa only
#2 - wpa2 only
#3 - both
wpa=2
#sets WPA Password required by the clients to authenticate themselves on the network
wpa_passphrase=anything
#sets wpa key management
wpa_key_mgmt=WPA-PSK
#sets encryption used by WPA2
rsn_pairwise=CCMP

Meu sistema é o Ubuntu 12.04.4 com o kernel linux-generic-lts-saucy (o kernel 3.11 do Saucy é retornado para o Ubuntu 12.04LTS ). Eu usei o driver sem fio brcmsmac , que tem suporte ao modo AP do kernel 3.10 em diante. Consegui obter uma velocidade de link 802.11n de 72Mbps na banda de 2,4GHz com largura de canal de 20MHz. Mas, como no seu caso, a velocidade de transferência real é inferior a 1MBps, mesmo para transferências por FTP.
Como o BCM4313 não pode operar em 5GHz, não podemos obter velocidades de n modo de ligação de canal de qualquer maneira. Nossa melhor aposta é obter largura do canal de 40MHz (modo HT40) na banda de 2,4GHz. O problema é que brcmsmac não suporta adequadamente o modo 40MHz na banda de 2.4GHz, pelo menos para o BCM4313. Não há suporte para o modo DSSS / CCK. Espero que o driver melhore nos novos kernels. Quando o Ubuntu 14.04 Trusty Tahr for lançado, tentarei novamente com seu kernel 3.13.

    
por HEXcube 27.03.2014 / 15:10