headers
Anish Mistry | 1 May 2008 05:23
Picon
Favicon

iwn can't associate with AP

I'm trying to get the iwn card in my laptop to work.  It's detected 
and the wlan device is created, but it can't associate with the 
access point.

If I turn on debugging I get:

Apr 30 23:08:57 smallguy wpa_supplicant[451]: Trying to associate with 
00:d0:41:a3:9a:31 (SSID='drago' freq=2412 MHz)
Apr 30 23:09:07 smallguy wpa_supplicant[451]: Authentication with 
00:d0:41:a3:9a:31 timed out.
Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 1 
status 1
Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 6 
status 1
Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 11 
status 1
Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 7 
status 1
Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 52 
status 1
Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 56 
status 1
Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 60 
status 1
Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 64 
status 1
Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 36 
status 1
Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 40 
status 1
(Continue reading)

Permalink | Reply | 1 comment |
headers
Anish Mistry | 1 May 2008 06:07
Picon
Favicon

Re: iwn can't associate with AP

On Wednesday 30 April 2008, Anish Mistry wrote:
> I'm trying to get the iwn card in my laptop to work.  It's detected
> and the wlan device is created, but it can't associate with the
> access point.
>
> If I turn on debugging I get:
>
> Apr 30 23:08:57 smallguy wpa_supplicant[451]: Trying to associate
> with 00:d0:41:a3:9a:31 (SSID='drago' freq=2412 MHz)
> Apr 30 23:09:07 smallguy wpa_supplicant[451]: Authentication with
> 00:d0:41:a3:9a:31 timed out.
> Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 1
> status 1
> Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 6
> status 1
> Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel
> 11 status 1
> Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel 7
> status 1
> Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel
> 52 status 1
> Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel
> 56 status 1
> Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel
> 60 status 1
> Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel
> 64 status 1
> Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel
> 36 status 1
> Apr 30 23:09:07 smallguy kernel: iwn_notif_intr: scanning channel
(Continue reading)

Permalink | Reply | 0 comments |
headers
Fabian Keil | 1 May 2008 16:39
Picon
Favicon

Re: Connection problems with wme enabled

Sam Leffler <sam <at> freebsd.org> wrote:

> It would still be worth understanding why WME operation breaks iwi; 
> please provide logs showing what is happening.

Where would I get meaningful logs?

dmesg doesn't show any relevant messages,
even when booted in verbose mode.

The ifconfig output looks normal (to me) as well:

fk <at> TP51 ~ $sudo ifconfig -v wlan0
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 00:0e:...
        inet 192.168.0.49 netmask 0xffffff00 broadcast 192.168.0.255
        media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
        status: associated
        ssid ... channel 7 (2442 Mhz 11g) bssid 00:14:...
        regdomain DEBUG country DE anywhere -ecm authmode OPEN -wps -tsn
        privacy ON deftxkey 1
        wepkey 1:104-bit powersavemode OFF powersavesleep 100 txpower 30
        txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346 bmiss 24
        11b    ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
        11g    ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
        11na   ucast NONE    mgmt  0 MCS  mcast  0 MCS  maxretry 6
        11ng   ucast NONE    mgmt  0 MCS  mcast  0 MCS  maxretry 6
        scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250
        roam:11b    rssi    7dBm rate  1 Mb/s
        roam:11g    rssi    7dBm rate  5 Mb/s -pureg protmode CTS -ht
(Continue reading)

Permalink | Reply | 4 comments |
headers
Sam Leffler | 1 May 2008 17:36
Picon
Favicon

Re: Connection problems with wme enabled

Fabian Keil wrote:
> Sam Leffler <sam <at> freebsd.org> wrote:
>
>   
>> It would still be worth understanding why WME operation breaks iwi; 
>> please provide logs showing what is happening.
>>     
>
> Where would I get meaningful logs?
>   

man wlandebug.  If the 802.11-related activity doesn't show you what you 
want then try driver-level debugging.  This should be controlled through 
sysctl dev.iwi.X.debug but some drivers still use debug.iwi or similar.

> dmesg doesn't show any relevant messages,
> even when booted in verbose mode.
>
> The ifconfig output looks normal (to me) as well:
>
> fk <at> TP51 ~ $sudo ifconfig -v wlan0
> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>         ether 00:0e:...
>         inet 192.168.0.49 netmask 0xffffff00 broadcast 192.168.0.255
>         media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
>         status: associated
>         ssid ... channel 7 (2442 Mhz 11g) bssid 00:14:...
>         regdomain DEBUG country DE anywhere -ecm authmode OPEN -wps -tsn
>         privacy ON deftxkey 1
>         wepkey 1:104-bit powersavemode OFF powersavesleep 100 txpower 30
(Continue reading)

