ubunty wifi: cant acquire IP address
in [Linux Networking]
|
From: David on 22 Apr 2008 17:54 "Dave Liquorice" <allsortsnotthisbit(a)howhill.com> wrote in message news:nyyfbegfubjuvyypbz.jzr9jj2.pminews(a)srv1.howhill.net... > On Tue, 22 Apr 2008 20:13:00 +0100, David wrote: > >> Channel:5 >> Frequency:2.432 GHz (Channel 5) > > It's a silly question but your AP is on Ch 5 isn't it? Yes, I know it > works in doze, but maye be doze quietly overides defaults or ubunty > does... > >> Quality=81/100 Signal level=-45 dBm Noise level=-68 dBm > > It appears to be seeing something but is it your AP? > > -- > Cheers > Dave. > At this stage I don't think anything is a silly question Dave! Yes my AP is on ch5 and I have incidentally changed it from ch 11 just in case there was soem weird channel issue. The AP is talking happily to other devices wirelessly. I've also tried to use auto for channel selection. I agree its seeing something and I am pretty sure it's my AP. Any ideas? Cheers dave
From: David on 22 Apr 2008 18:00 "Ben Bacarisse" <ben.usenet(a)bsb.me.uk> wrote in message news:87bq41eghm.fsf(a)bsb.me.uk... > "David" <dave(a)antispam.invalid> writes: > > <snip> >> 5.iwlist scan gives: >> -------------------- >> lo Interface doesn't support scanning. >> >> eth0 Interface doesn't support scanning. >> >> wmaster0 Interface doesn't support scanning. >> >> wlan0 Scan completed : >> Cell 01 - Address: 00:18:4D:49:2C:0E >> ESSID:"sally000" >> Mode:Master >> Channel:5 >> Frequency:2.432 GHz (Channel 5) >> Quality=81/100 Signal level=-45 dBm Noise level=-68 >> dBm >> Encryption key:on >> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s >> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s >> 48 Mb/s; 54 Mb/s >> Extra:tsf=00000005d64ca233 >> Cell 02 - Address: 00:01:38:8F:A8:8C >> ESSID:"zoom" >> Mode:Master >> Channel:10 >> Frequency:2.457 GHz (Channel 10) >> Quality=55/100 Signal level=-68 dBm Noise level=-68 >> dBm >> Encryption key:off >> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s >> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s >> 48 Mb/s; 54 Mb/s >> Extra:tsf=00000001225691da >> >> --------------------------- >> My wireless net SSID is sally000. The unprotected "zoom" is next door. I >> have told them about this before!! They are lucky it's me that's their >> neighbour! and not someone less scrupulous.! >> So iwlist doesn't seem to show my AP. >> >> I even reseated the PCI card, rebooted and did this all again. >> Then did a sudo iwconfig which gave: >> --------- >> lo no wireless extensions. >> >> eth0 no wireless extensions. >> >> wmaster0 no wireless extensions. >> >> wlan0 IEEE 802.11g ESSID:"sally000" >> Mode:Managed Frequency:2.432 GHz Access Point: >> 00:18:4D:49:2C:0E >> Tx-Power=27 dBm >> Retry min limit:7 RTS thr:off Fragment thr=2346 B >> Encryption key:A7C3-E7FF-5E >> Link Quality:0 Signal level:0 Noise level:0 >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >> -------- >> >> Note encryption now seems to be recognised. This is what I am uneasy >> about. >> How things seems to change back and forth. Flaky. > > It may seem flaky and firm up when you get a feel for what is going > on. I am in the dark here as I don't know this driver but all the > above looks good except for the signal level. I found this: > > http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/faq > > that says: > > If iwconfig shows > > * Link Quality:0 Signal level:0 > > then you may have wireless disabled in the BIOS. Check for things like > "Wireless : Application Control". > > Is that a possibility? > > -- > Ben. Hi Ben, Yes I've seen that url but the log I attached most recently now shows a signal is present. I guess that narrows down things. It's a desk top so I doubt there is any wifi on-off facility. Now trying PCLinuxOS as an alternative. Cheers
From: Ben Bacarisse on 22 Apr 2008 18:58 "David" <dave(a)antispam.invalid> writes: > "Ben Bacarisse" <ben.usenet(a)bsb.me.uk> wrote in message > news:87bq41eghm.fsf(a)bsb.me.uk... >> "David" <dave(a)antispam.invalid> writes: >> >> <snip> >>> 5.iwlist scan gives: >>> -------------------- >>> wlan0 Scan completed : >>> Cell 01 - Address: 00:18:4D:49:2C:0E >>> ESSID:"sally000" >>> Mode:Master >>> Channel:5 >>> Frequency:2.432 GHz (Channel 5) >>> Quality=81/100 Signal level=-45 dBm Noise level=-68 >>> dBm >>> Encryption key:on >>> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s >>> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s >>> 48 Mb/s; 54 Mb/s >>> Extra:tsf=00000005d64ca233 <snip> >>> --------------------------- <snip> >>> wlan0 IEEE 802.11g ESSID:"sally000" >>> Mode:Managed Frequency:2.432 GHz Access Point: >>> 00:18:4D:49:2C:0E >>> Tx-Power=27 dBm >>> Retry min limit:7 RTS thr:off Fragment thr=2346 B >>> Encryption key:A7C3-E7FF-5E >>> Link Quality:0 Signal level:0 Noise level:0 >>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 <snip> >> It may seem flaky and firm up when you get a feel for what is going >> on. I am in the dark here as I don't know this driver but all the >> above looks good except for the signal level. I found this: >> >> http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/faq >> >> that says: >> >> If iwconfig shows >> >> * Link Quality:0 Signal level:0 >> >> then you may have wireless disabled in the BIOS. Check for things like >> "Wireless : Application Control". >> >> Is that a possibility? > Yes I've seen that url but the log I attached most recently now shows a > signal is present. I don't think it does. The scan shows different data to that shown by iwconfig. The driver may well get the data in quite different ways (I don't know). If you are still seeing Link Quality:0 Signal level:0 Noise level:0 in the iwconfig output, then I would check your BIOS settings. It can't hurt. > I guess that narrows down things. The driver is still show no signal from the associated access point. That is a key indicator. Sadly, I don't know exactly what it indicates! -- Ben.
From: Larry Finger on 22 Apr 2008 19:57 David wrote: > > Yes using b43 as thats what > http://linuxwireless.sipsolutions.net/en/users/Drivers/b43 and soem googled > outputs have recommende and tht's what is the default on Ubuntu 8.04. > But still don't underatydnm what you mean by debug option. Sory to be thinck > but no idea what this and where. > Also not sure why you say to use silicon sonics drivers. Its a broadcom chip > so using broadcom firmware. Have I lost the plot? Sorry to be a noob. Debug is a kernel configuration option. The Broadcom chip connects to the main computer bus through a Sonics Silicon Backplane using the ssb driver. Both are there and both are needed. Larry
From: Larry Finger on 22 Apr 2008 20:07
Ben Bacarisse wrote: > "David" <dave(a)antispam.invalid> writes: > >> "Ben Bacarisse" <ben.usenet(a)bsb.me.uk> wrote in message >> news:87bq41eghm.fsf(a)bsb.me.uk... >>> "David" <dave(a)antispam.invalid> writes: >>> >>> <snip> >>>> 5.iwlist scan gives: >>>> -------------------- >>>> wlan0 Scan completed : >>>> Cell 01 - Address: 00:18:4D:49:2C:0E >>>> ESSID:"sally000" >>>> Mode:Master >>>> Channel:5 >>>> Frequency:2.432 GHz (Channel 5) >>>> Quality=81/100 Signal level=-45 dBm Noise level=-68 >>>> dBm >>>> Encryption key:on >>>> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s >>>> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s >>>> 48 Mb/s; 54 Mb/s >>>> Extra:tsf=00000005d64ca233 > <snip> >>>> --------------------------- > <snip> >>>> wlan0 IEEE 802.11g ESSID:"sally000" >>>> Mode:Managed Frequency:2.432 GHz Access Point: >>>> 00:18:4D:49:2C:0E >>>> Tx-Power=27 dBm >>>> Retry min limit:7 RTS thr:off Fragment thr=2346 B >>>> Encryption key:A7C3-E7FF-5E >>>> Link Quality:0 Signal level:0 Noise level:0 >>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 David - please ignore most of the "advice" that you are getting. These guys don't have the slightest idea what is going on. Your iwconfig output will not show any signal, noise, or link quality until it actually authenticates. If you are using NetworkManager with a normal configuration, then the presence of a ESSID name and/or an Access Point MAC indicates that the device has associated with the AP. Please send the output of 'dmesg | grep wlan0'. Larry |