[gentoo-user] Wireless Configuration...

[gentoo-user] Wireless Configuration...

[BRM]

I still haven't decided what to get for my system to replace the NIC with, but the card I have should be working with my existing 802.11g network already; however, it doesn't - I have had to connect my laptop via Ethernet cable to my wireless bridge to get network access.

/etc/init.d/net.wlan0 starts, but goes immediately inactive. From what I can find on-line, this seems to have been something common after moving to Base Layout 2/OpenRC; however, I couldn't find anything that specified what the actual solution was - I think most ended up doing a complete reinstall of their wicd/wpa-supplicant software - either way details were lacking.  I've successfully had wpa-supplicant working in the past, and as a result of all of this I've tried to get it up through the other method too (iwconfig?), but no success. (I think I have managed to get it to scan some, but not sufficiently and certainly no connections.)


Anyone see this issue and know what the solution is? I'd like to at least get my 802.11g access back - the current setup is a bit of a pain and very limiting.

Thanks!

Ben

Re: [gentoo-user] Wireless Configuration...

[Canek Peláez Valdés]

On Thu, Sep 1, 2011 at 11:52 PM, BRM <bm_witness@yahoo.com> wrote:
> I still haven't decided what to get for my system to replace the NIC with, but the card I have should be working with my existing 802.11g network already; however, it doesn't - I have had to connect my laptop via Ethernet cable to my wireless bridge to get network access.
>
> /etc/init.d/net.wlan0 starts, but goes immediately inactive. From what I can find on-line, this seems to have been something common after moving to Base Layout 2/OpenRC; however, I couldn't find anything that specified what the actual solution was - I think most ended up doing a complete reinstall of their wicd/wpa-supplicant software - either way details were lacking.  I've successfully had wpa-supplicant working in the past, and as a result of all of this I've tried to get it up through the other method too (iwconfig?), but no success. (I think I have managed to get it to scan some, but not sufficiently and certainly no connections.)

Did you followed the instructions at

http://www.gentoo.org/doc/en/openrc-migration.xml

specifically the network section?

> Anyone see this issue and know what the solution is? I'd like to at least get my 802.11g access back - the current setup is a bit of a pain and very limiting.

Since you use a laptop, I will assume you have either KDE, GNOME or
Xfce. If that's the case, why don't you try NetworkManager or connman,
and use the GUI thingy to do the work for you? I haven't manually
configured a wireless network in years, and I have been the last three
months traveling with my laptop literally all over the world,
connecting to all kinds of access points.

NetworkMnager just works, but I also hear great comments about connman.

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Re: [gentoo-user] Wireless Configuration...

[BRM]

----- Original Message -----

> From: Canek Peláez Valdés <caneko@gmail.com>
> On Thu, Sep 1, 2011 at 11:52 PM, BRM <bm_witness@yahoo.com> wrote:
>>  I still haven't decided what to get for my system to replace the NIC 
> with, but the card I have should be working with my existing 802.11g network 
> already; however, it doesn't - I have had to connect my laptop via Ethernet 
> cable to my wireless bridge to get network access.
>> 
>>  /etc/init.d/net.wlan0 starts, but goes immediately inactive. From what I 
> can find on-line, this seems to have been something common after moving to Base 
> Layout 2/OpenRC; however, I couldn't find anything that specified what the 
> actual solution was - I think most ended up doing a complete reinstall of their 
> wicd/wpa-supplicant software - either way details were lacking.  I've 
> successfully had wpa-supplicant working in the past, and as a result of all of 
> this I've tried to get it up through the other method too (iwconfig?), but 
> no success. (I think I have managed to get it to scan some, but not sufficiently 
> and certainly no connections.)
> 
> Did you followed the instructions at
> 
> http://www.gentoo.org/doc/en/openrc-migration.xml
> 
> specifically the network section?

Yes, I believe so. It's been a while since I made the migration, but the wireless configuration seems to have broken about the same time.

The wired configuration works just fine, and the guide mentions nothing about Wireless changes - e.g. WPA Supplicant - and that's where the problem is.
 
>>  Anyone see this issue and know what the solution is? I'd like to at 
> least get my 802.11g access back - the current setup is a bit of a pain and very 
> limiting.
> 
> Since you use a laptop, I will assume you have either KDE, GNOME or
> Xfce. If that's the case, why don't you try NetworkManager or connman,
> and use the GUI thingy to do the work for you? I haven't manually
> configured a wireless network in years, and I have been the last three
> months traveling with my laptop literally all over the world,
> connecting to all kinds of access points.
> NetworkMnager just works, but I also hear great comments about connman.

I'm using KDE, yes. I've tried the tools but it doesn't seem to ever scan for a wireless network on its own, and the scans I have been able to force don't result in a connection - they don't even find the network I'm trying to attach it to.  Prior to the change, I could get WPA Supplicant to connect to my wireless, though I did have to have it specifically configured to do so. It wouldn't typically work using the tools for the one wireless network, while I could get it to for others (hotels, other places, etc.).

I have added another network that is configured a little differently that I would prefer to connect to (over the old one), but at the moment I'll take either. (The new 802.11g network uses WPA2; the old one uses WEP+Shared.)

Ben

Re: [gentoo-user] Wireless Configuration...

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 3413 bytes --]

On Friday 02 Sep 2011 14:38:56 BRM wrote:
> ----- Original Message -----
> 
> > From: Canek Peláez Valdés <caneko@gmail.com>
> > 
> > On Thu, Sep 1, 2011 at 11:52 PM, BRM <bm_witness@yahoo.com> wrote:
> >>  I still haven't decided what to get for my system to replace the NIC
> > 
> > with, but the card I have should be working with my existing 802.11g
> > network already; however, it doesn't - I have had to connect my laptop
> > via Ethernet cable to my wireless bridge to get network access.
> > 
> >>  /etc/init.d/net.wlan0 starts, but goes immediately inactive. From what
> >>  I
> > 
> > can find on-line, this seems to have been something common after moving
> > to Base Layout 2/OpenRC; however, I couldn't find anything that
> > specified what the actual solution was - I think most ended up doing a
> > complete reinstall of their wicd/wpa-supplicant software - either way
> > details were lacking.  I've successfully had wpa-supplicant working in
> > the past, and as a result of all of this I've tried to get it up through
> > the other method too (iwconfig?), but no success. (I think I have
> > managed to get it to scan some, but not sufficiently and certainly no
> > connections.)
> > 
> > Did you followed the instructions at
> > 
> > http://www.gentoo.org/doc/en/openrc-migration.xml
> > 
> > specifically the network section?
> 
> Yes, I believe so. It's been a while since I made the migration, but the
> wireless configuration seems to have broken about the same time.
> 
> The wired configuration works just fine, and the guide mentions nothing
> about Wireless changes - e.g. WPA Supplicant - and that's where the
> problem is. 
> 
> >>  Anyone see this issue and know what the solution is? I'd like to at
> > 
> > least get my 802.11g access back - the current setup is a bit of a pain
> > and very limiting.
> > 
> > Since you use a laptop, I will assume you have either KDE, GNOME or
> > Xfce. If that's the case, why don't you try NetworkManager or connman,
> > and use the GUI thingy to do the work for you? I haven't manually
> > configured a wireless network in years, and I have been the last three
> > months traveling with my laptop literally all over the world,
> > connecting to all kinds of access points.
> > NetworkMnager just works, but I also hear great comments about connman.
> 
> I'm using KDE, yes. I've tried the tools but it doesn't seem to ever scan
> for a wireless network on its own, and the scans I have been able to force
> don't result in a connection - they don't even find the network I'm trying
> to attach it to.  Prior to the change, I could get WPA Supplicant to
> connect to my wireless, though I did have to have it specifically
> configured to do so. It wouldn't typically work using the tools for the
> one wireless network, while I could get it to for others (hotels, other
> places, etc.).
> 
> I have added another network that is configured a little differently that I
> would prefer to connect to (over the old one), but at the moment I'll take
> either. (The new 802.11g network uses WPA2; the old one uses WEP+Shared.)

