#778: upgrading madwifi, ubuntu breaks wireless on thinkpad
---------------------------------------+------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: other | Version: trunk
Resolution: | Keywords: ubuntu, thinkpad,
regression
Patch_attached: 0 |
---------------------------------------+------------------------------------
Changes (by mrenzmann):
* milestone: version 0.9.2 =>
Comment:
Please: don't assign a new ticket to a milestone until you know exactly
what you are doing. The reported issues surely won't be addressed in
release 0.9.2 (which will be released during the next hours). In fact,
they are not even classified and I'm not sure if they are bugs in MadWifi
at all.
Furthermore, support requests should be directed to the appropriate
[wiki:Resources#MailingLists mailing lists] rather than filing a ticket
for it (unless it's clear that the report is dealing with a real bug).
Anyway:
{{{
#!blockquote
Specifically, DHCP to a hub sitting ten centimeters away is successful but
only a small fraction of ping packets to the hub receive a response; I
expect every packet to receive a response.
}}}
Your WLAN card can not communicate directly with hubs (which are wire-
bound devices, in contrast to the wire-less stuff that WLAN deals with).
However, I think you have just accidentally chosen the wrong term and
actually referred to an Access Point (AP).
In that case you should take care that the distance between the AP and its
clients should not become too low, otherwise the [wiki:FAQ/SignalTooStrong
signal is too strong], the receiving card in the clients become saturated
and it will suffer from a horrible throughput. Seeing a high number of
lost pings is one of the related symptoms, for example.
{{{
#!blockquote
DHCP to farther-away hubs receives no response; I expect it to pick up an
IP address.
}}}
It's a bit unclear if your setup is sufficient for DHCP. For example, you
didn't mention which DHCP client software you are running, and if there is
actually a DHCP server reachable through the AP you're connecting to.
A [wiki:UserDocs/Troubleshooting#IcannotgetanIPwithDHCP common problem] in
this context is that the DHCP client gets started before the WLAN card has
properly associated with the AP. As a comparisson: you surely would not
expect to see a successful DHCP request/response sequence without having
your computer's ethernet card being connected properly with your network.
A more detailed description of your setup surely would help to determine
if the common requirements are met.
{{{
#!blockquote
What tools are available for debugging wireless problems?
}}}
In addition to what Kel already said, it might be worth to have a look at
the man pages of ''athdebug'' and ''80211debug''. The common
[http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html wireless
tools] are useful for roughly determining the link quality and stuff like
that. Having a network sniffer available, sitting between AP and DHCP
server, might also be a good idea in case your diving deeper into
debugging your issues.
--- M. Renzmann, Development and technical administration, madwifi.org
project
--
Ticket URL: <http://madwifi.org/ticket/778>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
