Re: Airport wireless and current Debian

[Dan DeVoto <dand1972@yahoo.com>]

I don't have a solution, but I remember coming across a forum post awhile back saying WEP no longer worked with 1st generation Airport cards due to a bug.  Looks like they didn't fix it.

Regards,

Dan

--------------------------------------------
On Wed, 4/13/16, Riccardo Mottola <riccardo.mottola@libero.it> wrote:

 Subject: Airport wireless and current Debian
 To: "PowerPC List Debian" <debian-powerpc@lists.debian.org>
 Date: Wednesday, April 13, 2016, 4:02 PM
 
 Hi,
 
 I just upgraded everything.
 
 I noticed that I cannot connect to my home wifi anymore,
 which is a 
 pretty simple WEP encrypted network, which always used to
 work.
 
 I noticed that the Airport card is detected as a device and
 that I can 
 configure it with iwconfig to the correct ESSID and KEY:
 
 eth0      IEEE 802.11b  ESSID:"xxx"
        
    Mode:Managed  Frequency:2.422
 GHz  Access Point: None
            Bit Rate:11
 Mb/s   Sensitivity:1/0
            Retry
 short  long limit:8   RTS thr=2347
 B   Fragment thr:off
            Encryption
 key:xxxxxx   Security mode:open
            Power
 Management:off
            Link
 Quality=0/70  Signal level=-122 dBm  Noise
 level=-122 dBm
            Rx invalid
 nwid:0  Rx invalid crypt:0  Rx invalid frag:0
            Tx excessive
 retries:0  Invalid misc:0   Missed
 beacon:0
 
 
 however, if I run dhclient... it just sits there for a long
 while, then 
 drops without configuring anything.
 Listening on LPF/eth0/00:30:65:0c:ba:d1
 Sending on   LPF/eth0/00:30:65:0c:ba:d1
 Sending on   Socket/fallback
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
 No DHCPOFFERS received.
 No working leases in persistent database - sleeping.
 
 During the upgrade, I lost the firmware, I reinstalled it.
 
 [   13.603514] orinoco 0.15 (David Gibson 
 <hermes@gibson.dropbear.id.au>,
 Pavel Roskin <proski@gnu.org>, et
 al)
 [   13.613102] airport 0.15 (Benjamin
 Herrenschmidt 
 <benh@kernel.crashing.org>)
 [   13.613319] airport: Physical address
 80030000
 [   15.130218] airport 0.00030000:radio:
 Hardware identity 
 0005:0001:0001:0002
 [   15.130913] airport 0.00030000:radio:
 Station identity 
 001f:0001:0008:0046
 [   15.131231] airport 0.00030000:radio:
 Firmware determined as 
 Lucent/Agere 8.70
 [   15.537135] airport 0.00030000:radio:
 firmware: direct-loading 
 firmware agere_sta_fw.bin
 [   15.617068] airport 0.00030000:radio:
 Hardware identity 
 0005:0001:0001:0002
 [   15.617202] airport 0.00030000:radio:
 Station identity 
 001f:0002:0009:0030
 [   15.617225] airport 0.00030000:radio:
 Firmware determined as 
 Lucent/Agere 9.48
 [   15.617238] airport 0.00030000:radio:
 Ad-hoc demo mode supported
 [   15.617249] airport 0.00030000:radio: IEEE
 standard IBSS ad-hoc mode 
 supported
 [   15.617261] airport 0.00030000:radio: WEP
 supported, 104-bit key
 [   15.617271] airport 0.00030000:radio:
 WPA-PSK supported
 
 
 I see nothing strange in dmesg... where else could I look?
 or do we have 
 a new bug?
 
 Riccardo