From: Pavel Roskin <proski@gnu.org>
To: "Thiago F. Tavares" <ttavares@halogica.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Issue: iwlist scanning sees the network; dhclient can't connect
Date: Wed, 30 Jul 2008 15:36:42 -0400 [thread overview]
Message-ID: <1217446602.25919.5.camel@dv> (raw)
In-Reply-To: <1127857B97C63B4285A9B02BEF67AEE601627648@afrodite.halogica.com.br>
On Wed, 2008-07-30 at 16:13 -0300, Thiago F. Tavares wrote:
> Hello,
>
> I have a problem with the broadcom wireless card (BCM4306 using b43).
> I'm can list the wireless ESSIDs with "iwlist scanning" command, but I'm
> can't connect in the LAN. My dhclient or dhcpcd can't receive an IP.
> When I set a static IP, I can't ping the gateway.
dhclient is not suitable for wireless networking because it brings the
interface down briefly and breaks the connection. So I suggest that you
use static addresses or a DHCP client that doesn't bring the interface
down.
Please check iwconfig output. In particular, please see "access point"
and "link quality". If the later is 0, there is no association. If
there is no association, no IP packets can go through. Try
reestablishing the association by setting ESSID with iwconfig while the
interface is up.
Also please see the kernel log for possible signs of trouble. It's
shown by the "dmesg" command.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-07-30 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 19:13 Issue: iwlist scanning sees the network; dhclient can't connect Thiago F. Tavares
2008-07-30 19:36 ` Pavel Roskin [this message]
2008-07-30 19:41 ` Michael Buesch
2008-07-30 19:51 ` Pavel Roskin
2008-07-31 8:41 ` Johannes Berg
2008-07-31 13:31 ` Michael Buesch
2008-07-31 13:49 ` Dan Williams
2008-07-31 15:01 ` Pavel Roskin
2008-07-31 20:01 ` Dan Williams
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=1217446602.25919.5.camel@dv \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ttavares@halogica.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).