wifi obtaining IP address
in [Debian]
|
From: Celejar on 7 Jul 2010 00:00 On Tue, 06 Jul 2010 20:42:24 -0700 Paul Scott <waterhorse(a)ultrasw.com> wrote: > On 07/06/2010 08:28 PM, Celejar wrote: > > On Tue, 06 Jul 2010 19:59:11 -0700 > > Paul Scott<waterhorse(a)ultrasw.com> wrote: > > > >> On 07/06/2010 06:31 PM, Celejar wrote: > >>> On Tue, 6 Jul 2010 17:41:07 -0700 > >>> Paul Scott<waterhorse(a)ultrasw.com> wrote: > >>> > >>>> Debian sid. > >>>> > >>>> A little over a week ago my laptop stopped being able to complete a connection. I am using an > >>>> Orinoco Silver (Hermes chipset) > >>>> The failure is the well-known "unable to obtain IP address." I have used both wicd and > >>>> Gnome Network Manager. iwlist and wifi-radar can see the access point. dhclient also fails. > >>>> > >>>> TIA for any ideas as to how to diagnose and solve this, > >>> > > > > Okay, the card reports that it's connected. What's the output of 'iwconfig eth2'? > > iwconfig: > > eth2 IEEE 802.11b ESSID:"bliss" > Mode:Managed Frequency:2.457 GHz Access Point: None > Bit Rate:11 Mb/s Sensitivity:1/0 > Retry limit:8 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality=80/70 Signal level=-22 dBm Noise level=-92 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 I can't be sure, since different drivers behave differently, and I have no experience with the Orinoco / Hermes, but generally, this means that the card isn't associated with the AP. When it is, you should see "Acess Point: xx:xx:xx:xx:xx:xx", with the hex digits of the AP's address. We need to figure out why the card isn't associating. Are you using WEP/WPA? > and ifconfig: > > eth2 Link encap:Ethernet HWaddr 00:02:2d:1e:db:1f > inet6 addr: fe80::202:2dff:fe1e:db1f/64 Scope:Link > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1 errors:60 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:16555 (16.1 KiB) > Interrupt:3 Base address:0x100 ifconfig doesn't matter here, since the problem is with the wireless association. Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100706235430.080cf1db.celejar(a)gmail.com
From: Paul Scott on 7 Jul 2010 00:10 On Tue, Jul 06, 2010 at 11:54:30PM -0400, Celejar wrote: > On Tue, 06 Jul 2010 20:42:24 -0700 > Paul Scott <waterhorse(a)ultrasw.com> wrote: > > > On 07/06/2010 08:28 PM, Celejar wrote: > > > On Tue, 06 Jul 2010 19:59:11 -0700 > > > Paul Scott<waterhorse(a)ultrasw.com> wrote: > > > > > > Okay, the card reports that it's connected. What's the output of 'iwconfig eth2'? > > > > iwconfig: > > > > eth2 IEEE 802.11b ESSID:"bliss" > > Mode:Managed Frequency:2.457 GHz Access Point: None > > Bit Rate:11 Mb/s Sensitivity:1/0 > > Retry limit:8 RTS thr:off Fragment thr:off > > Encryption key:off > > Power Management:off > > Link Quality=80/70 Signal level=-22 dBm Noise level=-92 dBm > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > I can't be sure, since different drivers behave differently, and I have > no experience with the Orinoco / Hermes, but generally, this means that > the card isn't associated with the AP. When it is, you should see > "Acess Point: xx:xx:xx:xx:xx:xx", with the hex digits of the AP's > address. > > We need to figure out why the card isn't associating. Are you using > WEP/WPA? Not at this point. (That's another story) > > and ifconfig: > > > > eth2 Link encap:Ethernet HWaddr 00:02:2d:1e:db:1f > > inet6 addr: fe80::202:2dff:fe1e:db1f/64 Scope:Link > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:1 errors:60 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:0 (0.0 B) TX bytes:16555 (16.1 KiB) > > Interrupt:3 Base address:0x100 > > ifconfig doesn't matter here, since the problem is with the wireless > association. It will when we get an IP address. Any idea why we get an IPv6 address? Thanks, Paul -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100707040420.GA10490(a)mail.ultrasw.com
From: Celejar on 7 Jul 2010 00:30 On Tue, 6 Jul 2010 21:04:22 -0700 Paul Scott <waterhorse(a)ultrasw.com> wrote: > On Tue, Jul 06, 2010 at 11:54:30PM -0400, Celejar wrote: > > On Tue, 06 Jul 2010 20:42:24 -0700 > > Paul Scott <waterhorse(a)ultrasw.com> wrote: > > > > > On 07/06/2010 08:28 PM, Celejar wrote: > > > > On Tue, 06 Jul 2010 19:59:11 -0700 > > > > Paul Scott<waterhorse(a)ultrasw.com> wrote: > > > > > > > > Okay, the card reports that it's connected. What's the output of 'iwconfig eth2'? > > > > > > iwconfig: > > > > > > eth2 IEEE 802.11b ESSID:"bliss" > > > Mode:Managed Frequency:2.457 GHz Access Point: None > > > Bit Rate:11 Mb/s Sensitivity:1/0 > > > Retry limit:8 RTS thr:off Fragment thr:off > > > Encryption key:off > > > Power Management:off > > > Link Quality=80/70 Signal level=-22 dBm Noise level=-92 dBm > > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > I can't be sure, since different drivers behave differently, and I have > > no experience with the Orinoco / Hermes, but generally, this means that > > the card isn't associated with the AP. When it is, you should see > > "Acess Point: xx:xx:xx:xx:xx:xx", with the hex digits of the AP's > > address. > > > > We need to figure out why the card isn't associating. Are you using > > WEP/WPA? > > Not at this point. (That's another story) Okay, try bringing the card down, then back up (ifconfig down, ifconfig up), and then trying to associate manually (iwconfig ethX essid nnnn), see if it associates, and if not, see the logs. > > > and ifconfig: > > > > > > eth2 Link encap:Ethernet HWaddr 00:02:2d:1e:db:1f > > > inet6 addr: fe80::202:2dff:fe1e:db1f/64 Scope:Link > > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:1 errors:60 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:1000 > > > RX bytes:0 (0.0 B) TX bytes:16555 (16.1 KiB) > > > Interrupt:3 Base address:0x100 > > > > ifconfig doesn't matter here, since the problem is with the wireless > > association. > > It will when we get an IP address. Any idea why we get an IPv6 address? No, sorry. I don't know anything about IPv6. Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100707002908.a22adc1e.celejar(a)gmail.com
From: Paul Scott on 7 Jul 2010 15:00 On 07/06/2010 09:29 PM, Celejar wrote: > On Tue, 6 Jul 2010 21:04:22 -0700 > Paul Scott<waterhorse(a)ultrasw.com> wrote: > >> On Tue, Jul 06, 2010 at 11:54:30PM -0400, Celejar wrote: >>> On Tue, 06 Jul 2010 20:42:24 -0700 >>> Paul Scott<waterhorse(a)ultrasw.com> wrote: >>> >>>> On 07/06/2010 08:28 PM, Celejar wrote: >>>>> On Tue, 06 Jul 2010 19:59:11 -0700 >>>>> Paul Scott<waterhorse(a)ultrasw.com> wrote: >>>>> >>>>> Okay, the card reports that it's connected. What's the output of 'iwconfig eth2'? >>>> >>>> iwconfig: >>>> >>>> eth2 IEEE 802.11b ESSID:"bliss" >>>> Mode:Managed Frequency:2.457 GHz Access Point: None >>>> Bit Rate:11 Mb/s Sensitivity:1/0 .... >>> I can't be sure, since different drivers behave differently, and I have >>> no experience with the Orinoco / Hermes, but generally, this means that >>> the card isn't associated with the AP. When it is, you should see >>> "Acess Point: xx:xx:xx:xx:xx:xx", with the hex digits of the AP's >>> address. >>> .... > Okay, try bringing the card down, then back up (ifconfig down, ifconfig > up), and then trying to associate manually (iwconfig ethX essid nnnn), > see if it associates, and if not, see the logs. Ok. I think the key in the logs is eth2: Lucent/Agere firmware doesn't support manual roaming According to other research I have done the firmware seems to be a corrupted version from the last update. I will try going back to the previous version since I can't seem to find a corrected file which is supposed to be available various places online. Thanks, Paul -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4C34CDF4.6000506(a)ultrasw.com
First
|
Prev
|
Pages: 1 2 Prev: dry humor Next: Opinions & why: What's the best DVD setup for Debian AMD64 system |