[Cbe-oss-dev] GELIC Wifi problems

[Masakazu Mokuno]

On Tue, 22 Jan 2008 22:34:29 +1100
"Adam Clark" <noaddress at gmail.com> wrote:

> With a bit more playing around I think I have found a bug which has to
> do with SSIDs that are not part of the broadcast beacon.
> 
> > Please set the essid after the key, like the following:
> >
> > # iwconfig eth1 key <your WEP key>
> > # iwconfig eth1 essid <your AP essid>
> 
> This procedure ends up with the same situation.  ethtool believes the
> the link is up, the green light is on.  If I manually set an IP
> address and attempt to ping the access point, the light does not
> flicker.  ifconfig for the interface reports Tx packets, but no Rx
> packets
> 
> The Fedora 7 Kernel:
> eth0      IEEE 802.11bg  ESSID:"PS3"  Nickname:"ps3.home"
>           Mode:Managed  Frequency:2.442 GHz  Access Point: 00:17:DF:10:63:90
>           Bit Rate:54 Mb/s
>           Encryption key:****-****-****-****-****-****-**
>           Link Quality=75/100  Signal level=-52 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> The new kernel:
> eth1      IEEE 802.11bg  ESSID:"PS3"  Nickname:"gelic_wl"
>           Mode:Managed  Access Point: 00:12:BF:1A:50:9A
>           Encryption key:1234-5678-90AB-CDEF-1234-5678-90   Security mode:open
>           Link Signal level=100/100
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> Notice the different MAC addresses.
> 
> # iwlist
>           Cell 02 - Address: 00:17:DF:10:63:90
>                     ESSID:"HummadaHummada"
>                     Channel:7
>                     Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
>                               11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
>                               48 Mb/s; 54 Mb/s
>                     Encryption key:on
>                     Mode:Master
>                     Signal level=72/100
>                     IE: IEEE 802.11i/WPA2 Version 1
>                         Group Cipher : CCMP
>                         Pairwise Ciphers (1) : CCMP
>                         Authentication Suites (1) : PSK
>           Cell 03 - Address: 00:12:BF:1A:50:9A
>                     ESSID:"TREEHOUSE"
>                     Channel:4
>                     Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
>                               11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
>                               36 Mb/s; 48 Mb/s; 54 Mb/s
>                     Encryption key:on
>                     Mode:Master
>                     Signal level=20/100
> 
> HummadaHummada is the SSID that normally carries the beacon on my AP.
> In this situation it has associated itself with TREEHOUSE (another AP
> in my building somewhere).  Configuring the following on my Cisco AP:


The gelic wireless driver selects one of scanned APs.  So if the list
doesn't have the AP which you want to connect, you cannot connet it.

In this case, it seemed that gelic selected the AP (00:12:BF:1A:50:9A)
as a compatible AP because this AP seemed to be configured WEP enabled.

> cisco-877w(config-ssid)#dot11 ssid HummadaHummada
> cisco-877w(config-ssid)#no guest-mode
> cisco-877w(config-ssid)#dot11 ssid PS3
> cisco-877w(config-ssid)#guest-mode
> 
> now has my PS3 SSID carry the beacon:
> # iwlist
>           Cell 01 - Address: 00:17:DF:10:63:90
>                     ESSID:"PS3"
>                     Channel:7
>                     Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
>                               11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
>                               48 Mb/s; 54 Mb/s
>                     Encryption key:on
>                     Mode:Master
>                     Signal level=87/100
> 
> I performed the iwconfig commands and it came up.  Full connectivity.
> 
> So it works fine only when it is associating with the beacon SSID.
> HummadaHummada is my WPA2-PSK SSID, so I dont want to leave my WEP
> SSID advertised.  While using WPA2 would be a solution in this case, I
> believe there is a patch required to be applied to wpa_supplicant.

If the 00:17:DF:10:63:90 is the AP what you want to connect with, the
following forces the gelic try to connect to specified AP with WEP (only
if the scan list has the AP), although I don't think it helps your
situation.

# ifconfig eth1 down
# iwconfig eth1 key <your wep key>
# iwconfig eth1 ap 00:17:DF:10:63:90
# ifconfig eth1 up 

-- 
Masakazu MOKUNO