From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] wpa_supplicant takes a long time to startup
Date: Sun, 25 Jun 2006 07:38:30 +0200 [thread overview]
Message-ID: <449E2156.3060700@mid.email-server.info> (raw)
Hello.
I'm using wpa_supplicant-0.5.4 on Gentoo and 0.4.x on Ubuntu Dapper (6.0.6).
When I set my /etc/conf.d/net so, that wpa_supplicant is used, I
experience a rather long delay before the DHCP packages are sent
out. On Ubuntu, I do not see such a long delay, so I don't think
that it has something to do with wpa_supplicant in *general*.
When I make Gentoo use WEP directly (ie. without the help of wpa_supplicant)
I also do not see a delay. I'm using a
00:06.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
Wifi card, and thus madwifi; madwifi-ng-0.1531.20060427 to be exact.
On Ubuntu, I'm using an older version of madwifi.
Do other also experience a long (ie. ~30 seconds) delay when
starting wpa_supplicant? How can I find out, what's happening
during this delay?
/etc/conf.d/net:
config_ath0=( "dhcp" )
dhcpcd_ath0="-t 25"
mode_ath0="managed"
fallback_ath0=( "192.168.1.60/24" )
fallback_route_ath0=( "default via 192.168.1.1" )
preferred_aps=( "MeinVerschlossenesNetz" )
modules=( "wpa_supplicant" )
wpa_supplicant_ath0="-Dmadwifi"
wpa_timeout_ath0=60
/etc/wpa_supplicant/wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="MeinVerschlossenesNetz"
psk=bf91a35[...]
}
blob-base64-exampleblob={
SGVsbG8gV29ybGQhCg==
}
Thanks,
Alexander Skwar
--
Keep brain from freezing.
-- Homer Simpson
Simpson and Delilah
--
gentoo-user@gentoo.org mailing list
reply other threads:[~2006-06-25 6:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=449E2156.3060700@mid.email-server.info \
--to=listen@alexander.skwar.name \
--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