From: Jeremy Moles <jeremy@emperorlinux.com>
To: linux-wireless@vger.kernel.org
Subject: iwlagn + Ad-Hoc + 5Ghz
Date: Fri, 20 Nov 2009 17:37:27 -0500 [thread overview]
Message-ID: <1258756647.2714.17.camel@localhost.localdomain> (raw)
Hello all! I have a group of machine here with an app that needs to set
up an ad-hoc network in 5Ghz+ range. The machines themselves are all
different (a Panasonic, a Dell, and a Lenovo) but they are all using
5100 cards, a 2.6.31 kernel, and the 2.6.31-rc7 driver from the website.
Using the command "iw list" I can get a lot of helpful info, but I see
"no IBSS" on any channel over 11, and I'm beginning to think that this
just isn't supported on these cards yet. Am I right here, or is it in
fact supported and I am just missing something? Could the hardware,
perhaps, be configured on a very low level to not allow something like
this?
Thanks in advance. :)
next reply other threads:[~2009-11-20 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 22:37 Jeremy Moles [this message]
2009-11-20 23:26 ` iwlagn + Ad-Hoc + 5Ghz Luis R. Rodriguez
2009-11-21 8:51 ` Benoit PAPILLAULT
2009-11-21 17:21 ` Patrick Grimm
2009-11-21 18:19 ` Luis R. Rodriguez
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=1258756647.2714.17.camel@localhost.localdomain \
--to=jeremy@emperorlinux.com \
--cc=linux-wireless@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox