Web lists-archives.com

Re: pointers to material for using netbook's wireless as access point




On Tue, Jun 6, 2017 at 7:30 PM, Dan Ritter <dsr@xxxxxxxxxxxxxxxx> wrote:
> On Tue, Jun 06, 2017 at 10:58:09AM +0900, Joel Rees wrote:
>> I've seen a lot of answers that say "NOT POSSIBLE!!", as if the device
>> manufacturers really want us to believe that it can only be done on
>> MSWindows and MacOSX.
>>
>> I've seen a bit of talk about what appears to me to be the reverse of what I
>> want to do -- allow other computers to connect via the netbook's ethernet
>> port and piggyback the netbook's wireless onto the web. That's not what
>> I want to do.
>>
>> I've got brctl and hostapd installed and have tried some
>> configurations I've seen. I keep getting blocked, apparently by
>> RF-kill and/or something
>> else that tells me it's not allowed.
>>
>> So, before I dump all my configuration files and error messages on the
>> list, can anyone point me to a good how-to? I want to make sure I'm not
>> missing something obvious before I start asking questions.
>
> Depends on the wifi chipset. Some are deliberately disabled by
> their manufacturer from acting in "infrastructure mode", which
> is to say, as an access point.
>
> Here's how to tell:
>
> sudo iwconfig wlan1 mode master

Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; Invalid argument.

But, without "master",

wlan0     IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=off
          Retry  long limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:on


> will put it into infrastructure mode if it can *and you have an
> older chip*
>
> or
>
> sudo iw list

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

I'll paste in the rest below, just in case.

> will show "AP" as an available mode on newer chips.
>
>
> brctl and hostapd are the right way to go.

If I only knew what to do with them. ;-/

It seems like my goal would be to set up a brdge, or perhaps
(according to some of the things I read) routing with NAT, and to set
up the netbook as a DHCP server for the wireless network. Am I
thinking in the right direction, there?

> RF-kill
> is sometimes in hardware (physical switch) and sometimes in
> software (package rfkill is available starting in Wheezy).

Would the rfkill package be useful to install if the messages I get about rfkill
include "hard blocked"?

> -dsr-

And, something I keep wondering about, would ad hoc mode be a good
alternative to setting up an access point? I seem to remember using that,
perhaps in addition to sharing, on old Macs some fifteen our so years ago.


-- 
Joel Rees

One of these days I'll get someone to pay me
to design a language that combines the best of Forth and C.
Then I'll be able to leap wide instruction sets with a single #ifdef,
run faster than a speeding infinite loop with a #define,
and stop all integer size bugs with a bare cast.

More of my delusions:
http://reiisi.blogspot.com/2017/05/do-not-pay-modern-danegeld-ransomware.html
http://reiisi.blogspot.jp/p/novels-i-am-writing.html

-----------------------------
iw list output:

Wiphy phy0
    Band 1:
        Capabilities: 0x1862
            HT20/HT40
            Static SM Power Save
            RX HT20 SGI
            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: 16 usec (0x07)
        HT TX/RX MCS rate indexes supported: 0-7, 32
        Frequencies:
            * 2412 MHz [1] (20.0 dBm)
            * 2417 MHz [2] (20.0 dBm)
            * 2422 MHz [3] (20.0 dBm)
            * 2427 MHz [4] (20.0 dBm)
            * 2432 MHz [5] (20.0 dBm)
            * 2437 MHz [6] (20.0 dBm)
            * 2442 MHz [7] (20.0 dBm)
            * 2447 MHz [8] (20.0 dBm)
            * 2452 MHz [9] (20.0 dBm)
            * 2457 MHz [10] (20.0 dBm)
            * 2462 MHz [11] (20.0 dBm)
            * 2467 MHz [12] (20.0 dBm)
            * 2472 MHz [13] (20.0 dBm)
            * 2484 MHz [14] (disabled)
        Bitrates (non-HT):
            * 1.0 Mbps
            * 2.0 Mbps
            * 5.5 Mbps
            * 11.0 Mbps
            * 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
    max scan IEs length: 2257 bytes
    RTS threshold: 2347
    Coverage class: 0 (up to 0m)
    Supported Ciphers:
        * WEP40 (00-0f-ac:1)
        * WEP104 (00-0f-ac:5)
        * TKIP (00-0f-ac:2)
        * CCMP (00-0f-ac:4)
    Available Antennas: TX 0 RX 0
    Supported interface modes:
         * IBSS
         * managed
         * AP
         * AP/VLAN
         * monitor
    software interface modes (can always be added):
         * AP/VLAN
         * monitor
    interface combinations are not supported
    Supported commands:
         * new_interface
         * set_interface
         * new_key
         * new_beacon
         * new_station
         * new_mpath
         * set_mesh_params
         * set_bss
         * authenticate
         * associate
         * deauthenticate
         * disassociate
         * join_ibss
         * join_mesh
         * remain_on_channel
         * set_tx_bitrate_mask
         * action
         * frame_wait_cancel
         * set_wiphy_netns
         * set_channel
         * set_wds_peer
         * connect
         * disconnect
    Supported TX frame types:
         * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
0xb0 0xc0 0xd0 0xe0 0xf0
         * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    Supported RX frame types:
         * IBSS: 0xd0
         * managed: 0x40 0xd0
         * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * mesh point: 0xb0 0xc0 0xd0
         * P2P-client: 0x40 0xd0
         * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0