FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 07-07-2010, 01:31 AM
Celejar
 
Default wifi obtaining IP address

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,

To diagnose this sort of thing, we need the logs (dmesg, syslog). Low
level tools are better than the high level, GUI stuff.

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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100706213141.b4c64a73.celejar@gmail.com">http://lists.debian.org/20100706213141.b4c64a73.celejar@gmail.com
 
Old 07-07-2010, 02:59 AM
Paul Scott
 
Default wifi obtaining IP address

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,


To diagnose this sort of thing, we need the logs (dmesg, syslog). Low
level tools are better than the high level, GUI stuff.


Here are syslog entries from dhclient eth2 and dmegs showing the
insertion of the PCMCIA card.


Thanks,

Paul

dmesg:

[ 1624.772201] pcmcia_socket pcmcia_socket1: pccard: PCMCIA card
inserted into slot 1
[ 1624.772239] pcmcia_socket pcmcia_socket1: cs: memory probe
0xa0000000-0xa0ffffff: clean.

[ 1624.809253] pcmcia 1.0: pcmcia: registering new device pcmcia1.0
[ 1625.729461] cfg80211: Using static regulatory domain info
[ 1625.729481] cfg80211: Regulatory domain: US
[ 1625.729492] (start_freq - end_freq @ bandwidth), (max_antenna_gain,
max_eirp)

