output of ifconfig list scan
Paul B. Mahol
onemda at gmail.com
Fri May 1 01:04:19 UTC 2009
On 4/30/09, Jeroen Hofstee <freebsd.questions at virtualhost.nl> wrote:
> Paul B. Mahol wrote:
>>> It appears that the tool assumes SSID are reported as
>>> SSID<session>, which is not the case here. My list is similar as listed
>>> in the handbook,
>>>
>>> Looking at ifconfig, it appears to me that the ieee80211 part queries
>>> the kernel and prints the returned values.
>>> I therefore assume that there are drivers, which report the session as
>>> SSID<session> instead of session directly.
>>>
>>
>> Whatever <session> means it is either not supported by NDIS or not
>> implemented
>> in ndisulator.
>>
> Perhaps I should explain my question a bit better. The <session> is just
> mentioned as an example.
> With the ndiswrapper the wifi is working proper and lists the available
> network (only mine shown), e.g.
>
> SSID BSSID CHAN RATE S:N INT CAPS
> DV201AM 00:13:d4:7a:16:b1 1 54M -51:-96 100 EP
> ....
>
> The wificonfig tool _assumes_ the output of ifconfig would look like.
> SSID BSSID CHAN RATE S:N INT CAPS
> SSID<DV201AM> 00:13:d4:7a:16:b1 1 54M -51:-96 100 EP
> ....
>
> My question is if there are wifi drivers which report the SSID like
> this, instead of reporting them
> directly as in my case and if so how the output is formatted in that case.
This is first time I heard about this, and looks like wificonfig tool bug.
--
Paul
More information about the freebsd-questions
mailing list