On 2/6/06, Lucas Reddinger <[EMAIL PROTECTED]> wrote:
> one more question about the same thing. i got my access point i wish
> to use on a NWID that noone else uses. i specify this nwid using
> ifconfig on my clients. however, as soon as i get a better signal from
> another access point on a different NWID, my card switches, and my
> clients lose their connection. here's what it looks like:
>
> =================================
> $ ifconfig wi0
> wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         lladdr 00:80:c6:e3:1c:ff
>         description: "dhcp
>         groups: egress
>         media: IEEE802.11 autoselect (DS11)
>         status: active
>         ieee80211: nwid linksys_9f 2dBm (auto)
>         inet6 fe80::280:c6ff:fee3:1cff%wi0 prefixlen 64 scopeid 0x2
>         inet 192.168.1.75 netmask 0xffffff00 broadcast 192.168.1.255
> $ wicontrol
> NIC serial number:                      [ 000000003841 ]
> Station name:                           [ WaveLAN/IEEE node ]
> SSID for IBSS creation:                 [ IBSS ]
> Current netname (SSID):                 [ greenmonster ]
> Desired netname (SSID):                 [ linksys_9f ]
> Current BSSID:                          [ 00:0c:41:68:70:f8 ]
> Channel list:                           [ 2047 ]
> IBSS channel:                           [ 1 ]
> Current channel:                        [ 4 ]
> Comms quality/signal/noise:             [ 36 67 4 ]
> Promiscuous mode:                       [ Off ]
> Process 802.11b Frame:                  [ Off ]
> Port type (1=BSS, 3=ad-hoc, 6=Host AP): [ 1 ]
> MAC address:                            [ 00:80:c6:e3:1c:ff ]
> TX rate (selection):                    [ 3 ]
> TX rate (actual speed):                 [ 11 ]
> Maximum data length:                    [ 2304 ]
> RTS/CTS handshake threshold:            [ 2347 ]
> Create IBSS:                            [ Off ]
> Antenna diversity (0=auto,1=pri,2=aux): [ ]
> Microwave oven robustness:              [ On ]
> Roaming mode(1=firm,3=disable):         [ 1 ]
> Access point density:                   [ 1 ]
> Power Management:                       [ Off ]
> Max sleep time:                         [ 100 ]
> Enhanced Security mode:                 [ ]
> Intersil Prism2-based card:             [ 1 ]
> Card info:                              [ PRISM2 HWB3163 rev.B, Firmware 
> 1.4.9 ]
> Encryption:                             [ Off ]
> Encryption algorithm:                   [ Firmware WEP ]
> Authentication type
> (1=OpenSys, 2=Shared Key):              [ 1 ]
> TX encryption key:                      [ 1 ]
> Encryption keys:                        [  ][  ][  ][  ]
> $ sudo wicontrol -L
> AP Information
> ap[0]:  netname (SSID):                 [ greenmonster ]
>         BSSID:                          [ 00:0c:41:68:70:f8 ]
>         Channel:                        [ 4 ]
>         Beacon Interval:                [ 100 ]
>         Quality/Signal/Noise [signal]:  [ 12 / 22 / 10 ]
>         Capinfo:                        [ ESS PRIV ]
>         DataRate [Mbps]:                [ 11.0 ]
>         AvailableRates [Mbps]:          [ 1.0 5.5 11.0 11.0 ]
> ap[1]:  netname (SSID):                 [ linksys_9f ]
>         BSSID:                          [ 00:13:10:e8:9f:44 ]
>         Channel:                        [ 6 ]
>         Beacon Interval:                [ 100 ]
>         Quality/Signal/Noise [signal]:  [ 11 / 21 / 10 ]
>         Capinfo:                        [ ESS ]
>         DataRate [Mbps]:                [ 11.0 ]
>         AvailableRates [Mbps]:          [ 1.0 2.0 5.5 11.0 18.0 24.0 36.0 
> 54.0 ]
> $
> =================================
>
> notice the:
> > Current netname (SSID):                 [ greenmonster ]
> > Desired netname (SSID):                 [ linksys_9f ]
> but "wicontrol -L" proves that the other access point is still there.
> this just happens when greenmonster's signal is stronger than
> linksys_9f's.
> sorry, but this is so frustrating to me, i can tell ifconfig to use a
> certain nwid, channel, &c; but as soon as it gets a better signal from
> another access point, it's game over.
>
> any help is _much_ appreciated.
>
> lucas reddinger
>

The wi(4) driver is _very_ old. Here is what I use to get my Prism2.5 card up:
#ifconfig wi0 nwkey <key> up
#wicontrol -n <nwid> -e 1
#dhclient wi0
It took me about a week to stumble across this sequence of commands.

I think the wi(4) driver will jump access points if you don't
explicitly tell it the nwid to use. That's what the -n flag is for. It
is annoying that you have to use two programs to configure one card
but there it is. It is not a very happy face.

-Kousu

Reply via email to