All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Kilroy <kilroyd@googlemail.com>
To: Dan Williams <dcbw@redhat.com>
Cc: zaphod@berentweb.com, linux-wireless@vger.kernel.org
Subject: Re: orinoco (Lucent/Agere 9.48) unable to connect
Date: Tue, 05 Nov 2013 23:17:17 +0000	[thread overview]
Message-ID: <52797C7D.9020906@gmail.com> (raw)
In-Reply-To: <1383596955.29469.2.camel@dcbw.foobar.com>

On 04/11/2013 20:29, Dan Williams wrote:
> On Mon, 2013-11-04 at 20:42 +0200, Beeblebrox wrote:
>>> What kind of access point are you trying to connect to?  These devices
>>> only support 802.11b, so if the access point is newer and is using
>>> 802.11n, there are some 11n configurations that simply don't support
>>> connections from 11b clients.
>>> Dan
>> Hi Dan, thanks for your answer.
>> The test A/P is a USR-5451-maxG with ddwrt as OS. A/P is on mixed mode
>> (B+G), but after your mail I tried B-Only mode, which failed also.
>> While observing the connection process, I got the feeling that the
>> orinoco card (eth1) is unable to set an IP. I have tried static and
>> dhclient, with same effect. Shortly after the connection process
>> starts, the card status shows as connected, but does not finalize .
>> Process then terminates (assuming because no IP is agreed on with AP).
>>
>> Please advise what other info/test I can try.
> If you're able, can you use wireshark on another computer to capture the
> 802.11 frames exchanged between the orinico device and the AP?
>
Check whether you're using wext or cfg80211. IIRC, you have to use wext. 
If that's not working, the relevant bits of wpa_supplicant log (-ddd) 
would be helpful.


Dave.

      reply	other threads:[~2013-11-05 23:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 10:53 orinoco (Lucent/Agere 9.48) unable to connect Beeblebrox
2013-11-04 16:18 ` Dan Williams
2013-11-04 18:42   ` Beeblebrox
2013-11-04 20:29     ` Dan Williams
2013-11-05 23:17       ` Dave Kilroy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52797C7D.9020906@gmail.com \
    --to=kilroyd@googlemail.com \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zaphod@berentweb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.