[ 1625.729512] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[ 1625.729530] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 1625.729549] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 1625.729567] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 1625.729584] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 1625.729600] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 1625.730050] cfg80211: Calling CRDA for country: US
[ 1626.033421] orinoco 0.15 (David Gibson
<hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
[ 1626.077137] orinoco_cs 0.15 (David Gibson
<hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)

[ 1626.185881] orinoco_cs 1.0: Hardware identity 0001:0001:0004:0000
[ 1626.185993] orinoco_cs 1.0: Station identity 001f:0001:0006:0010
[ 1626.186018] orinoco_cs 1.0: Firmware determined as Lucent/Agere 6.16
[ 1626.190614] orinoco_cs 1.0: firmware: requesting agere_sta_fw.bin
[ 1626.866015] orinoco_cs 1.0: Hardware identity 0001:0001:0004:0000
[ 1626.866155] orinoco_cs 1.0: Station identity 001f:0002:0009:0030
[ 1626.866176] orinoco_cs 1.0: Firmware determined as Lucent/Agere 9.48
[ 1626.866189] orinoco_cs 1.0: Ad-hoc demo mode supported
[ 1626.866203] orinoco_cs 1.0: IEEE standard IBSS ad-hoc mode supported
[ 1626.866218] orinoco_cs 1.0: WEP supported, 104-bit key
[ 1626.866228] orinoco_cs 1.0: WPA-PSK supported
[ 1627.656203] udev: renamed network interface eth1 to eth2
[ 1629.008197] ADDRCONF(NETDEV_UP): eth2: link is not ready
[ 1629.225289] eth2: New link status: Connected (0001)
[ 1629.225495] ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[ 1630.720511] eth2: Lucent/Agere firmware doesn't support manual roaming
[ 1635.918066] eth2: Lucent/Agere firmware doesn't support manual roaming
[ 1640.216115] eth2: no IPv6 routers present
[ 1641.125130] eth2: Lucent/Agere firmware doesn't support manual roaming
[ 1646.302985] eth2: Lucent/Agere firmware doesn't support manual roaming
[ 1651.624297] eth2: Lucent/Agere firmware doesn't support manual roaming
[ 1659.181055] eth2: Lucent/Agere firmware doesn't support manual roaming
[ 1664.379099] eth2: Lucent/Agere firmware doesn't support manual roaming
[ 1669.586645] eth2: Lucent/Agere firmware doesn't support manual roaming
[ 1674.783657] eth2: Lucent/Agere firmware doesn't support manual roaming
[ 1679.989689] eth2: Lucent/Agere firmware doesn't support manual roaming

syslog:

Jul 6 19:36:27 gotojoy avahi-autoipd(eth2)[14580]: Got SIGTERM, quitting.
Jul 6 19:36:27 gotojoy avahi-autoipd(eth2)[14580]: Callout STOP,
address 169.254.5.190 on interface eth2
Jul 6 19:36:27 gotojoy avahi-daemon[1239]: Withdrawing address record
for 169.254.5.190 on eth2.
Jul 6 19:36:27 gotojoy avahi-daemon[1239]: Leaving mDNS multicast group
on interface eth2.IPv4 with address 169.254.5.190.
Jul 6 19:36:27 gotojoy avahi-daemon[1239]: Interface eth2.IPv4 no
longer relevant for mDNS.
Jul 6 19:36:27 gotojoy avahi-autoipd(eth2)[14581]: client: RTNETLINK
answers: No such process
Jul 6 19:36:29 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 3
Jul 6 19:36:32 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 7
Jul 6 19:36:39 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 7
Jul 6 19:36:46 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 11
Jul 6 19:36:57 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 19
Jul 6 19:37:16 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 14
Jul 6 19:37:23 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 7
Jul 6 19:37:30 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 9

Jul 6 19:37:30 gotojoy dhclient: No DHCPOFFERS received.
Jul 6 19:37:30 gotojoy dhclient: No working leases in persistent
database - sleeping.
Jul 6 19:37:30 gotojoy avahi-autoipd(eth2)[14928]: Found user
'avahi-autoipd' (UID 102) and group 'avahi-autoipd' (GID 104).
Jul 6 19:37:30 gotojoy avahi-autoipd(eth2)[14928]: Successfully called
chroot().
Jul 6 19:37:30 gotojoy avahi-autoipd(eth2)[14928]: Successfully dropped
root privileges.
Jul 6 19:37:30 gotojoy avahi-autoipd(eth2)[14928]: Starting with
address 169.254.5.190
Jul 6 19:37:34 gotojoy avahi-autoipd(eth2)[14928]: Callout BIND,
address 169.254.5.190 on interface eth2
Jul 6 19:37:34 gotojoy avahi-daemon[1239]: Joining mDNS multicast group
on interface eth2.IPv4 with address 169.254.5.190.
Jul 6 19:37:34 gotojoy avahi-daemon[1239]: New relevant interface
eth2.IPv4 for mDNS.
Jul 6 19:37:34 gotojoy avahi-daemon[1239]: Registering new address
record for 169.254.5.190 on eth2.IPv4.
Jul 6 19:37:38 gotojoy avahi-autoipd(eth2)[14928]: Successfully claimed
IP address 169.254.5.190
Jul 6 19:37:39 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 9
Jul 6 19:37:48 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 15
Jul 6 19:38:03 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 13
Jul 6 19:38:16 gotojoy dhclient: DHCPDISCOVER on eth2 to
255.255.255.255 port 67 interval 8

Jul 6 19:38:24 gotojoy dhclient: No DHCPOFFERS received.
Jul 6 19:38:24 gotojoy dhclient: No working leases in persistent
database - sleeping.




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4C33ED7F.4010903@ultrasw.com">http://lists.debian.org/4C33ED7F.4010903@ultrasw.com
 
Old 07-07-2010, 03:28 AM
Celejar
 
Default wifi obtaining IP address

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,
> >
> > To diagnose this sort of thing, we need the logs (dmesg, syslog). Low
> > level tools are better than the high level, GUI stuff.
>
> Here are syslog entries from dhclient eth2 and dmegs showing the
> insertion of the PCMCIA card.
>
> Thanks,
>
> Paul
>
> dmesg:
>
> [ 1624.772201] pcmcia_socket pcmcia_socket1: pccard: PCMCIA card
> inserted into slot 1
> [ 1624.772239] pcmcia_socket pcmcia_socket1: cs: memory probe
> 0xa0000000-0xa0ffffff: clean.
> [ 1624.809253] pcmcia 1.0: pcmcia: registering new device pcmcia1.0
> [ 1625.729461] cfg80211: Using static regulatory domain info
> [ 1625.729481] cfg80211: Regulatory domain: US
> [ 1625.729492] (start_freq - end_freq @ bandwidth), (max_antenna_gain,
> max_eirp)
> [ 1625.729512] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
> [ 1625.729530] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> [ 1625.729549] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> [ 1625.729567] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> [ 1625.729584] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> [ 1625.729600] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
> [ 1625.730050] cfg80211: Calling CRDA for country: US
> [ 1626.033421] orinoco 0.15 (David Gibson
> <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
> [ 1626.077137] orinoco_cs 0.15 (David Gibson
> <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
> [ 1626.185881] orinoco_cs 1.0: Hardware identity 0001:0001:0004:0000
> [ 1626.185993] orinoco_cs 1.0: Station identity 001f:0001:0006:0010
> [ 1626.186018] orinoco_cs 1.0: Firmware determined as Lucent/Agere 6.16
> [ 1626.190614] orinoco_cs 1.0: firmware: requesting agere_sta_fw.bin
> [ 1626.866015] orinoco_cs 1.0: Hardware identity 0001:0001:0004:0000
> [ 1626.866155] orinoco_cs 1.0: Station identity 001f:0002:0009:0030
> [ 1626.866176] orinoco_cs 1.0: Firmware determined as Lucent/Agere 9.48
> [ 1626.866189] orinoco_cs 1.0: Ad-hoc demo mode supported
> [ 1626.866203] orinoco_cs 1.0: IEEE standard IBSS ad-hoc mode supported
> [ 1626.866218] orinoco_cs 1.0: WEP supported, 104-bit key
> [ 1626.866228] orinoco_cs 1.0: WPA-PSK supported
> [ 1627.656203] udev: renamed network interface eth1 to eth2
> [ 1629.008197] ADDRCONF(NETDEV_UP): eth2: link is not ready
> [ 1629.225289] eth2: New link status: Connected (0001)
> [ 1629.225495] ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
> [ 1630.720511] eth2: Lucent/Agere firmware doesn't support manual roaming
> [ 1635.918066] eth2: Lucent/Agere firmware doesn't support manual roaming
> [ 1640.216115] eth2: no IPv6 routers present
> [ 1641.125130] eth2: Lucent/Agere firmware doesn't support manual roaming
> [ 1646.302985] eth2: Lucent/Agere firmware doesn't support manual roaming
> [ 1651.624297] eth2: Lucent/Agere firmware doesn't support manual roaming
> [ 1659.181055] eth2: Lucent/Agere firmware doesn't support manual roaming
> [ 1664.379099] eth2: Lucent/Agere firmware doesn't support manual roaming
> [ 1669.586645] eth2: Lucent/Agere firmware doesn't support manual roaming
> [ 1674.783657] eth2: Lucent/Agere firmware doesn't support manual roaming
> [ 1679.989689] eth2: Lucent/Agere firmware doesn't support manual roaming

Okay, the card reports that it's connected. What's the output of 'iwconfig eth2'?

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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100706232841.edab9b37.celejar@gmail.com">http://lists.debian.org/20100706232841.edab9b37.celejar@gmail.com
 
Old 07-07-2010, 03:42 AM
Paul Scott
 
Default wifi obtaining IP address

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 thrff Fragment thrff
Encryption keyff
Power Managementff
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

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

Thanks,

Paul



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4C33F7A0.6020307@ultrasw.com">http://lists.debian.org/4C33F7A0.6020307@ultrasw.com
 
Old 07-07-2010, 03:54 AM
Celejar
 
Default wifi obtaining IP address

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 thrff Fragment thrff
> Encryption keyff
> Power Managementff
> 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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100706235430.080cf1db.celejar@gmail.com">http://lists.debian.org/20100706235430.080cf1db.celejar@gmail.com
 
Old 07-07-2010, 04:04 AM
Paul Scott
 
Default wifi obtaining IP address

On Tue, Jul 06, 2010 at 11:54:30PM -0400, Celejar wrote:
> 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:
> > >
> > > 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 thrff Fragment thrff
> > Encryption keyff
> > Power Managementff
> > 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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100707040420.GA10490@mail.ultrasw.com">http://lists.debian.org/20100707040420.GA10490@mail.ultrasw.com
 
Old 07-07-2010, 04:29 AM
Celejar
 
Default wifi obtaining IP address

On Tue, 6 Jul 2010 21:04:22 -0700
Paul Scott <waterhorse@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@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:
> > > >
> > > > 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 thrff Fragment thrff
> > > Encryption keyff
> > > Power Managementff
> > > 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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100707002908.a22adc1e.celejar@gmail.com">http://lists.debian.org/20100707002908.a22adc1e.celejar@gmail.com
 
Old 07-07-2010, 06:56 PM
Paul Scott
 
Default wifi obtaining IP address

On 07/06/2010 09:29 PM, Celejar wrote:

On Tue, 6 Jul 2010 21:04:22 -0700
Paul Scott<waterhorse@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@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:

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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4C34CDF4.6000506@ultrasw.com">http://lists.debian.org/4C34CDF4.6000506@ultrasw.com
 

Thread Tools




All times are GMT. The time now is 08:43 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org