Re: ath cannot find my wireless network any more

Lars Engels wrote:
> On Thu, Jan 29, 2009 at 10:28:03PM +0100, Paul B. Mahol wrote:
>> On 1/29/09, Lars Engels <lme_at_freebsd.org> wrote:
>>> On Thu, Jan 29, 2009 at 12:16:44PM -0800, Sam Leffler wrote:
>>>> Lars Engels wrote:
>>>>> On Thu, Jan 29, 2009 at 11:28:30AM -0800, Andrew Thompson wrote:
>>>>>
>>>>>> On Thu, Jan 29, 2009 at 08:22:41PM +0100, Lars Engels wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>> hi Sam,
>>>>>>>
>>>>>>> I just build world && kernel from todays sources.
>>>>>>> Now my Atheros 5212 pccard cannot find my wireless network any more,
>>>>>>> but
>>>>>>> still sees other networks:
>>>>>>>
>>>>>>> lars_at_pts/3 # ifconfig wlan0 up scan
>>>>>>> SSID            BSSID              CHAN RATE   S:N     INT CAPS
>>>>>>> Arcor-C6DE58    00:1a:2a:c6:de:56    9   54M -95:-96  100 EPS  RSN WPA
>>>>>>> WME
>>>>>>> WLAN-AFCB47     00:1d:19:af:cb:e0    1   54M -96:-96  100 EPS  WPS RSN
>>>>>>> WPA WME
>>>>>>> 0x0000          00:03:c9:54:18:bb    8   54M -94:-96  100 EP   WPA
>>>>>>>
>>>>>>> In contrast to this, the internal wpi chip still finds and connects to
>>>>>>> the network:
>>>>>>> lars_at_pts/3 # ifconfig wlan1 scan
>>>>>>> SSID            BSSID              CHAN RATE   S:N     INT CAPS
>>>>>>> dd-wrt          00:18:39:c7:6a:dd    6   54M  22:0    100 EP   RSN WME
>>>>>>>
>>>>>>> I also don't know why wpi only finds my own network.
>> If such behavior was from start(not regression) it can means only wpi
>> problem/feature.
> 
> I can't tell because I haven't used wpi for months... But now I am glad
> that it can still connect to my wireless network. :)
> 
>>> So I ran
>>> # wlandebug -i wlan0 scan
>>> net.wlan.0.debug: 0x0 => 0x200000<scan>
>>>
>>> But nothing new then:
>> Interesting output is not available from ifconfig it is printed by
>> kernel on console.
> 
> Ahhh, thanks for the hint. There's a lot of scanning going on in
> /var/log/messages but no sign of my own network.


Unfortunately you haven't shown what this output is.  I asked you to do
it to be sure the scan visited the channel w/ your ap and/or whether it
sent a probe request frame or saw a beacon from the ap.  The hal changes
should not have altered anything for you because your eeprom setup
appears to have default settings.  I've been running these changes for a
while but I'm likely testing different things than you.

If you can send me the debug output it might help (feel free to send it
directly).  Otherwise you might try reverting the change.  Since you
still haven't sent me the mac+phy revs for your card I can't try to
reproduce your setup.

	Sam