Permalink | Reply | 3 comments |
headers
Peter Schuller | 1 May 2008 18:15
Gravatar

Re: ZFS file caching question

> on FreeBSD.  This is inefficient in a number of ways.  I have also seen
> things that make me suspicious that it is not caching properly even when
> you tune it to be "large enough" (if possible given memory constraints),
> but I haven't confirmed this.

FWIW, I have had some suspiciouns here too strictly from a user-centric point 
of view.

Most recently I found that I could not get ZFS to cache enough such 
that "pkg_info" would not have to get down on disk (thus making all package 
installation and similar dead-slow, due to the number of times /var/db/pkg is 
accesses in deep dependency hierarchies).

In this case I tended up killing as much as I could  on the machine (web 
browsers, MUA:s, whatever else), on the theory that large files being kept 
open would affect the caching strategy. Even after killing most stuff and 
after multiple pkg_info:s (to accumulate frequency), it was still only 
caching enough for perhaps 20% of what pkg_info needs on this machine (when 
invoked without arguments, listing all packages).

I don't know if this is just a result of giving too much weight to past 
history or if there is an actual bug somewhere; but the perceived end-result 
for me as a user was clearly significantly worse than a plain page-wise LRU 
would have given.

I ended up rebooting the machine to get package upgrades to complete within a 
reasonable amount of time.

This was on my 64 bit desktop machine with:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Fabian Keil | 1 May 2008 20:11
Picon
Favicon

Re: Connection problems with wme enabled

Sam Leffler <sam <at> freebsd.org> wrote:

> Fabian Keil wrote:
> > Sam Leffler <sam <at> freebsd.org> wrote:

> > dmesg doesn't show any relevant messages,
> > even when booted in verbose mode.
> >
> > The ifconfig output looks normal (to me) as well:
> >
> > fk <at> TP51 ~ $sudo ifconfig -v wlan0
> > wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> >         ether 00:0e:...
> >         inet 192.168.0.49 netmask 0xffffff00 broadcast 192.168.0.255
> >         media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
> >         status: associated
> >         ssid ... channel 7 (2442 Mhz 11g) bssid 00:14:...
> >         regdomain DEBUG country DE anywhere -ecm authmode OPEN -wps -tsn
> >         privacy ON deftxkey 1
> >         wepkey 1:104-bit powersavemode OFF powersavesleep 100 txpower 30
> >         txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346 bmiss 24
> >         11b    ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
> >         11g    ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
> >         11na   ucast NONE    mgmt  0 MCS  mcast  0 MCS  maxretry 6
> >         11ng   ucast NONE    mgmt  0 MCS  mcast  0 MCS  maxretry 6
> >         scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250
> >         roam:11b    rssi    7dBm rate  1 Mb/s
> >         roam:11g    rssi    7dBm rate  5 Mb/s -pureg protmode CTS -ht
> >         -htcompat -ampdu ampdulimit 8k ampdudensity - -amsdu -shortgi
> >         htprotmode RTSCTS -puren wme -burst -ff -dturbo -dwds roaming AUTO
(Continue reading)

Permalink | Reply | 2 comments |
headers
Sam Leffler | 1 May 2008 22:25
Picon
Favicon

Re: Connection problems with wme enabled

Fabian Keil wrote:
> Sam Leffler <sam <at> freebsd.org> wrote:
>
>   
>> Fabian Keil wrote:
>>     
>>> Sam Leffler <sam <at> freebsd.org> wrote:
>>>       
>
>   
>>> dmesg doesn't show any relevant messages,
>>> even when booted in verbose mode.
>>>
>>> The ifconfig output looks normal (to me) as well:
>>>
>>> fk <at> TP51 ~ $sudo ifconfig -v wlan0
>>> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>>>         ether 00:0e:...
>>>         inet 192.168.0.49 netmask 0xffffff00 broadcast 192.168.0.255
>>>         media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
>>>         status: associated
>>>         ssid ... channel 7 (2442 Mhz 11g) bssid 00:14:...
>>>         regdomain DEBUG country DE anywhere -ecm authmode OPEN -wps -tsn
>>>         privacy ON deftxkey 1
>>>         wepkey 1:104-bit powersavemode OFF powersavesleep 100 txpower 30
>>>         txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346 bmiss 24
>>>         11b    ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
>>>         11g    ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
>>>         11na   ucast NONE    mgmt  0 MCS  mcast  0 MCS  maxretry 6
>>>         11ng   ucast NONE    mgmt  0 MCS  mcast  0 MCS  maxretry 6
(Continue reading)

