public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jan Seeger <jan.seeger@thenybble.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] iwlwifi & psk auth
Date: Mon, 10 Mar 2008 21:33:32 +0100	[thread overview]
Message-ID: <20080310203332.GA26816@venus> (raw)
In-Reply-To: <11710023105.20080310213732@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1944 bytes --]

On Mon, 10. Mar, Sergey Kobzar spammed my inbox with 
<snip>
> My kernel is Linux 2.6.24-gentoo-r3.
> Unfortunately I can't emerge iwlwifi (but maybe it's not required?):
Yes, with 2.6.24, iwlwifi is not required anymore.
<snip>
> 
> Also looks like it's impossible to get WPA-PSK working with iwlwifi
> driver - I didn't find any success story in Google.
Then you haven't read mine^^. I actually have it working beautifully with
WPA-PSK and unencrypted. Here's my wpa_supplicant.conf and my /etc/conf.d/net
(with passwords removed, of course^^):

/etc/wpa_supplicant/wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
update_config=0
fast_reauth=1
ap_scan=1


network={
    ssid="WLAN1"
    psk="<key>"
    pairwise=TKIP
    group=TKIP
    priority=5
}

network={
    ssid="WLAN2"
    psk="<key>"
    pairwise=TKIP
    group=TKIP
    priority=500
}


network={
    ssid="lrz"
    key_mgmt=NONE
    priority=500
}

network={
    key_mgmt=NONE
    priority=0
}

/etc/conf.d/net (with comments):


modules=("wpa_supplicant")
wpa_supplicant_wlan0="-Dwext" # This, you need

#preferred_aps=( "WLAN1","WLAN2" ) Do not set this: wpa_supplicant chooses
#the APs itself

#Network configuration
config_WLAN1=( "192.168.178.25 netmask 255.255.255.0 broadcast 192.168.178.255" )
config_WLAN2=( "192.168.178.25 netmask 255.255.255.0 broadcast 192.168.178.255" );
#
routes_WLAN1=( "default via 192.168.178.1" )
routes_WLAN2=( "default via 192.168.178.1" )
#
dns_servers_WLAN1=( "192.168.178.1" )
dns_servers_WLAN2=( "192.168.178.1" )
#
gateways_WLAN1=( "192.168.178.1" )
gateways_WLAN2=( "192.168.178.1" )

Also, I have a handy little script which I will attach. It stops the net.wlan0
initscript, unloads the iwl module and reloads the module. The initscript
automatically restarts.

HTH,
Jan
-- 
thenybble.de/blog/ -- four bits at a time

[-- Attachment #1.2: iwlrestart --]
[-- Type: text/plain, Size: 72 bytes --]

#!/bin/bash

/etc/init.d/net.wlan0 stop
rmmod iwl3945
modprobe iwl3945


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-03-10 20:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 19:37 [gentoo-user] iwlwifi & psk auth Sergey Kobzar
2008-03-10 20:23 ` Pongracz Istvan
2008-03-10 20:33 ` Jan Seeger [this message]
2008-03-10 20:44   ` Re[2]: " Sergey Kobzar
2008-03-10 21:01     ` Jan Seeger
2008-03-10 21:28       ` Pongracz Istvan
2008-03-10 21:39         ` Pongracz Istvan
2008-03-11  8:00           ` Re[2]: " Sergey Kobzar
2008-03-11  9:05             ` Pongracz Istvan
2008-03-11 10:49               ` Pongracz Istvan
2008-03-11 12:02                 ` Peter Humphrey
2008-03-11 19:39                   ` Pongracz Istvan
2008-03-10 20:56   ` Pongracz Istvan
2008-03-11 11:32   ` Peter Humphrey
2008-03-11 12:36     ` Jan Seeger
2008-03-11 17:22       ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080310203332.GA26816@venus \
    --to=jan.seeger@thenybble.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox