On Sun, Nov 04, 2007 at 12:46:45AM +0100, Sjoerd Hiemstra wrote: > Op Tue, 30 Oct 2007 23:23:11 -0400 Celejar wrote: > > On Tue, 30 Oct 2007 23:10:48 +0100 Sjoerd Hiemstra wrote: > > > Following the directions at [2], the entry for wifi0 > > > in /etc/network/interfaces now looks like this: > > > > > > iface wifi0 inet dhcp > > > wireless-essid <....> > > > wireless-key <....> > > > auto wifi0 > > > allow-hotplug wifi0 > > > > > > If I do an 'iwlist wifi0 scan' then my AP is detected correctly (as > > > well as two neighbouring APs - interesting). > > > > > > There is only one remaining obstacle. > > > The following messages appear if I do an 'ifup wifi0'. > > > They also appear after '/etc/init.d/networking stop' and then > > > '/etc/init.d/networking start'. > > > And they also appear if I do a 'dhclient wifi0'. > > > > > > wifi0: unknown hardware address type 801 > > > wifi0: unknown hardware address type 801 > > > Listening on LPF/wifi0/ > > > Sending on LPF/wifi0/ > > > Sending on Socket/fallback > > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 5 > > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 12 > > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 14 > > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 11 > > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 12 > > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 7 > > > No DHCPOFFERS received. > > > No working leases in persistent database - sleeping. > > > > > > Something wrong with DHCP on the AP? My main computer works well > > > with it, through a wired ethernet connection. Since you question the state of DHCP on the AP, then have you checked that? It may be that you can control whether DHCP is offered over wireless independently of whether it is offered over wired interface. > > > > This can also indicate that the card isn't properly associating with > > the AP. What does 'iwconfig wifi0' give? > > # iwconfig wifi0 > wifi0 IEEE 802.11-DS ESSID:"SX551559148" > Mode:Managed Frequency:2.432 GHz Access Point:00:01:E3:55:91:48 > Bit Rate:11 Mb/s Tx-Power=17 dBm Sensitivity=0/65535 > Retry limit:16 RTS thr:off Fragment thr:off > Encryption key:****-****-****-****-****-****-** [4] Security mode:open > Power Management:off > Link Quality=80/100 Signal level=-55 dBm Noise level=-98 dBm > Rx invalid nvid:614 Rx invalid crypt:437 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:12986 Missed beacon:0 I looks like it *is* associated with the Access Point listed above. Is that you're access point? Look at the MAC address on the bottom of the AP. > > The output of 'dmesg | grep airo' is: > airo(): Probing for PCI adapters > airo(eth0): Found an MPI350 card > airo(eth0): WPA is supported. > airo(eth0): MAC enabled 0:2:8a:dd:a6:b7 > airo(): Finished probing for PCI adapters > > So I am under the impression that I should use the eth0 interface instead. > But then 'iwconfig eth0' gives hardly any difference: > > # iwconfig eth0 > eth0 IEEE 802.11-DS ESSID:"SX551559148" > Mode:Managed Frequency:2.432 GHz Access Point:00:01:E3:55:91:48 here you are associated with the same AP, looks like it doesn't matter which interface name you use. > Bit Rate:11 Mb/s Tx-Power=17 dBm Sensitivity=0/65535 > Retry limit:16 RTS thr:off Fragment thr:off > Encryption key:****-****-****-****-****-****-** [4] Security mode:open > Power Management:off > Link Quality=72/100 Signal level=-59 dBm Noise level=-98 dBm > Rx invalid nvid:94 Rx invalid crypt:341 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:4709 Missed beacon:0 > > And still there's the error message 'No DHCPOFFERS received'. > And there is some difference with the output of 'iwlist eth0 scan': > > # iwlist eth0 scan > .... > Cell 03 - Address: 00:01:E3:55:91:48 > ESSID:"SX551559148" > Mode:Master > Frequency:2.432 GHz (channel 5) > Quality=88/100 Signal level=-51 dBm Noise level:-98 dBm > Encryption key:on > Bit rates: 1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6Mb/s > 12 Mb/s; 24 Mb/s; 36 Mb/s > Extra:bcn_int=100 > IE: IEEE 802.11i/WPA2 Version 1 -----------------------------^^^^ Are yiou using wpasupplicant? Looks like you need to use wpa to connect... A
Attachment:
signature.asc
Description: Digital signature