Eu não estou conseguindo configurar um ponto de acesso sem fio (AP)

Question

Estou tentando fazer com que este cartão seja um ponto de acesso e estou falhando. Eu tentei vários lançamentos do Ubuntu e verifiquei no ARM e no i386. A versão do kernel que usei é a 2.6.35, e não há o Network Manager.

Aqui estão as entradas de registro em /var/log/syslog quando conecto o dispositivo:

May 27 10:56:46 vab kernel: usb wakeup is here
May 27 10:56:46 vab kernel: ehci_fsl_bus_resume, Host 1
May 27 10:56:46 vab kernel: usb 2-1.2: new high speed USB device using fsl-ehci and address 8
May 27 10:56:47 vab kernel: usb 2-1.2: New USB device found, idVendor=0cf3, idProduct=9271
May 27 10:56:47 vab kernel: usb 2-1.2: New USB device strings: Mfr=16, Product=32, SerialNumber=48
May 27 10:56:47 vab kernel: usb 2-1.2: Product: WLAN 
May 27 10:56:47 vab kernel: usb 2-1.2: Manufacturer: MVA1020
May 27 10:56:47 vab kernel: usb 2-1.2: SerialNumber: 12345
May 27 10:56:47 vab kernel: usb 2-1.2: ath9k_htc: Transferred FW: ar9271.fw, size: 51312
May 27 10:56:49 vab kernel: ath: EEPROM regdomain: 0x10
May 27 10:56:49 vab kernel: ath: EEPROM indicates we should expect a direct regpair map
May 27 10:56:49 vab kernel: ath: Country alpha2 being used: CO
May 27 10:56:49 vab kernel: ath: Regpair used: 0x10
May 27 10:56:49 vab kernel: Registered led device: ath9k-phy4::radio
May 27 10:56:49 vab kernel: Registered led device: ath9k-phy4::assoc
May 27 10:56:49 vab kernel: Registered led device: ath9k-phy4::tx
May 27 10:56:49 vab kernel: Registered led device: ath9k-phy4::rx
May 27 10:56:49 vab kernel: usb 2-1.2: ath9k_htc: USB layer initialized

hostapd arquivo de configuração:

$ cat config
interface=wlan0
driver=nl80211
ssid=test
channel=1

e executá-lo:

$ sudo hostapd conf 
Configuration file: conf
Failed to set interface wlan0 to master mode.
nl80211 driver initialization failed.
ELOOP: remaining socket: sock=5 eloop_data=0xa4a38 user_data=(nil) handler=0x3d2f8

Saída de iw list :

Wiphy phy4
    Band 1:
        Capabilities: 0x104e
            HT20/HT40
            SM Power Save disabled
            RX HT40 SGI
            No RX STBC
            Max AMSDU length: 7935 bytes
            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] (27.0 dBm)
            * 2417 MHz [2] (27.0 dBm)
            * 2422 MHz [3] (27.0 dBm)
            * 2427 MHz [4] (27.0 dBm)
            * 2432 MHz [5] (27.0 dBm)
            * 2437 MHz [6] (27.0 dBm)
            * 2442 MHz [7] (27.0 dBm)
            * 2447 MHz [8] (27.0 dBm)
            * 2452 MHz [9] (27.0 dBm)
            * 2457 MHz [10] (27.0 dBm)
            * 2462 MHz [11] (27.0 dBm)
            * 2467 MHz [12] (disabled)
            * 2472 MHz [13] (disabled)
            * 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
    max # scan SSIDs: 4
    Supported interface modes:
         * IBSS
         * managed
         * monitor
    Supported commands:
         * new_interface
         * set_interface
         * new_key
         * new_beacon
         * new_station
         * set_bss
         * authenticate
         * associate
         * deauthenticate
         * disassociate
         * join_ibss
         * Unknown command (55)
         * Unknown command (57)
         * Unknown command (59)
         * set_wiphy_netns
         * Unknown command (65)
         * connect
         * disconnect

Para que isso funcione, espero ver AP listado em Supported interface modes nessa saída (como acontece quando eu conecto no meu desktop Debian 7.0+, que tem o Network Manager em execução).

    

Answer 1

O mais provável é que o meu kernel era muito antigo. Eu usei as ferramentas compat-wireless , que suportam novos drivers sem fio para kernels antigos. Eu tenho a última versão mostrada nessa página (3.6.x), segui as instruções, e funciona ... e eu estou feliz.