Re: wifi obtaining IP address

[Celejar <celejar@gmail.com>]

On Tue, 06 Jul 2010 20:42:24 -0700
Paul Scott <waterhorse@ultrasw.com> wrote:

> On 07/06/2010 08:28 PM, Celejar wrote:
> > On Tue, 06 Jul 2010 19:59:11 -0700
> > Paul Scott<waterhorse@ultrasw.com>  wrote:
> >
> >> On 07/06/2010 06:31 PM, Celejar wrote:
> >>> On Tue, 6 Jul 2010 17:41:07 -0700
> >>> Paul Scott<waterhorse@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