Permalink | Reply | 1 comment |
headers
David Cornejo | 1 May 2008 22:34
Picon

Re: problems making an access point w/current

from dmesg:

ath0: mac 5.9 phy 4.3 radio 3.6
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

[root <at> ap2] 111% ifconfig -v wlan0
wlan0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
metric 0 mtu 2290
        ether 00:0b:6b:34:65:99
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11a <hostap>
        status: running
        ssid hmiln channel 52 (5260 Mhz 11a) bssid 00:0b:6b:34:65:99
        regdomain DEBUG country US anywhere ecm authmode WPA -wps -tsn
        privacy MIXED deftxkey 2
        TKIP 2:128-bit
        TKIP 3:128-bit powersavemode OFF powersavesleep 100 txpower 19
        txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346 bmiss 7
        11a    ucast NONE    mgmt  6 Mb/s mcast  6 Mb/s maxretry 6
        11b    ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
        11g    ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
        turboA ucast NONE    mgmt  6 Mb/s mcast  6 Mb/s maxretry 6
        11na   ucast NONE    mgmt  0 MCS  mcast  0 MCS  maxretry 6
        11ng   ucast NONE    mgmt  0 MCS  mcast  0 MCS  maxretry 6
        scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250
        roam:11a    rssi    7dBm rate 12 Mb/s
        roam:11b    rssi    7dBm rate  1 Mb/s
        roam:11g    rssi    7dBm rate  5 Mb/s
        roam:turboA rssi    7dBm rate 12 Mb/s
        roam:sturbo rssi    7dBm rate 12 Mb/s -pureg protmode CTS -ht
        -htcompat -ampdu ampdulimit 8k ampdudensity - -amsdu -shortgi
(Continue reading)

Permalink | Reply | 10 comments |
headers
Ben Kaduk | 2 May 2008 00:46
Picon

Re: HEADSUP: 802.11 vap support merged

On 4/27/08, Andrew Thompson <thompsa <at> freebsd.org> wrote:
> On Sat, Apr 26, 2008 at 08:57:27PM -0400, Ben Kaduk wrote:
>  > Hi Sam,
>  >
>  > On 4/22/08, Sam Leffler <sam <at> errno.com> wrote:
>  > > From UPDATING:
>  > >
>  > >  20080420:
>  > >        The 802.11 wireless support was redone to enable multi-bss
>  > >        operation on devices that are capable.  The underlying device
>  > >        is no longer used directly but instead wlanX devices are
>  > >        cloned with ifconfig.  This requires changes to rc.conf files.
>  > >
>  >
>  > Again, sorry for jumping in late.
>  >
>  > Do I interpret this correctly as that it is unsupported, now, to
>  > do something like `ifconfig ndis0 up`?
>  > In my present configuration, I can do:
>  > ifconfig wlan0 create wlandev ndis0
>  > ifconfig ndis0 up
>  > ...
>  > and get a useable connection, but:
>  > ifconfig ndis0 up
>  > gives me a panic (hand transcribed)
>  > Fatal trap 12: page fault while in kernel mode
>  > ndis_setstate_80211
>
>
> I can see why this would happen, can you try this patch.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Sam Leffler | 2 May 2008 01:28
Picon
Favicon

Re: problems making an access point w/current

Are you certain hostapd is up to date?  There was a bug like this a 
while back (before code was committed to CVS) when I failed to update 
hostapd to plumb keys correctly.  I routinely test this same config 
(i.e. card) w/o any issues.

    Sam

David Cornejo wrote:
> from dmesg:
>
> ath0: mac 5.9 phy 4.3 radio 3.6
> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
>
> [root <at> ap2] 111% ifconfig -v wlan0
> wlan0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
> metric 0 mtu 2290
>         ether 00:0b:6b:34:65:99
>         media: IEEE 802.11 Wireless Ethernet autoselect mode 11a <hostap>
>         status: running
>         ssid hmiln channel 52 (5260 Mhz 11a) bssid 00:0b:6b:34:65:99
>         regdomain DEBUG country US anywhere ecm authmode WPA -wps -tsn
>         privacy MIXED deftxkey 2
>         TKIP 2:128-bit
>         TKIP 3:128-bit powersavemode OFF powersavesleep 100 txpower 19
>         txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346 bmiss 7
>         11a    ucast NONE    mgmt  6 Mb/s mcast  6 Mb/s maxretry 6
>         11b    ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
>         11g    ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
>         turboA ucast NONE    mgmt  6 Mb/s mcast  6 Mb/s maxretry 6
>         11na   ucast NONE    mgmt  0 MCS  mcast  0 MCS  maxretry 6
(Continue reading)

Permalink | Reply | 7 comments |

Gmane