Assuming that you have built in your kernel or loaded the driver module for 
your NIC and any firmware blobs have also been loaded, please show:

 /etc/conf.d/net 

and  

 grep ^[^#] /etc/wpa_supplicant/wpa_supplicant.conf

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Wireless Configuration...

[BRM]

----- Original Message -----

> From: Mick <michaelkintzios@gmail.com>
> To: gentoo-user@lists.gentoo.org
> Cc: 
> Sent: Friday, September 2, 2011 11:29 AM
> Subject: Re: [gentoo-user] Wireless Configuration...
> 
> On Friday 02 Sep 2011 14:38:56 BRM wrote:
>>  ----- Original Message -----
>> 
>>  > From: Canek Peláez Valdés <caneko@gmail.com>
>>  > 
>>  > On Thu, Sep 1, 2011 at 11:52 PM, BRM <bm_witness@yahoo.com> 
> wrote:
>>  >>  I still haven't decided what to get for my system to replace 
> the NIC
>>  > 
>>  > with, but the card I have should be working with my existing 802.11g
>>  > network already; however, it doesn't - I have had to connect my 
> laptop
>>  > via Ethernet cable to my wireless bridge to get network access.
>>  > 
>>  >>  /etc/init.d/net.wlan0 starts, but goes immediately inactive. From 
> what
>>  >>  I
>>  > 
>>  > can find on-line, this seems to have been something common after 
> moving
>>  > to Base Layout 2/OpenRC; however, I couldn't find anything that
>>  > specified what the actual solution was - I think most ended up doing a
>>  > complete reinstall of their wicd/wpa-supplicant software - either way
>>  > details were lacking.  I've successfully had wpa-supplicant 
> working in
>>  > the past, and as a result of all of this I've tried to get it up 
> through
>>  > the other method too (iwconfig?), but no success. (I think I have
>>  > managed to get it to scan some, but not sufficiently and certainly no
>>  > connections.)
>>  > 
>>  > Did you followed the instructions at
>>  > 
>>  > http://www.gentoo.org/doc/en/openrc-migration.xml
>>  > 
>>  > specifically the network section?
>> 
>>  Yes, I believe so. It's been a while since I made the migration, but 
> the
>>  wireless configuration seems to have broken about the same time.
>> 
>>  The wired configuration works just fine, and the guide mentions nothing
>>  about Wireless changes - e.g. WPA Supplicant - and that's where the
>>  problem is. 
>> 
>>  >>  Anyone see this issue and know what the solution is? I'd like 
> to at
>>  > 
>>  > least get my 802.11g access back - the current setup is a bit of a 
> pain
>>  > and very limiting.
>>  > 
>>  > Since you use a laptop, I will assume you have either KDE, GNOME or
>>  > Xfce. If that's the case, why don't you try NetworkManager or 
> connman,
>>  > and use the GUI thingy to do the work for you? I haven't manually
>>  > configured a wireless network in years, and I have been the last three
>>  > months traveling with my laptop literally all over the world,
>>  > connecting to all kinds of access points.
>>  > NetworkMnager just works, but I also hear great comments about 
> connman.
>> 
>>  I'm using KDE, yes. I've tried the tools but it doesn't seem to 
> ever scan
>>  for a wireless network on its own, and the scans I have been able to force
>>  don't result in a connection - they don't even find the network 
> I'm trying
>>  to attach it to.  Prior to the change, I could get WPA Supplicant to
>>  connect to my wireless, though I did have to have it specifically
>>  configured to do so. It wouldn't typically work using the tools for the
>>  one wireless network, while I could get it to for others (hotels, other
>>  places, etc.).
>> 
>>  I have added another network that is configured a little differently that I
>>  would prefer to connect to (over the old one), but at the moment I'll 
> take
>>  either. (The new 802.11g network uses WPA2; the old one uses WEP+Shared.)
> 
> Assuming that you have built in your kernel or loaded the driver module for 
> your NIC and any firmware blobs have also been loaded, please show:

Yes. As I noted, it's worked before. The driver loads it find the firmware, etc.
Configuration information is below.
 
> /etc/conf.d/net 

# This is a network block that connects to any unsecured access point.
# We give it a low priority so any defined blocks are preferred.
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
#ctrl_interface_group=wheel
ap_scan=1
fast_reauth=1
# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d.  To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).

# Standard Network:
config_eth0=( "dhcp" )

dns_domain_lo="coal"
# Wireless Network:
# TBD
#config_wlan0 ( "wpa_supplicant" )
#

# Enable this to use WPA supplicant; however, need to change the configuration of the Wireless first.
modules=( "!plug" "!iwconfig" "wpa_supplicant" )
#modules=( "!plug" "wpa_supplicant" )
#modules=("iwconfig")
#wpa_supplicant_wlan0="-Dwext"
#wpa_timeout_wlan0=15

#modules=("iwconfig")
#iwconfig_wlan0="mode managed"
#wpa_timeout_wlan0=15
 
> and  
> 
> grep ^[^#] /etc/wpa_supplicant/wpa_supplicant.conf

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
ap_scan=1
fast_reauth=1
country=US

# Home Network
#network={
#       ssid="MY-NETWORK"
#       key_mgmt=IEEE8021X
#       eap=TLS
#       wep_key0=DEADBEAF0123456789ABCDEF000
#       priority=1
#       auth_alg=SHARED
#}
#
#network={
#       key_mgmt=NONE
#       priority=-9999999
#}

The network information is commented out as I was trying to get it to work with the normal user-space tools (e.g. Network Manager); however, it is no longer working in that configuration either. It doesn't seem to ever get to doing the SCAN portion of trying to find networks.

I can see wlan0 in wpa_gui, but I can't get it to scan at all. And I'd much rather use Network Manager if I could over wpa_gui; but it doesn't even see wlan0 (it happily finds eth0, my wired NIC.)

Ben

Re: [gentoo-user] Wireless Configuration...

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 4585 bytes --]

On Saturday 03 Sep 2011 15:14:27 BRM wrote:
> ----- Original Message -----
> 
> > From: Mick <michaelkintzios@gmail.com>
> > To: gentoo-user@lists.gentoo.org

> > Assuming that you have built in your kernel or loaded the driver module
> > for your NIC and any firmware blobs have also been loaded, please show:
>
> Yes. As I noted, it's worked before. The driver loads it find the firmware,
> etc. Configuration information is below.
>  
> 
> > /etc/conf.d/net
> 
> # This is a network block that connects to any unsecured access point.
> # We give it a low priority so any defined blocks are preferred.
> ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel

I think the above should be either:

  ctrl_interface=/var/run/wpa_supplicant
  ctrl_interface_group=wheel

or, 

  DIR=/var/run/wpa_supplicant GROUP=wheel

> #ctrl_interface_group=wheel
> ap_scan=1
> fast_reauth=1
> # This blank configuration will automatically use DHCP for any net.*
> # scripts in /etc/init.d.  To create a more complete configuration,
> # please review /etc/conf.d/net.example and save your configuration
> # in /etc/conf.d/net (this file :]!).
> 
> # Standard Network:
> config_eth0=( "dhcp" )

The old syntax you use here, which was ( "value" ) is now deprecated.  You 
should replace all such entries by removing the brackets, e.g. the above 
becomes:

config_eth0="dhcp"

This is explained in: http://www.gentoo.org/doc/en/openrc-migration.xml


> dns_domain_lo="coal"
> # Wireless Network:
> # TBD
> #config_wlan0 ( "wpa_supplicant" )
> #
> 
> # Enable this to use WPA supplicant; however, need to change the
> configuration of the Wireless first. modules=( "!plug" "!iwconfig"
> "wpa_supplicant" )
> #modules=( "!plug" "wpa_supplicant" )
> #modules=("iwconfig")
> #wpa_supplicant_wlan0="-Dwext"
> #wpa_timeout_wlan0=15
> 
> #modules=("iwconfig")
> #iwconfig_wlan0="mode managed"
> #wpa_timeout_wlan0=15

You should also add something like:

modules="wpa_supplicant"
wpa_supplicant_wlan0="-Dwext"
config_wlan0="dhcp"


> > and 
> > 
> > grep ^[^#] /etc/wpa_supplicant/wpa_supplicant.conf
> 
> ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
> ap_scan=1
> fast_reauth=1
> country=US
> 
> # Home Network
> #network={
> #       ssid="MY-NETWORK"
> #       key_mgmt=IEEE8021X
> #       eap=TLS
> #       wep_key0=DEADBEAF0123456789ABCDEF000
> #       priority=1
> #       auth_alg=SHARED
> #}
> #
> #network={
> #       key_mgmt=NONE
> #       priority=-9999999
> #}
> 
> The network information is commented out as I was trying to get it to work
> with the normal user-space tools (e.g. Network Manager); however, it is no
> longer working in that configuration either. It doesn't seem to ever get
> to doing the SCAN portion of trying to find networks.
> 
> I can see wlan0 in wpa_gui, but I can't get it to scan at all. And I'd much
> rather use Network Manager if I could over wpa_gui; but it doesn't even
> see wlan0 (it happily finds eth0, my wired NIC.)
> 
> Ben

You need to add or uncomment the following to your wpa_supplicant.conf:
=====================
network={
        key_mgmt=NONE
        priority=0
}
=====================

The above will let latch on the first available AP.


Also, you can then add any AP of preference with passphrases and what not:
=====================
# Home Network
network={
      ssid="MY-NETWORK"
#      key_mgmt=IEEE8021X  <--You don't need these entries here, unless
#      eap=TLS             <--you run SSL certs for authentication
      wep_key0=DEADBEAF0123456789ABCDEF000
      priority=1
      auth_alg=OPEN
}
=====================

and something like this for WPA2:
=====================
network={
        ssid="what-ever"
        proto=RSN
        key_mgmt=WPA-PSK
        pairwise=CCMP
        auth_alg=OPEN
		group=CCMP
		psk"pass_123456789"
		priority=5
=====================

Something like the above should get you online again, but you may need to 
experiment with different settings depending on the encryption used by the 
chosen AP.

When wardriving open the wpa_gui, scan and double-click on your desired AP.  
Then enter the key for it (if it has one) and you should be able to associate.  
At that point dhcpcd will kick in and you'll get an IP address and be able to 
connect to the Internet (as long as the AP is not asking for DNS 
authentication or some such security measure).

Of course if you use networkmanager you do not need to use wpa_gui.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Wireless Configuration...

[BRM]

----- Original Message -----

> From: Mick <michaelkintzios@gmail.com>
> On Saturday 03 Sep 2011 15:14:27 BRM wrote:
>>  ----- Original Message -----
>>  > Assuming that you have built in your kernel or loaded the driver 
> module
>>  > for your NIC and any firmware blobs have also been loaded, please 
> show:
>> 
>>  Yes. As I noted, it's worked before. The driver loads it find the 
> firmware,
>>  etc. Configuration information is below.
>>   
>> 
>>  > /etc/conf.d/net
>> 
>>  # This is a network block that connects to any unsecured access point.
>>  # We give it a low priority so any defined blocks are preferred.
>>  ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
> 
> I think the above should be either:
> 
>   ctrl_interface=/var/run/wpa_supplicant
>   ctrl_interface_group=wheel
> 
> or, 
> 
>   DIR=/var/run/wpa_supplicant GROUP=wheel

Ok. Corrected that to the first one.
 
>>  #ctrl_interface_group=wheel
>>  ap_scan=1
>>  fast_reauth=1
>>  # This blank configuration will automatically use DHCP for any net.*
>>  # scripts in /etc/init.d.  To create a more complete configuration,
>>  # please review /etc/conf.d/net.example and save your configuration
>>  # in /etc/conf.d/net (this file :]!).
>> 
>>  # Standard Network:
>>  config_eth0=( "dhcp" )

> The old syntax you use here, which was ( "value" ) is now deprecated.  
> You 
> should replace all such entries by removing the brackets, e.g. the above 
> becomes:
> 
> config_eth0="dhcp"
> 
> This is explained in: http://www.gentoo.org/doc/en/openrc-migration.xml

Corrected that one too. eth0 was working fine though.
 
>>  dns_domain_lo="coal"
>>  # Wireless Network:
>>  # TBD
>>  #config_wlan0 ( "wpa_supplicant" )
>>  #
>> 
>>  # Enable this to use WPA supplicant; however, need to change the
>>  configuration of the Wireless first. modules=( "!plug" 
> "!iwconfig"
>>  "wpa_supplicant" )
>>  #modules=( "!plug" "wpa_supplicant" )
>>  #modules=("iwconfig")
>>  #wpa_supplicant_wlan0="-Dwext"
>>  #wpa_timeout_wlan0=15
>> 
>>  #modules=("iwconfig")
>>  #iwconfig_wlan0="mode managed"
>>  #wpa_timeout_wlan0=15
> 
> You should also add something like:
> 
> modules="wpa_supplicant"
> wpa_supplicant_wlan0="-Dwext"
> config_wlan0="dhcp"

I re-enabled those and added the last line.
 
> 
>>  > and 
>>  > 
>>  > grep ^[^#] /etc/wpa_supplicant/wpa_supplicant.conf
>> 
>>  ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
>>  ap_scan=1
>>  fast_reauth=1
>>  country=US
>> 
>>  # Home Network
>>  #network={
>>  #       ssid="MY-NETWORK"
>>  #       key_mgmt=IEEE8021X
>>  #       eap=TLS
>>  #       wep_key0=DEADBEAF0123456789ABCDEF000
>>  #       priority=1
>>  #       auth_alg=SHARED
>>  #}
>>  #
>>  #network={
>>  #       key_mgmt=NONE
>>  #       priority=-9999999
>>  #}
>> 
>>  The network information is commented out as I was trying to get it to work
>>  with the normal user-space tools (e.g. Network Manager); however, it is no
>>  longer working in that configuration either. It doesn't seem to ever 
> get
>>  to doing the SCAN portion of trying to find networks.
>> 
>>  I can see wlan0 in wpa_gui, but I can't get it to scan at all. And 
> I'd much
>>  rather use Network Manager if I could over wpa_gui; but it doesn't even
>>  see wlan0 (it happily finds eth0, my wired NIC.)
>> 
>>  Ben
> 
> You need to add or uncomment the following to your wpa_supplicant.conf:
> =====================
> network={
>         key_mgmt=NONE
>         priority=0
> }
> =====================
> The above will let latch on the first available AP.

I wasn't sure that that one was for. I've re-enabled it and the original one for my network.
 
> Also, you can then add any AP of preference with passphrases and what not:
> =====================
> # Home Network
> network={
>       ssid="MY-NETWORK"
> #      key_mgmt=IEEE8021X  <--You don't need these entries here, unless
> #      eap=TLS             <--you run SSL certs for authentication
>       wep_key0=DEADBEAF0123456789ABCDEF000
>       priority=1
>       auth_alg=OPEN
> }
> =====================

Interestingly, wpa_supplicant complains if those two lines are not there even though I am not doing SSL auth.
 
> and something like this for WPA2:
> =====================
> network={
>         ssid="what-ever"
>         proto=RSN
>         key_mgmt=WPA-PSK
>         pairwise=CCMP
>         auth_alg=OPEN
>         group=CCMP
>         psk"pass_123456789"
>         priority=5
> =====================

I want to try to get away from adding things directly to the wpa_supplicant.conf file as I would rather that the connection information be managed by a GUI tool.
 
> Something like the above should get you online again, but you may need to 
> experiment with different settings depending on the encryption used by the 
> chosen AP.
> 
> When wardriving open the wpa_gui, scan and double-click on your desired AP.  
> Then enter the key for it (if it has one) and you should be able to associate.  
> At that point dhcpcd will kick in and you'll get an IP address and be able 
> to 
> connect to the Internet (as long as the AP is not asking for DNS 
> authentication or some such security measure).
> 
> Of course if you use networkmanager you do not need to use wpa_gui.

I'd rather use the NetworkManager in KDE than wpa_gui.

That said, NetworkManager in KDE seems to be using wicd for some reason.

I also have KDE running under Kubuntu on my work computer (4.6.2) and the Network Manager is completely different (don't know why) - it's not wicd as far as I can tell.

However, They are still not working. wpa_gui refuses to scan and find networks; while wicd is not finding networks either - but there's so little information in the GUI that it is practically useless to say why.
Perhaps I've got something at the KDE layer screwed up?

I also updated everything so I am now using KDE 4.6.5 (I think it was 4.6.2 or 4.6.3 before).

TIA,

Ben

Re: [gentoo-user] Wireless Configuration...

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 4629 bytes --]

On Tuesday 06 Sep 2011 15:24:33 BRM wrote:
> ----- Original Message -----
> 
> > From: Mick <michaelkintzios@gmail.com>
> > 
> > On Saturday 03 Sep 2011 15:14:27 BRM wrote:
> >>  ----- Original Message -----

> > I think the above should be either:
> > 
> >   ctrl_interface=/var/run/wpa_supplicant
> >   ctrl_interface_group=wheel
> > 
> > or,
> > 
> >   DIR=/var/run/wpa_supplicant GROUP=wheel
> 
> Ok. Corrected that to the first one.

Fine.  I note that you said the wpa_gui won't scan further down this thread, 
just in case ... is your user part of the wheel group?

> >>  #ctrl_interface_group=wheel
> >>  ap_scan=1
> >>  fast_reauth=1
> >>  # This blank configuration will automatically use DHCP for any net.*
> >>  # scripts in /etc/init.d.  To create a more complete configuration,
> >>  # please review /etc/conf.d/net.example and save your configuration
> >>  # in /etc/conf.d/net (this file :]!).
> >>  
> >>  # Standard Network:
> >>  config_eth0=( "dhcp" )
> > 
> > The old syntax you use here, which was ( "value" ) is now deprecated. 
> > You
> > should replace all such entries by removing the brackets, e.g. the above
> > becomes:
> > 
> > config_eth0="dhcp"
> > 
> > This is explained in: http://www.gentoo.org/doc/en/openrc-migration.xml
> 
> Corrected that one too. eth0 was working fine though.

Yes, because eth0 will default to dhcp, after the old syntax you were using 
errors out or is ignored.


> > modules="wpa_supplicant"
> > wpa_supplicant_wlan0="-Dwext"
> > config_wlan0="dhcp"
> 
> I re-enabled those and added the last line.

OK, wpa_supplicant should now work as intended.


> > You need to add or uncomment the following to your wpa_supplicant.conf:
> > =====================
> > network={
> >         key_mgmt=NONE
> >         priority=0
> > }
> > =====================
> > The above will let latch on the first available AP.
> 
> I wasn't sure that that one was for. I've re-enabled it and the original
> one for my network. 

OK, this is useful for open AP which accept connections.  If they need 
encryption you can add this using the wpa_gui.


> > Also, you can then add any AP of preference with passphrases and what
> > not: =====================
> > # Home Network
> > network={
> >       ssid="MY-NETWORK"
> > #      key_mgmt=IEEE8021X  <--You don't need these entries here, unless
> > #      eap=TLS             <--you run SSL certs for authentication
> >       wep_key0=DEADBEAF0123456789ABCDEF000
> >       priority=1
> >       auth_alg=OPEN
> > }
> > =====================
> 
> Interestingly, wpa_supplicant complains if those two lines are not there
> even though I am not doing SSL auth. 

Hmm ... what is the error/warning that comes up?

Either way, can you please add:

eapol_version=1


> > and something like this for WPA2:
> > =====================
> > network={
> >         ssid="what-ever"
> >         proto=RSN
> >         key_mgmt=WPA-PSK
> >         pairwise=CCMP
> >         auth_alg=OPEN
> >         group=CCMP
> >         psk"pass_123456789"
> >         priority=5
> > =====================
> 
> I want to try to get away from adding things directly to the
> wpa_supplicant.conf file as I would rather that the connection information
> be managed by a GUI tool. 

You should be able to add such details in the GUI of choice.  Adding them in 
wpa_supplicant.conf means that they should appear already filled in the GUI.

 
> I'd rather use the NetworkManager in KDE than wpa_gui.
> 
> That said, NetworkManager in KDE seems to be using wicd for some reason.

You need someone else to chime in here, because I use neither of these.  As 
far as I read in this M/L wicd is more or less fool-proof.

> I also have KDE running under Kubuntu on my work computer (4.6.2) and the
> Network Manager is completely different (don't know why) - it's not wicd
> as far as I can tell.
> 
> However, They are still not working. wpa_gui refuses to scan and find
> networks; while wicd is not finding networks either - but there's so
> little information in the GUI that it is practically useless to say why.
> Perhaps I've got something at the KDE layer screwed up?

I don't know if one is causing a clash with the other, so don't try to use 
both at the same time.  If wicd is started automatically when you boot/login, 
then just use that.

When wpa_gui refuses to scan what message do you get?  What do the logs say.

Also, if wpa_gui or wicd fail to scan for APs what do you get from:

# iwlist wlan0 scanning

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Wireless Configuration...

[BRM]

----- Original Message -----

> From: Mick <michaelkintzios@gmail.com>
> On Tuesday 06 Sep 2011 15:24:33 BRM wrote:
>>  ----- Original Message -----
>>  > From: Mick <michaelkintzios@gmail.com>
>>  > On Saturday 03 Sep 2011 15:14:27 BRM wrote:
>>  >>  ----- Original Message -----
>>  > I think the above should be either:
>>  > 
>>  >   ctrl_interface=/var/run/wpa_supplicant
>>  >   ctrl_interface_group=wheel
>>  > 
>>  > or,
>>  > 
>>  >   DIR=/var/run/wpa_supplicant GROUP=wheel
>> 
>>  Ok. Corrected that to the first one.
> 
> Fine.  I note that you said the wpa_gui won't scan further down this thread, 
> 
> just in case ... is your user part of the wheel group?

Yes, so I can use sudo.
 
>>  >>  #ctrl_interface_group=wheel
>>  >>  ap_scan=1
>>  >>  fast_reauth=1
>>  >>  # This blank configuration will automatically use DHCP for any 
> net.*
>>  >>  # scripts in /etc/init.d.  To create a more complete 
> configuration,
>>  >>  # please review /etc/conf.d/net.example and save your 
> configuration
>>  >>  # in /etc/conf.d/net (this file :]!).
>>  >>  
>>  >>  # Standard Network:
>>  >>  config_eth0=( "dhcp" )
>>  > 
>>  > The old syntax you use here, which was ( "value" ) is now 
> deprecated. 
>>  > You
>>  > should replace all such entries by removing the brackets, e.g. the 
> above
>>  > becomes:
>>  > 
>>  > config_eth0="dhcp"
>>  > 
>>  > This is explained in: 
> http://www.gentoo.org/doc/en/openrc-migration.xml
>> 
>>  Corrected that one too. eth0 was working fine though.
> 
> Yes, because eth0 will default to dhcp, after the old syntax you were using 
> errors out or is ignored.

Ok.
 
>>  > modules="wpa_supplicant"
>>  > wpa_supplicant_wlan0="-Dwext"
>>  > config_wlan0="dhcp"
>> 
>>  I re-enabled those and added the last line.
> 
> OK, wpa_supplicant should now work as intended.
> 
> 
>>  > You need to add or uncomment the following to your 
> wpa_supplicant.conf:
>>  > =====================
>>  > network={
>>  >         key_mgmt=NONE
>>  >         priority=0
>>  > }
>>  > =====================
>>  > The above will let latch on the first available AP.
>> 
>>  I wasn't sure that that one was for. I've re-enabled it and the 
> original
>>  one for my network. 
> 
> OK, this is useful for open AP which accept connections.  If they need 
> encryption you can add this using the wpa_gui.

Interesting. Good to know. Thanks!
 
>>  > Also, you can then add any AP of preference with passphrases and what
>>  > not: =====================
>>  > # Home Network
>>  > network={
>>  >       ssid="MY-NETWORK"
>>  > #      key_mgmt=IEEE8021X  <--You don't need these entries 
> here, unless
>>  > #      eap=TLS             <--you run SSL certs for authentication
>>  >       wep_key0=DEADBEAF0123456789ABCDEF000
>>  >       priority=1
>>  >       auth_alg=OPEN
>>  > }
>>  > =====================
>> 
>>  Interestingly, wpa_supplicant complains if those two lines are not there
>>  even though I am not doing SSL auth. 
> 
> Hmm ... what is the error/warning that comes up?

I'll have to check after I get home.
 
> Either way, can you please add:
> 
> eapol_version=1

Will do this evening.
 
>>  I'd rather use the NetworkManager in KDE than wpa_gui.
>>  That said, NetworkManager in KDE seems to be using wicd for some reason.
> You need someone else to chime in here, because I use neither of these.  As 
> far as I read in this M/L wicd is more or less fool-proof.
>>  I also have KDE running under Kubuntu on my work computer (4.6.2) and the
>>  Network Manager is completely different (don't know why) - it's not 
> wicd
>>  as far as I can tell.
>> 
>>  However, They are still not working. wpa_gui refuses to scan and find
>>  networks; while wicd is not finding networks either - but there's so
>>  little information in the GUI that it is practically useless to say why.
>>  Perhaps I've got something at the KDE layer screwed up?
> I don't know if one is causing a clash with the other, so don't try to 
> use 
> both at the same time.  If wicd is started automatically when you boot/login, 
> then just use that.

Well, I figured this part out. Essentially, I had wpa_supplicant, and wicd installed.
However, what I really wanted to NetworkManager and KNetworkManager installed.
So I removed wicd, and installed NetworkManager and KNetworkManager.
I now get the interface I expected under KDE and don't need to use wpa_gui any more.
Still, it doesn't scan.
 
> When wpa_gui refuses to scan what message do you get?  What do the logs say.
> Also, if wpa_gui or wicd fail to scan for APs what do you get from:
> # iwlist wlan0 scanning

At least from the applications I am not getting any error messages. I'll have to check the logs tonight and let you know.

This morning I checked the antennae to verify they were properly connected to the mini-PCI card (as I had opened it up a few weeks ago to see whether it was mini-PCI or mini-PCIe; but I didn't remove/disconnect anything at that  time). Everything checked out. So it shouldn't be a hardware issue unless the card is completely fried for some reason.

I'll check the logs this evening and let you know.

Thanks!

Ben

Re: [gentoo-user] Wireless Configuration...

[Michael Mol]

On Wed, Sep 7, 2011 at 9:54 AM, BRM <bm_witness@yahoo.com> wrote:
>> From: Mick <michaelkintzios@gmail.com>
>> On Tuesday 06 Sep 2011 15:24:33 BRM wrote:
>> I don't know if one is causing a clash with the other, so don't try to
>> use
>> both at the same time.  If wicd is started automatically when you boot/login,
>> then just use that.
>
> Well, I figured this part out. Essentially, I had wpa_supplicant, and wicd installed.
> However, what I really wanted to NetworkManager and KNetworkManager installed.
> So I removed wicd, and installed NetworkManager and KNetworkManager.
> I now get the interface I expected under KDE and don't need to use wpa_gui any more.
> Still, it doesn't scan.

I believe NetworkManager provides WPA supplicant functionlaity, so I
don't think you need wpa_supplicant if you have NetworkManager. It's
been a *long* time (about five years) since I messed with wireless
configuration daemons, though. Lots of things can change in that time,
including memory...

-- 
:wq

[gentoo-user] Re: Wireless Configuration...

[Moritz Schlarb]

Am 07.09.2011 16:06, schrieb Michael Mol:
> I believe NetworkManager provides WPA supplicant functionlaity, so I
> don't think you need wpa_supplicant if you have NetworkManager. It's
> been a *long* time (about five years) since I messed with wireless
> configuration daemons, though. Lots of things can change in that time,
> including memory...
> 

I don't think so! NetworkManager generates a configuration file on the
fly for wpa_supplicant, so you still need it, you just don't need to
configure it anywhere else than NetworkManager!

Regards
-- 
Moritz Schlarb

Re: [gentoo-user] Re: Wireless Configuration...

[Albert W. Hopkins]

On Friday, September 9 at 13:53 (+0200), Moritz Schlarb said:

> I don't think so! NetworkManager generates a configuration file on the
> fly for wpa_supplicant, so you still need it, you just don't need to
> configure it anywhere else than NetworkManager!
> 
Well, not entirely through an on-the-fly config file but through a dbus
connection.

But yeah, NM requires wpa_supplicant (with dbus enabled).  Just look at
the .ebuild.

Re: [gentoo-user] Wireless Configuration...

[BRM]

----- Original Message -----

> From: Mick <michaelkintzios@gmail.com>
> To: gentoo-user@lists.gentoo.org
> Cc: 
> Sent: Tuesday, September 6, 2011 5:32 PM
> Subject: Re: [gentoo-user] Wireless Configuration...
> 
> On Tuesday 06 Sep 2011 15:24:33 BRM wrote:
>>  ----- Original Message -----
>> 
>>  > From: Mick <michaelkintzios@gmail.com>
>>  > 
>>  > On Saturday 03 Sep 2011 15:14:27 BRM wrote:
>>  >>  ----- Original Message -----
> 
>>  > I think the above should be either:
>>  > 
>>  >   ctrl_interface=/var/run/wpa_supplicant
>>  >   ctrl_interface_group=wheel
>>  > 
>>  > or,
>>  > 
>>  >   DIR=/var/run/wpa_supplicant GROUP=wheel
>> 
>>  Ok. Corrected that to the first one.
> 
> Fine.  I note that you said the wpa_gui won't scan further down this thread, 
> 
> just in case ... is your user part of the wheel group?
> 
>>  >>  #ctrl_interface_group=wheel
>>  >>  ap_scan=1
>>  >>  fast_reauth=1
>>  >>  # This blank configuration will automatically use DHCP for any 
> net.*
>>  >>  # scripts in /etc/init.d.  To create a more complete 
> configuration,
>>  >>  # please review /etc/conf.d/net.example and save your 
> configuration
>>  >>  # in /etc/conf.d/net (this file :]!).
>>  >>  
>>  >>  # Standard Network:
>>  >>  config_eth0=( "dhcp" )
>>  > 
>>  > The old syntax you use here, which was ( "value" ) is now 
> deprecated. 
>>  > You
>>  > should replace all such entries by removing the brackets, e.g. the 
> above
>>  > becomes:
>>  > 
>>  > config_eth0="dhcp"
>>  > 
>>  > This is explained in: 
> http://www.gentoo.org/doc/en/openrc-migration.xml
>> 
>>  Corrected that one too. eth0 was working fine though.
> 
> Yes, because eth0 will default to dhcp, after the old syntax you were using 
> errors out or is ignored.
> 
> 
>>  > modules="wpa_supplicant"
>>  > wpa_supplicant_wlan0="-Dwext"
>>  > config_wlan0="dhcp"
>> 
>>  I re-enabled those and added the last line.
> 
> OK, wpa_supplicant should now work as intended.
> 
> 
>>  > You need to add or uncomment the following to your 
> wpa_supplicant.conf:
>>  > =====================
>>  > network={
>>  >         key_mgmt=NONE
>>  >         priority=0
>>  > }
>>  > =====================
>>  > The above will let latch on the first available AP.
>> 
>>  I wasn't sure that that one was for. I've re-enabled it and the 
> original
>>  one for my network. 
> 
> OK, this is useful for open AP which accept connections.  If they need 
> encryption you can add this using the wpa_gui.
> 
> 
>>  > Also, you can then add any AP of preference with passphrases and what
>>  > not: =====================
>>  > # Home Network
>>  > network={
>>  >       ssid="MY-NETWORK"
>>  > #      key_mgmt=IEEE8021X  <--You don't need these entries 
> here, unless
>>  > #      eap=TLS             <--you run SSL certs for authentication
>>  >       wep_key0=DEADBEAF0123456789ABCDEF000
>>  >       priority=1
>>  >       auth_alg=OPEN
>>  > }
>>  > =====================
>> 
>>  Interestingly, wpa_supplicant complains if those two lines are not there
>>  even though I am not doing SSL auth. 
> 
> Hmm ... what is the error/warning that comes up?

pneumo-martyr wpa_supplicant # /etc/init.d/net.wlan0 start  
 * Bringing up interface wlan0
 *   Starting wpa_supplicant on wlan0 ...
Line 17: WPA-PSK accepted for key management, but no PSK configured.
Line 17: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant.conf'.
 *   start-stop-daemon: failed to start `/usr/sbin/wpa_supplicant'                                                                       [ !! ]
 * ERROR: net.wlan0 failed to start


> Either way, can you please add:
> 
> eapol_version=1

Done.

>>  > and something like this for WPA2:
>>  > =====================
>>  > network={
>>  >         ssid="what-ever"
>>  >         proto=RSN
>>  >         key_mgmt=WPA-PSK
>>  >         pairwise=CCMP
>>  >         auth_alg=OPEN
>>  >         group=CCMP
>>  >         psk"pass_123456789"
>>  >         priority=5
>>  > =====================
>> 
>>  I want to try to get away from adding things directly to the
>>  wpa_supplicant.conf file as I would rather that the connection information
>>  be managed by a GUI tool. 
> 
> You should be able to add such details in the GUI of choice.  Adding them in 
> wpa_supplicant.conf means that they should appear already filled in the GUI.
> 
> 
>>  I'd rather use the NetworkManager in KDE than wpa_gui.
>> 
>>  That said, NetworkManager in KDE seems to be using wicd for some reason.
> 
> You need someone else to chime in here, because I use neither of these.  As 
> far as I read in this M/L wicd is more or less fool-proof.
> 
>>  I also have KDE running under Kubuntu on my work computer (4.6.2) and the
>>  Network Manager is completely different (don't know why) - it's not 
> wicd
>>  as far as I can tell.
>> 
>>  However, They are still not working. wpa_gui refuses to scan and find
>>  networks; while wicd is not finding networks either - but there's so
>>  little information in the GUI that it is practically useless to say why.
>>  Perhaps I've got something at the KDE layer screwed up?
> 
> I don't know if one is causing a clash with the other, so don't try to 
> use 
> both at the same time.  If wicd is started automatically when you boot/login, 
> then just use that.
> 
> When wpa_gui refuses to scan what message do you get?  What do the logs say.
> 
> Also, if wpa_gui or wicd fail to scan for APs what do you get from:
> 
> # iwlist wlan0 scanning

Simply returns:

wlan0            No scan results

It also returns "0". I have wlan0 logs directed to /var/log/net/wireless, here's the output from the last attempt:

Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): driver supports SSID scans (scan_capa 0x01).
Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): new 802.11 WiFi device (driver: 'b43legacy')
Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): now managed
Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): device state change: 1 -> 2 (reason 2)
Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): bringing up device.
Sep  7 23:01:43 pneumo-martyr kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): preparing device.
Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): deactivating device (reason: 2).
Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): supplicant interface state:  starting -> ready
Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): device state change: 2 -> 3 (reason 42)

That's about as far as I have been able to get tonight.

Ben

Re: [gentoo-user] Wireless Configuration...

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2993 bytes --]

On Thursday 08 Sep 2011 04:52:44 BRM wrote:
> ----- Original Message -----
> 
> > From: Mick <michaelkintzios@gmail.com>

> > Hmm ... what is the error/warning that comes up?
> 
> pneumo-martyr wpa_supplicant # /etc/init.d/net.wlan0 start 
>  * Bringing up interface wlan0
>  *   Starting wpa_supplicant on wlan0 ...
> Line 17: WPA-PSK accepted for key management, but no PSK configured.
> Line 17: failed to parse network block.
> Failed to read or parse configuration
> '/etc/wpa_supplicant/wpa_supplicant.conf'. *   start-stop-daemon: failed
> to start
> `/usr/sbin/wpa_supplicant'                                                
>                        [ !! ] * ERROR: net.wlan0 failed to start

Ah!  This shows that your /etc/wpa_supplicant/wpa_supplicant.conf has 
something wrong with it and it can't be parsed.  Please check the file's 
access rights and its contents.  This is what it looks like here:

$ ls -la /etc/wpa_supplicant/wpa_supplicant.conf
-rw-r--r-- 1 root root 33388 Jun 14 15:02 
/etc/wpa_supplicant/wpa_supplicant.conf


> > # iwlist wlan0 scanning
> 
> Simply returns:
> 
> wlan0            No scan results

Your device has not been initiated, therefore it would not be able to scan 
until then.


> It also returns "0". I have wlan0 logs directed to /var/log/net/wireless,
> here's the output from the last attempt:
> 
> Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): driver
> supports SSID scans (scan_capa 0x01). Sep  7 23:01:43 pneumo-martyr
> NetworkManager: <info>  (wlan0): new 802.11 WiFi device (driver:
> 'b43legacy') Sep  7 23:01:43 pneumo-martyr NetworkManager: <info> 
> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 Sep  7
> 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): now managed Sep  7
> 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): device state
> change: 1 -> 2 (reason 2) Sep  7 23:01:43 pneumo-martyr NetworkManager:
> <info>  (wlan0): bringing up device. Sep  7 23:01:43 pneumo-martyr kernel:
> ADDRCONF(NETDEV_UP): wlan0: link is not ready Sep  7 23:01:43
> pneumo-martyr NetworkManager: <info>  (wlan0): preparing device. Sep  7
> 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): deactivating
> device (reason: 2). Sep  7 23:01:43 pneumo-martyr NetworkManager: <info> 
> (wlan0): supplicant interface state:  starting -> ready Sep  7 23:01:43
> pneumo-martyr NetworkManager: <info>  (wlan0): device state change: 2 -> 3
> (reason 42)
> 
> That's about as far as I have been able to get tonight.

Just in case, can you please check that rfkill lists both soft and hard locks 
are *not* on? 

Also, what is your wireless NIC?  It may be worth checking that you are still 
using the correct driver for your wireless chipset?

http://linuxwireless.org/en/users/Drivers/b43

and that you are using the latest firmware?

http://linuxwireless.org/en/users/Drivers/b43#Device_firmware_installation
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Wireless Configuration...

[BRM]

----- Original Message -----

> From: Mick <michaelkintzios@gmail.com>
> On Thursday 08 Sep 2011 04:52:44 BRM wrote:
>>  ----- Original Message -----
>> 
>>  > From: Mick <michaelkintzios@gmail.com>
> 
>>  > Hmm ... what is the error/warning that comes up?
>> 
>>  pneumo-martyr wpa_supplicant # /etc/init.d/net.wlan0 start 
>>   * Bringing up interface wlan0
>>   *   Starting wpa_supplicant on wlan0 ...
>>  Line 17: WPA-PSK accepted for key management, but no PSK configured.
>>  Line 17: failed to parse network block.
>>  Failed to read or parse configuration
>>  '/etc/wpa_supplicant/wpa_supplicant.conf'. *   start-stop-daemon: 
> failed
>>  to start
>>  `/usr/sbin/wpa_supplicant'                                              
>   
>>                         [ !! ] * ERROR: net.wlan0 failed to start
> 
> Ah!  This shows that your /etc/wpa_supplicant/wpa_supplicant.conf has 
> something wrong with it and it can't be parsed.  Please check the file's 
> 
> access rights and its contents.  This is what it looks like here:
> 
> $ ls -la /etc/wpa_supplicant/wpa_supplicant.conf
> -rw-r--r-- 1 root root 33388 Jun 14 15:02 
> /etc/wpa_supplicant/wpa_supplicant.conf

That error only comes up when those two lines are commented out. If I return them, then all is fine.
 
>>  > # iwlist wlan0 scanning
>> 
>>  Simply returns:
>> 
>>  wlan0            No scan results
> 
> Your device has not been initiated, therefore it would not be able to scan 
> until then.

True.

>>  It also returns "0". I have wlan0 logs directed to 
> /var/log/net/wireless,
>>  here's the output from the last attempt:
>> 
>>  Sep  7 23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): driver
>>  supports SSID scans (scan_capa 0x01). Sep  7 23:01:43 pneumo-martyr
>>  NetworkManager: <info>  (wlan0): new 802.11 WiFi device (driver:
>>  'b43legacy') Sep  7 23:01:43 pneumo-martyr NetworkManager: 
> <info> 
>>  (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 Sep  7
>>  23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): now managed 
> Sep  7
>>  23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): device state
>>  change: 1 -> 2 (reason 2) Sep  7 23:01:43 pneumo-martyr NetworkManager:
>>  <info>  (wlan0): bringing up device. Sep  7 23:01:43 pneumo-martyr 
> kernel:
>>  ADDRCONF(NETDEV_UP): wlan0: link is not ready Sep  7 23:01:43
>>  pneumo-martyr NetworkManager: <info>  (wlan0): preparing device. Sep  
> 7
>>  23:01:43 pneumo-martyr NetworkManager: <info>  (wlan0): deactivating
>>  device (reason: 2). Sep  7 23:01:43 pneumo-martyr NetworkManager: 
> <info> 
>>  (wlan0): supplicant interface state:  starting -> ready Sep  7 23:01:43
>>  pneumo-martyr NetworkManager: <info>  (wlan0): device state change: 2 
> -> 3
>>  (reason 42)
>> 
>>  That's about as far as I have been able to get tonight.
> 
> Just in case, can you please check that rfkill lists both soft and hard locks 
> are *not* on? 

I have checked rfkill quite a bit. For a while, it was an issue whenever I restarted the wlan0 - I'd have to stop wlan0, rfkill unblock all, then start wlan0 again to get a connection. Very annoying.
Using KNetworkManager I have found it on occasion being blocked, but mostly unblocked.

> Also, what is your wireless NIC?  It may be worth checking that you are still 
> using the correct driver for your wireless chipset?
> http://linuxwireless.org/en/users/Drivers/b43
> and that you are using the latest firmware?
> http://linuxwireless.org/en/users/Drivers/b43#Device_firmware_installation

Sadly, it's a Dell TrueMobile 1300, which used the BroadCom 4306/Rev2 chipset.
There's only one version of the firmware usable for it, and the b43-legacy driver is the only one that supports it.

I am still trying to find a good replacement. Since I want a 802.11n capable replacement, finding a new mini-PCI card is hard. (Intel only has mini-PCIe.)
Finding a decently supported PCMCIA/PC Card card (Type 1 or 2)     is also hard - most that are supported are only the 2.4GHZ range, and I'd like to use the 5GHZ range for 802.11n with the 2.4 GHZ for 802.11g.
Simply put, I'd like to take full advantage of 802.11n and finding something capable and supported is proving difficult. The linuxwireless.org website is not very helpful in that respect either.

So, yes - I'm full open to replacement suggestions. I'd much rather have a fully supported Atheros-based card, and I'm getting tired of looking too.

Ben

Re: [gentoo-user] Wireless Configuration...

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 256 bytes --]

OK, so if you restore the two lines and this error goes away, can you then 
initialise the device without any other errors?

Assuming that rfkill shows all is unlocked and the device active, what does 
iwlist wlan0 scan show now?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Wireless Configuration...

[BRM]

----- Original Message -----

> From: Mick <michaelkintzios@gmail.com>
> Subject: Re: [gentoo-user] Wireless Configuration...
> OK, so if you restore the two lines and this error goes away, can you then 
> initialise the device without any other errors?

So far as I am aware.

> Assuming that rfkill shows all is unlocked and the device active, what does 
> iwlist wlan0 scan show now?

The output I quoted was from that configuration.

----- Original Message -----
> From: Moritz Schlarb <mail@moritz-schlarb.de>
> Subject: [gentoo-user] Re: Wireless Configuration...
> Am 07.09.2011 16:06, schrieb Michael Mol:
>>  I believe NetworkManager provides WPA supplicant functionlaity, so I
>>  don't think you need wpa_supplicant if you have NetworkManager. 
> It's
>>  been a *long* time (about five years) since I messed with wireless
>>  configuration daemons, though. Lots of things can change in that time,
>>  including memory...
>
> I don't think so! NetworkManager generates a configuration file on the
> fly for wpa_supplicant, so you still need it, you just don't need to
> configure it anywhere else than NetworkManager!

So NetworkManager/KNetworkManager generates a wpa_supplicant.conf on the fly to use, thereby ignoring the one in /etc/wpa_supplicant?
Would it then be correct that it also ignores the settings in /etc/conf.d/net?

Ben

Re: [gentoo-user] Wireless Configuration...

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1000 bytes --]

On Friday 09 Sep 2011 14:31:23 BRM wrote:
> ----- Original Message -----
> 
> > From: Mick <michaelkintzios@gmail.com>
> > Subject: Re: [gentoo-user] Wireless Configuration...
> > OK, so if you restore the two lines and this error goes away, can you
> > then initialise the device without any other errors?
> 
> So far as I am aware.
> 
> > Assuming that rfkill shows all is unlocked and the device active, what
> > does iwlist wlan0 scan show now?
> 
> The output I quoted was from that configuration.

I see.  In that case if with the card initialised and unlocked it still cannot 
scan, I fear that the problem is with the driver/firmware.

If this started happening after a particular kernel version I would readily 
blame the kernel.

Although it won't solve the problem at hand you can boot with a previous 
kernel (from the time when it all worked fine) to prove that this is the case.

You can also try later kernels to see if it has been fixed.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]